Fix mouse-pointer-preventdefault for Firefox/Safari #25056
Merged
Conversation
This file contains 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
wpt-pr-bot
approved these changes
Aug 17, 2020
Safari and Firefox fire pointerevents & compatible mouse events in a different order than Chrome. The order matches the PointerEvents specification for all browsers. Modify the test to reflect this difference in the browser implementation. Bug: 1085549, 1085647 Change-Id: I43ed0bbbabb0abbcbd93fbab7e5d8ee98a902611 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359588 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Commit-Queue: Liviu Tinta <liviutinta@chromium.org> Cr-Commit-Position: refs/heads/master@{#801077}
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-2359588
branch
from
3c367eb
to
81f5c60
Compare
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.
Safari and Firefox fire pointerevents & compatible mouse
events in a different order than Chrome. The order matches the
PointerEvents specification for all browsers. Modify the test to
reflect this difference in the browser implementation.
Bug: 1085549, 1085647
Change-Id: I43ed0bbbabb0abbcbd93fbab7e5d8ee98a902611
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359588
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801077}