Re: [whatwg/dom] `childList` records across multiple `MutationObserver`s are observed in fundamentally incorrect order (Issue #1111)

The one thing that was excellent about DOM Mutation Events is that reactions were always in order (in their case, because they were synchronous).

Going async is great, but maintaining order is also highly important, or else people get shot in the foot.

Custom Element `connected`/`attributeChanged`/`disconnectedCallback`s are synchronous. People write large apps with custom elements today, and they work fine, which proves that a synchronous event pattern can be as performant as custom element callbacks, differing for the most part only in API shape.



> I'm not sure if https://github.com/webqit/realdom resonates with the case here, but I often just want a realtime DOM mutations API so I built that.

Your work is excellent! I was thinking of patching DOM APIs to achieve that as well, but its a bit of work I haven't gotten to yet.

However now you you've built a library around this, I think I might just migrate to this.

I have some plans to implement styling for 3D WebGL elements and I think this will help a lot because it will guarantee that my code *just works* without strange ordering issues.

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

Message ID: <whatwg/dom/issues/1111/1868014238@github.com>