Re:Chrome will aggressively throttle background tabs
by just2n on Tuesday January 24, 2017 @02:49PM
(#13474819)
Why not limit it to a single render queued with the latest information?
I see this done via debouncing for render operations that happen on repeated events, for instance typing (send query to server, then show matching results in a render of some list).
I see this done via debouncing for render operations that happen on repeated events, for instance typing (send query to server, then show matching results in a render of some list).