Add a note and diagram to clarify legacy mouse pointer behavior. #458
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
This shows the effective position of legacy mouse pointer when two primary pointers are active at the same time, and points out the disconnection between `pointerout` and `mouseout` events.
|
@flackr and @patrickhlauke PTAL. I will fine-tune on the animated GIF once the text seems okay. |
flackr
reviewed
Oct 12, 2022
|
Did some tweaking/rewording |
Instead of repeating the same concepts in slightly different way in the note, replace the possibly a bit obscure original wording with some of the clearer prose. Use `<video>` element for the `.webm` rather than `<img>` (as, at least for me, this didn't appear to be supported in the browser)
patrickhlauke
force-pushed
the
gh-pages
branch
from
f1a3df0
to
4fcf9f3
Compare
mustaqahmed
commented
Oct 26, 2022
| @@ -1196,7 +1196,7 @@ <h1><dfn data-lt="compatibility mouse events">Compatibility mapping with mouse e | |||
| </div> | |||
| <section> | |||
| <h2><dfn>Tracking the effective position of the legacy mouse pointer</dfn></h2> | |||
| <p>While only <a>primary pointers</a> can produce compatibility mouse events, <a href="#multiple-primary-pointers">multiple primary pointers</a> can be active simultaneously, each producing its own compatibility mouse events. For compatibility with scripts relying on MouseEvents, mouse transition events (<code>pointerover</code>, <code>pointerout</code>, <code>pointerenter</code> and <code>pointerleave</code>) SHOULD simulate the movement of a <em>single</em> legacy mouse input. This means that the entry/exit state for every event target is valid, in accordance with [[UIEVENTS]]. Users agents SHOULD guarantee this by maintaining the <dfn>effective position of the legacy mouse pointer</dfn> in the document as follows.</p> | |||
| <p>While only <a>primary pointers</a> can produce compatibility mouse events, <a href="#multiple-primary-pointers">multiple primary pointers</a> can be active simultaneously, each producing its own compatibility mouse events. For compatibility with scripts relying on MouseEvents, the mouse transition events (<code>mouseover</code>, <code>mouseout</code>, <code>mouseenter</code> and <code>mouseleave</code>) SHOULD simulate the movement of a <em>single</em> legacy mouse input. This means that the entry/exit state for every event target is valid, in accordance with [[UIEVENTS]]. Users agents SHOULD guarantee this by maintaining the <dfn>effective position of the legacy mouse pointer</dfn> in the document as follows.</p> | |||
There was a problem hiding this comment.
Good catch listing the actual mouse* events here, rather than pointer* ones
| and <code>pointerleave</code>) to corresponding legacy mouse transition events (i.e., <code>mouseover</code>, | ||
| <code>mouseout</code>, <code>mouseenter</code> and <code>mouseleave</code>). The following animation illustrates a case | ||
| where a user agent needs to dispatch more legacy mouse transition events than pointer transition events to be able to | ||
| reconcile two primary pointers using a single legacy mouse input.</p> |
patrickhlauke
approved these changes
Oct 26, 2022
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.
This shows the effective position of legacy mouse pointer when two primary pointers are active at the same time, and points out the disconnection between
pointeroutandmouseoutevents.Closes #454.
Preview | Diff