Contact emails
nzol...@chromium.org
Spec
https://w3c.github.io/pointerevents/#extensions-to-the-globaleventhandlers-interface
Summary
Previously in PointerEvents spec v1 (https://www.w3.org/TR/pointerevents/) ongotpointercapture and onlostpointercapture were attributes as part of the Element, driven by the idea that the target can only ever be an Element. Now we are moving them to GlobalEventHandlers to make them consistent with the other on'event' attributes as it is possible to listen to these events in their capturing dispatch phase. Note that this way of listening to the events through on'event' attributes are legacy and should not be mostly used. But this change makes sure they are all consistent.
Motivation
There was a web developer reported issue regarding the onpointerdown attribute. So for consistency in the spec ongot/lostpointercapture attributes have been added to the GlobalEventHandlers IDL.
Interoperability risk
Firefox: No public signals
Edge: Public support
Safari: No public signals
Web developers: No signals
Compatibility risk
The risk should be minimal as for the most part we are expanding the scope of definition of the attribute. All code using ongotpointercapture and onlostpointercapture today will continue to work after this change.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux,
Chrome OS, Android, and Android WebView)? Yes
OWP launch tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=674290
Link to entry on the Chrome Platform Status
https://www.chromestatus.com/features/5702802084986880
Requesting approval to ship? Yes
LGTM2
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
On 12/19/16 8:49 AM, Navid Zolghadr wrote:
Now we are moving
them to GlobalEventHandlers to make them consistent with the other
on'event' attributes as it is possible to listen to these events in
their capturing dispatch phase.
Except you can't use on* attributes to add capturing listeners. So they will be completely useless in practice, if the event doesn't bubble. I _think_ these events don't bubble. It's a bit hard to tell because https://w3c.github.io/pointerevents/#firing-events-using-the-pointerevent-interface links to an old and less-clear version of the DOM spec, but if I assume it should be linking to the current version then the event certainly won't bubble the way it's being fired right now.