Hi! First of all, thanks for your interest!
I have no objections to the discussion points. I'll proceed as you suggested. Thanks! - Yeonghan 2026년 3월 5일 목요일 AM 1시 28분 11초 UTC+9에 Philip Jägenstedt님이 작성: > Hi Yeonghan, > > We discussed this in the API owners meeting today (present: Daniel, Yoav, > Chris, Vlad, Dan, Mike, Alex, me) and we think makes sense to remove these > in M148, without deprecation period: > > AnimationEvent > CloseEvent > ErrorEvent > IDBVersionChangeEvent > PageTransitionEvent > TrackEvent > WebGLContextEvent > PopStateEvent > WheelEvent > > The last two have non-zero usage, but it's still incredibly low. > > Please use a flag for this group so that we can revert it with Finch if > necessary. > > For KeyboardEvent, the risk seems slightly higher because it could be used > together with initKeyboardEvent() in old code, from the time that this was > the only supported way to create an initialize such events. > > For TransitionEvent, the usage is a bit high (~0.01%) so it makes sense to > be more careful. > > So, for KeyboardEvent and TransitionEvent, we'd like to see them > deprecated for 3 milestones before removal in M151. > > If you're happy with this approach, LGTM1. > > Best regards, > Philip > > On Tue, Mar 3, 2026 at 4:50 PM YeongHan Kim <[email protected]> wrote: > >> You are right. I think my previous explanation was insufficient and I >> apologize for the confusion. I have now updated chromestatus with more >> detailed information. >> >> In addition, events with 0 usage will be removed, and events with low >> usage but still carrying risk, including KeyboardEvents, will be deprecated >> without remove. >> >> The status and risk of each individual event are summarized in the sheet >> below. Please refer to it. >> >> Reference: >> https://docs.google.com/spreadsheets/d/1z3UP34xP0BDSOr5kINyMfBnPC1IdqrquJMtt806wuRM/edit?usp=sharing >> >> Thank you. >> >> 2026년 2월 26일 목요일 AM 1시 23분 18초 UTC+9에 [email protected]님이 작성: >> >>> What makes you say there's no initEvent? Eg. this code seems to work >>> today: >>> >>> let ke = document.createEvent("KeyboardEvent") >>> ke.initEvent("keydown") >>> ke.type >>> > 'keydown' >>> >>> Even with the low use counter, given that this works today I wouldn't be >>> surprised if some old Enterprise LOB app relies on this somewhere, in which >>> case we need to follow the process for making Enterprise-friendly >>> breaking changes >>> <https://www.chromium.org/developers/enterprise-changes/>. This used to >>> be the only way to create events, so unfortunately I don't think we can >>> consider this as zero compat risk. >>> >>> Rick >>> >>> On Fri, Feb 20, 2026 at 4:51 AM Chromestatus < >>> [email protected]> wrote: >>> >>>> *Contact emails* >>>> [email protected], [email protected] >>>> >>>> *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 >>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EDOM%22> >>>> >>>> *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 desktop 146 >>>> DevTrial on Android 146 >>>> >>>> *Link to entry on the Chrome Platform Status* >>>> https://chromestatus.com/feature/5095987863486464?gate=6283297569243136 >>>> >>>> This intent message was generated by Chrome Platform Status >>>> <https://chromestatus.com>. >>>> >>>> -- >>>> >>> 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/69982e7e.710a0220.1e5fb2.0081.GAE%40google.com >>>> >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69982e7e.710a0220.1e5fb2.0081.GAE%40google.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> 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/ac2cd874-344d-433a-9fcc-58b5f2bf8ae2n%40chromium.org >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ac2cd874-344d-433a-9fcc-58b5f2bf8ae2n%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > -- 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/546a41e6-8ab6-438e-ac58-263970f99261n%40chromium.org.
