RE: MutationObserver does not observe state changes

From: Anne van Kesteren [annevk@annevk.nl]

> Given that this internal state is a per-node affair, I'm not sure we can provide a coherent API.

Well, as long as such state is exposed via changing properties, I think `Object.observe` is the ideal coherent API. But that's obviously a ways out, and yes, until then I guess we can just keep adding events everywhere.

Thanks, I think the tree-modification vs. internal state distinction was important, and for me at least clarifying.