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

> It's worth noting that the [removal of mutation events](https://chromestatus.com/feature/5083947249172480) has shipped in Chrome 127 thanks to @mfreed7. While there is [an enterprise policy](https://chromeenterprise.google/policies/#MutationEventsEnabled) that we expect to support for at least 9 months (and there have been a bunch of bugs that ended with telling folks that they need to use the enterprise policy to keep their apps working until those apps can be fixed), the removal seems so far to be sticking.

Knock on wood! 😄  But yeah, so far the removal is going cautiously well. It only very recently (last 48 hours) reached 100% of stable users, and it sometimes takes a few days for bugs to trickle back to me. I'll try to check back in here after a few more weeks with a more definitive status update. But assuming that's successful, I'd strongly advocate for this issue being closed as "WontFix". There are also a few mentions of mutation events in the spec (e.g. https://html.spec.whatwg.org/#concept-document-fire-mutation-events-flag) that should likely be deleted.

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

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

Received on Wednesday, 31 July 2024 16:35:46 UTC