(In reply to Bramus from comment #6) > The most visual outcome is that the animations are no longer subject to jank. E.g. https://cdpn.io/pen/debug/MYgNVay keeps running buttery smooth in Chrome 144+ while the Main Thread gets (artificially) blocked. (FWIW: in Firefox, when jank happens in this^ codepen testcase, the animation seems to immediately snap to the end [right when the jank starts]; whereas in Chrome, the animation pauses for the duration of the jank [which is the thing that the optimization seeks to address]). I wonder if Firefox's immediately-snap-to-the-end behavior is related to the outcome we ended up with in bug 1540906, or something else...
Bug 2000047 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Bramus from comment #6) > The most visual outcome is that the animations are no longer subject to jank. E.g. https://cdpn.io/pen/debug/MYgNVay keeps running buttery smooth in Chrome 144+ while the Main Thread gets (artificially) blocked. (FWIW: in Firefox, when random-synthetic-jank happens in this^ codepen testcase, the animation seems to immediately snap to the end [right when the jank starts]; whereas in Chrome, the animation pauses for the duration of the jank [which is the thing that the optimization seeks to address]). I wonder if Firefox's immediately-snap-to-the-end behavior is related to the outcome we ended up with in bug 1540906, or something else...
(In reply to Bramus from comment #6) > The most visual outcome is that the animations are no longer subject to jank. E.g. https://cdpn.io/pen/debug/MYgNVay keeps running buttery smooth in Chrome 144+ while the Main Thread gets (artificially) blocked. (FWIW: in Firefox, when random-synthetic-jank happens in this^ codepen testcase, the animation seems to immediately snap to the end [right away, when the jank starts]; whereas in Chrome, the animation pauses for the duration of the jank [which is the thing that the optimization seeks to address]). I wonder if Firefox's immediately-snap-to-the-end behavior is related to the outcome we ended up with in bug 1540906, or something else...
(In reply to Bramus from comment #6) > The most visual outcome is that the animations are no longer subject to jank. E.g. https://cdpn.io/pen/debug/MYgNVay keeps running buttery smooth in Chrome 144+ while the Main Thread gets (artificially) blocked. (FWIW: in Firefox, when random-synthetic-jank happens in this^ codepen testcase, the animation seems to immediately snap to the end [right away, when the jank starts]; whereas in Chrome release, the animation pauses for the duration of the jank [which is the thing that the optimization seeks to address] and *then* snaps to the end [or wherever it should be]). I wonder if Firefox's immediately-snap-to-the-end behavior is related to the outcome we ended up with in bug 1540906, or something else...