-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Additional definitions exports for Pointer Events #6758
Comments
Since this is imprecise descriptive prose anyway, I suggest it be replaced with "event loop", so that "task queue" can continue being a HTML-internal concept which we are free to refactor.
This is a classic example of monkeypatching. We should not export the operation from HTML so that it can be monkeypatched. Instead, this normative requirement (to fire pointercancel + pointerout + pointerleave, all synchronously I guess) should be moved to the definition of "initiate the drag-and-drop operation".
Yeah, another monkeypatch. The correct architecture here is trickier, but here's one idea:
This will also make it clear where the coalesced pointer events get fired, relative to all the other things that happen during update the rendering (i.e. autofocus, resize, scroll, media queries, animations, fullscreen, animation frame callbacks, intersection observers, paint timing...). |
Helps with w3c/pointerevents#384. See also #6758.
There is a remaining last clarification to make but I believe the issue here could be closed since it's been resolved on the pointer events side. Thank you @domenic for the feedback. |
Hmm. I think there's still work to do here if possible:
|
Helps with w3c/pointerevents#384. See also whatwg#6758.
From w3c/pointerevents#381
Pointer Events link to 3 places in HTML that are not exported:
cc @patrickhlauke
The text was updated successfully, but these errors were encountered: