-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dispatch mouseenter/leave/out/over when the layout (or scroll) changes #154
Comments
Anything you can link to here about existing browser behavior and web compat impact (eg. example sites/developers preferring this behavior)? |
I have a question relating the referenced commit https://github.com/w3c/uievents/pull/155/files, for example, mouseover. The spec says:
Thus, moving an element underneath a non-primary pointing device doesn't imply any mouseover event. But I wonder whether such moving also silently update “current” element underneath that non-primary pointing device, or keep the previous underneath one, so that mouseover event will be fired if, after such moving, the pointer has moved inside that moved element. |
Non primary pointing devices don't end up firing mouse events. (see https://w3c.github.io/pointerevents/#dfn-primary-pointer) |
dtapuska, thanks a lot! |
Chrome implementation: https://chromium-review.googlesource.com/c/615424 W3C UIEvents issue: w3c/uievents#154 BUG=488886 Change-Id: I732ef83ea7ca916d564d3af0419f4da0e3db1d45
Chrome implementation: https://chromium-review.googlesource.com/c/615424 W3C UIEvents issue: w3c/uievents#154 BUG=488886 Change-Id: I732ef83ea7ca916d564d3af0419f4da0e3db1d45
Chrome implementation: https://chromium-review.googlesource.com/c/615424 W3C UIEvents issue: w3c/uievents#154 BUG=488886 Change-Id: I732ef83ea7ca916d564d3af0419f4da0e3db1d45 Reviewed-on: https://chromium-review.googlesource.com/615146 Commit-Queue: Dave Tapuska <[email protected]> Reviewed-by: Mustaq Ahmed <[email protected]> Cr-Commit-Position: refs/heads/master@{#526684}
Chrome implementation: https://chromium-review.googlesource.com/c/615424 W3C UIEvents issue: w3c/uievents#154 BUG=488886 Change-Id: I732ef83ea7ca916d564d3af0419f4da0e3db1d45 Reviewed-on: https://chromium-review.googlesource.com/615146 Commit-Queue: Dave Tapuska <[email protected]> Reviewed-by: Mustaq Ahmed <[email protected]> Cr-Commit-Position: refs/heads/master@{#526684}
Add text to ensure that when a layout or scroll changes mousenter/leave/out/over MUST be dispatched.
A user agent may select to dispatch them shortly after the action is completed for say a scroll action it does not make sense to dispatch them until the user agent has determined the scroll to end.
The text was updated successfully, but these errors were encountered: