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

The proposed disconnect option would also be useful to me — and a `flush()` method even moreso, for the reasons @WebReflection described. Every time I’ve ever used `takeRecords()`, it was specifically to do what `flush()` would do, and its absence presently necessitates keeping a common function reference around for both scenarios, which has seemed like awkward boilerplate.

(And yep: I’d also love an unobserve-specific-node-only method — though I imagine that would probably merit its own issue.)

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

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