1) compatibility and interoperability risks Firefox has removed all of them, and WebKit has removed all events except KeyboardEvents, PopStateEvent, and WheelEvent. Reference: https://wpt.fyi/results/dom/nodes/Document-createEvent.https.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&q=chrome%3A%21pass There have been previous discussions in Chromium: - https://groups.google.com/a/chromium.org/g/blink-dev/c/BkPSl0Oey8k/m/kZZ_GR9VAAAJ - https://groups.google.com/a/chromium.org/g/blink-dev/c/bj1SUohzcR4/m/5SXyG3kbBAAJ In summary, for interfaces without init*Event() methods, the recommendation is to use constructors instead of createEvent. Therefore, I believe it should be fine to deprecate and remove events that are not in the current spec [1] and have low usage. [1] https://dom.spec.whatwg.org/#dom-document-createevent 2) information on TransitionEvent usage I looked into some usage cases of TransitionEvent: - https://github.com/search?q=document.createEvent%28%27TransitionEvent%27%29%3B&type=code It appears that most usage is in Angular legacy code or older websites, and is mostly being used for feature detection. However, since the usage is above 0.01%, there seems to be some risk. So how about only deprecating TransitionEvent while removing the other events? Note that TransitionEvent is not currently in a deprecated state (no warning is shown when used). - yeonghan
-- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/699b2921.050a0220.5427a.002e.GAE%40google.com.
