W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2013

RE: MutationObserver does not observe state changes

From: Domenic Denicola <domenic@domenicdenicola.com>
Date: Wed, 31 Jul 2013 15:35:53 +0000
To: Anne van Kesteren <annevk@annevk.nl>, Rafael Weinstein <rafaelw@google.com>, Adam Klein <adamk@chromium.org>
CC: Bradley Meck <bradley.meck@gmail.com>, "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <B4AE8F4E86E26C47AC407D49872F6F9F878933CD@BY2PRD0510MB354.namprd05.prod.outlook.com>
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.
Received on Wednesday, 31 July 2013 15:37:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:03 UTC