- From: Ryosuke Niwa <notifications@github.com>
- Date: Sun, 11 Sep 2022 13:35:29 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 11 September 2022 20:35:43 UTC
MutationObserver is a 10 year old API at this point. I don't think we can do (1) without causing some breakage. We definitely don't want to do (3) because mutation events still are a source of many security vulnerabilities in browser engines, and it's extremely expensive (i.e. hurt performance) to fire those events. > 1. Once a parent is removed from DOM, it can not have its children independently observed. Having per-element MOs allows that option. https://jsfiddle.net/epo8rhf2 What do you mean by this? Mutation observer can observe a node as long as you call `observe` function on it regardless of whether the node was a part of some other subtree or not. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1111#issuecomment-1243038123 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1111/1243038123@github.com>
Received on Sunday, 11 September 2022 20:35:43 UTC