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

> I am not complaining as I saw this coming so I am just curious: while developers should stay away from long time deprecated features, I wonder why potentially huge breaking changes like this would ship when most people are on vacation or planning to ... if you were looking for causing troubles, you surely nailed the worst time after Xmas ... is there any rationale for picking this time around? 🤔

I suppose a bit later in the year might have been slightly better. But my rationale was simply that I [published a blog post announcing the removal](https://developer.chrome.com/blog/mutation-events-deprecation) in ~June of 2023, and I also added loud deprecation messages in Chrome around the same time. I wanted to give "plenty of time" for folks to see that messaging, so they weren't surprised. And "1 year" sounded like "plenty of time" without being so long that people dismissed it as too far into the future, so I chose June/July of 2024. I'm not sure there's ever a great time to do something like this, really. And again, I've so far been pleasantly surprised by the lack of major issues. Sorry if you ran into issues resulting from this removal!



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

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