Improve preemptive task blocking around user gestures |
|||||||
Issue descriptionAt the moment blink scheduler blocks all timer and loading tasks (if they are expensive) for 2 seconds after a user gesture (expecting that a new one might come). It it known to cause a number of problems for the web developers. We need to tune it to make it less aggressive and more predictable while saving the performance wins.
,
Oct 31 2017
,
Nov 4 2017
How much of a performance win was it when we turned on this blocking? I just want context for what we're trading off here.
,
Nov 8 2017
Re #3: It used to give a major performance benefit, but we're not sure if it is true anymore with passive event listener intervention. One of the first items here would be to measure the current state.
,
Jan 11 2018
I realized my previous comment could be taken to support removing or keeping it. To be clear, I'd support just deleting and seeing if anything regresses.
,
Mar 29 2018
,
Mar 29 2018
Issue 529529 has been merged into this issue.
,
Apr 3 2018
,
Aug 17
,
Aug 20
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by altimin@chromium.org
, Oct 31 2017