W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2010

Re: Deprecation of DOMAttrModified (Was: DOMActivate vs. Activation Behavior)

From: Sean Hogan <shogun70@westnet.com.au>
Date: Wed, 10 Feb 2010 10:46:22 +1100
Message-ID: <4B71F3CE.4040608@westnet.com.au>
To: James Craig <jcraig@apple.com>
CC: David Bolter <david.bolter@gmail.com>, Jonas Sicking <jonas@sicking.cc>, Doug Schepers <schepers@w3.org>, "w3c-wai-pf@w3.org PF" <w3c-wai-pf@w3.org>, "www-dom@w3.org" <www-dom@w3.org>, public-hypertext-cg@w3.org
On 10/02/10 8:37 AM, James Craig wrote:
> On Feb 9, 2010, at 1:03 PM, David Bolter wrote:
>
>    
>> That said, I'm not sure if this pattern is used a lot today.
>>      
> As far as I'm aware, it's not used at all today, because there isn't a way to implement it.
>
>    

Currently IE has onpropertychange and Firefox / Opera have DOMAttrModified.
Aren't they sufficient?

>
> On Feb 9, 2010, at 1:03 PM, David Bolter wrote:
>
>    
>> Hi Jonas,
>>
>> The idea is that AT can (through API) cause the modification of an attribute, and the web developer should have a standard way to tell that modification happened (without js timer/polling). For example perhaps visual focus changes (aria-activedescedant). That said, I'm not sure if this pattern is used a lot today.
>>
>> cheers,
>> David
>>      
Received on Tuesday, 9 February 2010 23:47:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:04 GMT