Re: [whatwg/dom] MutationObserver observed element removal (#779)

I think I see what you mean ; you could just have node connected/disconnect events as you do on custom elements - which'd likely be useful in many ways and possibly cover some of what's being discussed in #533..

but this would depend (presumably) on addEventListener which can be overridden by the page code. 

If I was developing a tracking blocker say, this implementation would allow the page to circumvent the user's attempt to manage tracking related nodes. whereas events on the MutationObserver are (currently) outside of the page developer's control - there is a case for MutationObservers to get this info outside of the typical page access to the same information.

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