W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: Mutation events replacement

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 8 Jul 2011 11:05:41 -0700
Message-ID: <CAAWBYDBXmnBE=Furbcf48sMdqY88t9x3pVMGsEWbJP25kQHw8w@mail.gmail.com>
To: Sean Hogan <shogun70@westnet.com.au>
Cc: Jonas Sicking <jonas@sicking.cc>, John J Barton <johnjbarton@johnjbarton.com>, Olli@pettay.fi, Rafael Weinstein <rafaelw@google.com>, Aryeh Gregor <Simetrical+w3c@gmail.com>, Adam Klein <adamk@google.com>, Anne van Kesteren <annevk@opera.com>, Webapps WG <public-webapps@w3.org>
On Fri, Jul 8, 2011 at 6:55 AM, Sean Hogan <shogun70@westnet.com.au> wrote:
> On 8/07/11 10:21 PM, Sean Hogan wrote:
>> - ARIA support in JS libs currently involves updating aria-attributes to
>> be appropriate to behavior the lib is implementing. Attribute mutation
>> listeners would allow an inverse approach - behaviors being triggered off
>> changes to aria-attributes.
>
> As has been mentioned, listening for attribute mutations is horrendously
> inefficient because your handler has to receive every mutation, even if only
> interested in one attribute.

This is a limitation of current mutation events.  We don't have to
repeat this mistake.  Allowing a script to listen for changes to a
specific attribute is a big low-hanging fruit.

~TJ
Received on Friday, 8 July 2011 18:06:37 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:46 GMT