Re: Deprecation of DOMAttrModified (Was: DOMActivate vs. Activation Behavior) from James Craig on 2010-02-10 (public-hypertext-cg@w3.org from January to March 2010)

From: James Craig <jcraig@apple.com>
Date: Tue, 09 Feb 2010 17:20:49 -0800
To: Sean Hogan <shogun70@westnet.com.au>
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" <public-hypertext-cg@w3.org>
Message-id: <5542AC76-0712-4475-85EB-C53E346C5496@apple.com>

On Feb 9, 2010, at 3:46 PM, Sean Hogan wrote:

> 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?

Even if DOMAttrModified wasn't threatened with deprecation and was implemented consistently across all major browsers, it would still require additional implementation on the part of a screen reader, but no screen reader dev team is going to waste time implementing a feature at relies on a deprecated event model.

Received on Wednesday, 10 February 2010 01:21:13 UTC