Mutation Events (or rather, mutation observers) when we have Object.defineProperty getter/setters don't make the most sense. The getter/setter incur virtually no overhead, being baked into JS at the lowest possible level, compared to mutation observers, which are rather heavy hitting things for notifying non-owner objects of changes. Which is the difference here, too: defining getter/setter functions directly tied to the element's prototype and/or owning instance. While mutation observers are great for listening to "what's happening somewhere else", for attribute change handling by the owning element I'd much rather have getter/setter functionality available. - Mike On Fri, Apr 5, 2013 at 2:44 PM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Fri, Apr 5, 2013 at 7:39 PM, Travis Leithead > <travis.leithead@microsoft.com> wrote: > > By "we" do you mean Presto-now-Blink? I expect there's too much web > compat risk to remove Mutation Events anytime soon from a browser > implementation. > > By we I mean at least Gecko (to be perfectly clear, I'm not employed > by Opera), and like-minded folks at Apple and Google. > > > -- > http://annevankesteren.nl/ >
Received on Friday, 5 April 2013 18:58:21 UTC