Re: [whatwg/dom] Define mutation events (#305)

mfreed7 left a comment (whatwg/dom#305)

> > I have a couple of concerns given the existence of the "reverse origin trial":
> > 
> > * It's not transparent which websites continue to be able to use mutation events in Chromium. This makes it much harder for other browsers to remove mutation events before May 2025. E.g., while WebKit in theory could lean on `Quirks.cpp` without knowledge of what to fill it with it'd turn into a game of whack-a-mole. Also, Chromium has extended those deprecation deadlines in the past (e.g., with locking SharedArrayBuffer behind COOP+COEP, that might still be ongoing?).
> 
> This is a very good point. There are some sites using the origin trial, though not a ton. But I agree it might be the best to simply wait for the end of the OT before turning off mutation events in other browsers, to be safe.

I just wanted to check back in on this issue. Chromium has now successfully shipped the removal of the Mutation Events (deprecation) Origin Trial, in version 135, which went to stable Chrome this week. And I just landed the code to remove the enterprise policy also. At this point, the feature is disabled for all open web users of Chrome (and I believe Edge). So it should be safe to remove in other browsers now - please let me know if you run into any compat issues, since that would surprise me greatly.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/305#issuecomment-2779845660
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/305/2779845660@github.com>