Intent to Ship: Pseudo target on events

19 views
Skip to first unread message

Daniil Sakhapov

unread,
9:31 AM (2 hours ago) 9:31 AM
to blink-dev
Contact emails
sakh...@chromium.org

Explainer
Please note, that  the spec edit has been mostly approved and finalized, but put on hold due to a major spec repo refactoring. But I don't think it should stop from shipping, since ideally it would be shipped together with CSSPseudoElement interface in M147.

Specification
https://github.com/w3c/uievents/pull/413/changes

Summary
Specific events are now extended to have `.pseudoTarget` that is either CSSPseudoElement (if interaction has been with pseudo-element) or null. This allows to have more specific information on the event origin, e.g. that not just an ultimate originating element (Event.target) has been clicked, but more specifically that it was ::after. Note that the Event.target is unchanged so event only has extra info on pseudo-element interaction. The events are UIEvent, AnimationEvent, TransitionEvent. mouseover, mouseout, mouseenter, mouseleave and their pointer* counterparts are not yet supported.

Blink component
Blink>CSS

TAG review
No information provided

TAG review status
Pending

Risks

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes

Is this feature fully tested by web-platform-tests?
Yes
https://wpt.fyi/css/css-pseudo/events-on-pseudo-element-mutation.tentative.html http://wpt.fyi/css/css-pseudo/events-on-pseudo-element.tentative.html

Tracking bug
https://issues.chromium.org/issues/40639103

Estimated milestones
Shipping on desktop147
Shipping on Android147
Shipping on WebView147

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5179328935624704?gate=6529265912905728

This intent message was generated by Chrome Platform Status.
Reply all
Reply to author
Forward
0 new messages