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 17:03:58 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>, "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <B4AE8F4E86E26C47AC407D49872F6F9F87893E56@BY2PRD0510MB354.namprd05.prod.outlook.com>
Right, firing change records on everything affected is definitely a no-go; thanks for the clear illustration. Maybe just certain properties should be called out as observable (i.e. change records will be fired for them). The motivation would be to eliminate the plethora of "xchanged" events we keep introducing into specs, in favor of a centralized mechanism. So the cost of adding such change-record--firing code would be the same as the cost of maintaining such events.

Received on Wednesday, 31 July 2013 17:04:32 UTC

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