Intent to Ship: Non-composed Mouse and Pointer enter/leave events
Mustaq Ahmed
Contact emails
mus...@chromium.orgSpecification
https://w3c.github.io/uievents/#event-type-mouseenterSummary
Make the event.composed property in mouseenter, mouseleave, pointerenter and pointerleave events "false" to be spec compliant and to fix interop gaps. Both the UI Events spec for Mouse Events and the Pointer Events spec define these events as non-composed. Both specs switched away from their original definitions few years ago: https://github.com/w3c/uievents/pull/210 https://github.com/w3c/pointerevents/pull/461 In addition to addressing the interop gap, this change also fixes an erroneous double/triple dispatch of these events to a shadow DOM host in Chromium when the shadow DOM also listens to the event (https://crbug.com/1136584).
Blink component
Blink>InputTAG review
NoneTAG review status
Not applicableRisks
Interoperability
This fixes a well-known interop gap.
Compatibility
The risk is negligible because Mozilla shipped the feature 5 years ago. Some prominent websites were updated back then, thanks to Mozilla's outreach (https://bugzilla.mozilla.org/show_bug.cgi?id=1478959). The compat risk is non-zero because Chromium has always dispatched these events as composed.
Gecko: Shipped/Shipping (https://bugzilla.mozilla.org/show_bug.cgi?id=1484371)
WebKit: Shipped/Shipping (https://bugs.chromium.org/p/chromium/issues/detail?id=1136584)
Web developers: Positive (https://crbug.com/1136584 --- this is a 5-star dev reported bug).
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Debuggability
No special change needed here: DevTools console and event listener breakpoints support investigating all event attributes.Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
YesIs this feature fully tested by web-platform-tests?
YesRequires code in //chrome?
FalseTracking bug
https://crbug.com/876994Sample links
https://codepen.io/mustaqahmed/pen/XWYZdYpEstimated milestones
| Shipping on desktop | 116 |
| Shipping on Android | 116 |
| Shipping on WebView | 116 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
NoneLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5073526551216128
Rick Byers
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAB0cuO73bus-BhZU1sxYhRQTAiwh5whzTwP4%2BsJcgUciAtxG7Q%40mail.gmail.com.
Chris Harrelson
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY8_2G%3DCAr%2BkDcz0ttx_eCsYxo-qbH%2BRUabsd-sinF2hZg%40mail.gmail.com.
Daniel Bratell
LGTM3
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9QNNGvW9aCG1bV1eFTiAyd05fFXtSVgwYo8AEgTre-Ug%40mail.gmail.com.