Re: [whatwg/dom] MutationObserver needs an equivalent of disconnected & connected callbacks (#533)

@smaug you're right, that example is not directly related but it's something I can do already and it's based on MutationObserver. The `onconnected` is just a hint, imagining a list of added nodes per each record could be checked against `node.hasAttribute("onconnected")` and react accordingly.

That being said I wouldn't mind having a native `onconnected/disconnected` event in the DOM though but that's another story.

- - -

@rniwa 

> Due to security concerns, we can't fire blur synchronously in that case.

I am having hard time understanding why there wouldn't be security concern if `blur` can be intercepted through an observer ... what's the difference?

A focused node that never fires blur is a source of troubles. Mitigating troubles through other mechanism is a work around, not a solution to that issue.

Regardless, if that's the case you were looking for to justify connected/disconnected, I'm OK with it.

-- 
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/533#issuecomment-367604025