Repository navigation
Conversation
Contributor
|
Warning The target branch has been automatically set to Please Edit this PR if this wasn't your intention. |
Contributor
Author
|
CC @emilio , @mustaqahmed |
Contributor
Author
|
Note that I ran the modified test on Chrome (on Linux) and Safari, the test passed on 20/20, 20/20 respectively so I would say it's stable. |
mustaqahmed
approved these changes
Oct 27, 2026
mustaqahmed
left a comment
mustaqahmed
left a comment
Contributor
There was a problem hiding this comment.
The change LGTM. I am asking for a comment update, and optionally a resize0 logging too.
emilio
reviewed
Oct 27, 2026
…ng updates apart in new-scroll-event-dispatched-at-next-updating-rendering-time.html. r?#layout-reviewers Timer callbacks are queued on the timer task source and rendering updates on the rendering task source, and the event loop picks among task queues in an implementation-defined manner, so a timeout set in a requestAnimationFrame callback may run after the next rendering update. The resize event fired by the next rendering update's resize steps, right before its scroll steps, marks the start of that update instead. https://html.spec.whatwg.org/#event-loop-processing-model
|
No new issues detected. This pull request is 🆗 |
1 similar comment
|
No new issues detected. This pull request is 🆗 |
emilio
approved these changes
Oct 28, 2026
|
Pull request closed by commit b0161d1 |
lando-worker Bot
pushed a commit
that referenced
this pull request
Oct 29, 2026
…… r=mustaqahmed,emilio …ng updates apart in new-scroll-event-dispatched-at-next-updating-rendering-time.html. r?#layout-reviewers Timer callbacks are queued on the timer task source and rendering updates on the rendering task source, and the event loop picks among task queues in an implementation-defined manner, so a timeout set in a requestAnimationFrame callback may run after the next rendering update. The resize event fired by the next rendering update's resize steps, right before its scroll steps, marks the start of that update instead. https://html.spec.whatwg.org/#event-loop-processing-model Pull request: #416
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ng updates apart in new-scroll-event-dispatched-at-next-updating-rendering-time.html. r?#layout-reviewers
Timer callbacks are queued on the timer task source and rendering updates on the rendering task source, and the event loop picks among task queues in an implementation-defined manner, so a timeout set in a requestAnimationFrame callback may run after the next rendering update. The resize event fired by the next rendering update's resize steps, right before its scroll steps, marks the start of that update instead.
https://html.spec.whatwg.org/#event-loop-processing-model
Lando: link
Bugzilla: bug 1962340
🚫 This pull request has 1 blocker.