Differentiate Chrome-crafted scroll events from user-initiated events#24
Merged
Differentiate Chrome-crafted scroll events from user-initiated events#24
scroll events from user-initiated events#24Conversation
This was referenced Jun 21, 2019
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
1 participant
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.
Description
This work will differentiate Chrome-crafted
scrollevents from user-initiated events. If thescrollevent is fired from Chrome, the panel should continue to be sticky.Changelog
Composer: fix #22, syntheticscrollevents crafted by Chrome should not cause stickiness to lose, in PR #23