-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Update HTML Drag-and-Drop steps to include pointercancel firing. #6912
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3111,7 +3111,9 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute | |
|
|
||
| <ul class="brief"> | ||
| <li><dfn data-x-href="https://w3c.github.io/pointerevents/#pointerevent-interface"><code>PointerEvent</code></dfn> interface</li> | ||
| <li><dfn data-x-href="https://w3c.github.io/pointerevents/#dfn-fire-a-pointer-event">fire a pointer event</dfn></li> | ||
| <li><dfn data-x="event-pointerup" data-x-href="https://w3c.github.io/pointerevents/#the-pointerup-event"><code>pointerup</code></dfn> event</li> | ||
| <li><dfn data-x="event-pointercancel" data-x-href="https://w3c.github.io/pointerevents/#the-pointercancel-event"><code>pointercancel</code></dfn> event</li> | ||
| </ul> | ||
|
|
||
| <p>This specification sometimes uses the term <dfn data-x="">name</dfn> to refer to the event's | ||
|
|
@@ -78297,13 +78299,17 @@ dictionary <dfn dictionary>DragEventInit</dfn> : <span>MouseEventInit</span> { | |
| <span>source node</span>.</p> | ||
|
|
||
| <p>If the event is canceled, then the drag-and-drop operation should not occur; return.</p> | ||
| <!-- only a should because the UA can always allow the user to drag without the page knowing --> | ||
| <!-- only a "should" because the UA can always allow the user to drag without the page knowing --> | ||
|
|
||
| <p class="note">Since events with no event listeners registered are, almost by definition, never | ||
| canceled, drag-and-drop is always available to the user if the author does not specifically | ||
| prevent it.</p> | ||
| </li> | ||
|
|
||
| <li><p><span>Fire a pointer event</span> at the <span>source node</span> named <code | ||
| data-x="event-pointercancel">pointercancel</code>, and fire any other follow-up events as | ||
| required by <cite>Pointer Events</cite>. <ref spec=POINTEREVENTS></p></li> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, this kind of vagueness is not great, but I guess that's how the pointer events spec is structured, so probably it's OK.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, there is no algorithmic steps to link to here! |
||
|
|
||
| <li> | ||
| <p><span>Initiate the drag-and-drop operation</span> in a manner consistent with platform | ||
| conventions, and as described below.</p> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like it needs to use https://w3c.github.io/pointerevents/#dfn-fire-a-pointer-event instead of concept-event fire.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.