- From: Frederik Wessberg <notifications@github.com>
- Date: Sun, 27 Apr 2025 16:41:09 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 27 April 2025 23:41:13 UTC
wessberg left a comment (whatwg/dom#533) @trusktr Whether to design a synchronous or asynchronous solution has been a discussion point and likely one of the main reasons why we haven't been able to move forward in any direction so far. I for one have argued for an _asynchronous_ approach, partly because we know from the past how `MutationEvents` was shipped and later unshipped from browsers due to concerns among browser implementers about their synchronous nature. There are several reasons why observing the connectedness of any node is not trivially solves with mutation observers, in part because a Node may move between roots in the DOM tree. Listening for changes to child lists across every existing and future Shadow Root in the document just to track a Node is not ideal, and at least my primary motivation for wanting to see this eventually being solved by observing the node itself. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/533#issuecomment-2833697895 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/533/2833697895@github.com>
Received on Sunday, 27 April 2025 23:41:13 UTC