No scrollend events should be fired after the last scroll event #45450
Conversation
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
hiikezoe
reviewed
Apr 2, 2024
|
|
||
| assert_true(scroll_event_count > 0, "A scroll event has fired"); | ||
|
|
||
| await waitForCompositorCommit(); |
There was a problem hiding this comment.
I'd prefer using two rAFs instead of waitForCompositorCommit, the function might be changed in future.
|
It would be nice to have a link to https://bugzilla.mozilla.org/show_bug.cgi?id=1881974 in the test itself. |
For a given scroll, no scrollend events should be fired after the last scroll event was fired.
4ebecd4 to
2744b48
Compare
Good suggestions! Updated the tests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
For a given scroll, no scrollend events should be fired after the last scroll event was fired.
CC: @hiikezoe @theres-waldo