- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 9 Feb 2010 17:26:44 -0800
- To: James Craig <jcraig@apple.com>
- Cc: Sean Hogan <shogun70@westnet.com.au>, David Bolter <david.bolter@gmail.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" <public-hypertext-cg@w3.org>
On Tue, Feb 9, 2010 at 5:20 PM, James Craig <jcraig@apple.com> wrote: > 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. They don't need to. They just need to set the attribute and rely on the fact that the browser will send *some* type of notification to the page. What that notification is currently varies between browsers, and likely will change at some point in the future, but that doesn't affect what the screen reader needs to do. / Jonas
Received on Wednesday, 10 February 2010 01:27:50 UTC