Intent to Deprecate and Remove: Deprecate and remove: non-allowlisted Event interfaces from document.createEvent()

29 views
Skip to first unread message

Chromestatus

unread,
4:51 AM (6 hours ago) 4:51 AM
to blin...@chromium.org, soosu...@gmail.com, zi...@chromium.org
Contact emails
soosu...@gmail.com, zi...@chromium.org

Explainer
No information provided

Specification
https://dom.spec.whatwg.org/#dom-document-createevent

Summary
Remove support for creating non-allowlisted event interfaces from document.createEvent(). After this change, these will throw NOT_SUPPORTED_ERR as required by the specification.

Blink component
Blink>DOM

Web Feature ID
No information provided

Motivation
The DOM spec defines an allow-list for createEvent(), but Chrome also supports interfaces not on this list: - AnimationEvent - Usage : 0(https://chromestatus.com/metrics/feature/timeline/popularity/1162) - CloseEvent - Usage : 0(https://chromestatus.com/metrics/feature/timeline/popularity/1227) - ErrorEvent - Usage : 0(https://chromestatus.com/metrics/feature/timeline/popularity/1170) - IDBVersionChangeEvent - Usage : 0(https://chromestatus.com/metrics/feature/timeline/popularity/1201) - KeyboardEvents - Usage : 0.00003(https://chromestatus.com/metrics/feature/timeline/popularity/1228) - PageTransitionEvent - Usage : 0(https://chromestatus.com/metrics/feature/timeline/popularity/1174) - PopStateEvent - Usage : 0.000007(https://chromestatus.com/metrics/feature/timeline/popularity/1176) - TrackEvent - Usage : 0(https://chromestatus.com/metrics/feature/timeline/popularity/1186) - TransitionEvent - Usage : 0.012334(https://chromestatus.com/metrics/feature/timeline/popularity/1183) - WebGLContextEvent - Usage : 0(https://chromestatus.com/metrics/feature/timeline/popularity/1224) - WheelEvent - Usage : 0.000011(https://chromestatus.com/metrics/feature/timeline/popularity/1184) These interfaces lack init*Event() methods, making the created events unusable. Event constructors can be used instead (e.g., new AnimationEvent()).

Initial public proposal
No information provided

Debuggability
No information provided

Requires code in //chrome?
False

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

Estimated milestones
DevTrial on desktop146
DevTrial on Android146


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

This intent message was generated by Chrome Platform Status.

Yoav Weiss (@Shopify)

unread,
7:25 AM (4 hours ago) 7:25 AM
to Chromestatus, blin...@chromium.org, soosu...@gmail.com, zi...@chromium.org
I believe we'd need some more information about the compatibility and interoperability risks with this.

--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69982e7e.710a0220.1e5fb2.0081.GAE%40google.com.

David Baron

unread,
9:32 AM (2 hours ago) 9:32 AM
to Yoav Weiss (@Shopify), blin...@chromium.org, soosu...@gmail.com, zi...@chromium.org
It looks like all of the usage numbers are negligible (less than 1 in 2 million page loads, i.e., less than 0.00005%) except for TransitionEvent, which is around 0.01% of page loads (1 in ten thousand).  Do you know anything about the usage of TransitionEvent?  Is it for feature detection?

-David

Reply all
Reply to author
Forward
0 new messages