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

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

From: Joseph Scheuhammer <clown@utoronto.ca>
Date: Tue, 09 Feb 2010 17:19:53 -0500
Message-ID: <4B71DF89.5010307@utoronto.ca>
To: Jonas Sicking <jonas@sicking.cc>
CC: James Craig <jcraig@apple.com>, 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 09/02/10 4:43 PM, Jonas Sicking wrote:
> It does however strike me as scary that AT is modifying web pages and
> expecting web pages to react to these modifications.

It's "worse" than that.  The a11y api that the user agent uses to 
communicate with the AT allows for getting and setting states.  Thus, 
even if the AT wasn't directly changing the dom, it could do so 
indirectly through the a11y api.  In call chain pseudo code:

- AT uses a11y api to set the sort order on some object:  
object.setSortOrder('ascending');
-- user agent sets the aria-sort to 'ascending' on the relevant dom element.

Without DOMAttrModified, the web app is completely unaware that the 
sort-order for that element has changed.

-- 
;;;;joseph

'Clown control to Mao Tse Tung.'
  - D. Bowie (misheard lyric) -
Received on Tuesday, 9 February 2010 22:20:34 GMT

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