RE: MutationObserver does not observe state changes
Domenic Denicola <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <B4AE8F4E86E26C47AC407D49872F6F9F878933CD@BY2PRD0510MB354.namprd05.prod.outlook.com> |
From: Anne van Kesteren [[email protected]] > 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.