You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If jQuery execution is blocked for whatever reason (debugger pause, tab change, etc) it will continue to queue up animation events, then it executes them once the process is unblocked (debugger play, return to tab). If there are many terminal lines that have come in since the process was blocked, the user cannot scroll until every jQuery scroll animation has completed, synchronously. This takes a while if there are hundreds of animations queued up.
This behavior can be found in other jQuery animations like slideshows and non-CSS animations, and is exhibited in browsers that block non-active tab processes to save resources.
Not sure how to fix this - detect if the tab is active before executing the page scroll animation?
The text was updated successfully, but these errors were encountered:
If jQuery execution is blocked for whatever reason (debugger pause, tab change, etc) it will continue to queue up animation events, then it executes them once the process is unblocked (debugger play, return to tab). If there are many terminal lines that have come in since the process was blocked, the user cannot scroll until every jQuery scroll animation has completed, synchronously. This takes a while if there are hundreds of animations queued up.
This behavior can be found in other jQuery animations like slideshows and non-CSS animations, and is exhibited in browsers that block non-active tab processes to save resources.
Not sure how to fix this - detect if the tab is active before executing the page scroll animation?
The text was updated successfully, but these errors were encountered: