Re: [whatwg/dom] `mutationObserver.disconnect({ flush: true })` (Issue #1283)

I actually wonder if this might be something we could simply fix. Code that follows the pattern in my first comment won't break, it will simply take the records before `disconnect()` is called. And the rest is already broken — I'd wager it's highly unlikely that code depends on pending records _not_ being taken.

If not, another solution is to introduce a _different_ method, and deprecate `disconnect()`. Though this is a conventional name at this point that other observers share too…

@annevk What do you think?

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

Message ID: <whatwg/dom/issues/1283/2392866729@github.com>