Re: [aapi] ARIAAttrModified?

Me again.

Just an FYI that I still regularly hang out as 'davidb' on:
#accessibility on irc.mozilla.org
#wai-aria on irc.w3.org:6665

So if anyone wants to higher bandwidth discussion on anything related to
ARIA and especially browser implementation, please ping me. We need to
get some kind of consensus before moving forward on these kinds of
solutions.

cheers,
David

David Bolter wrote:
> Hi All,
>
> During some discussion over IRC yesterday Olli Pettay suggested that a
> performant way of implementing DOM attribute mutations might be to have
> separate but similar API to DOMAttrModified.
>
> Note DOMAttrModified would serve the same purpose, but having the
> browser create DOM mutation events for all mutations is going to slow
> the web experience.
>
> ARIAAttrModified is tabled as a way of only creating mutation events for
> aria attributes.
>
> Background: why do we need these mutations? In the case that an
> aria-attribute is modified, not by the web developer (perhaps through
> platform API), for
> example aria-sort is set to "true", the web developer is supposed to
> respond to that change (a dom attr mutation), and put his web
> application into a state that corresponds with the aria-sort="true"
> semantic.
>
> (see http://www.w3.org/Bugs/Public/show_bug.cgi?id=6653)
>
> If this is something we think is worthwhile, we should work with the
> DOM3 group to make it happen.
>
> cheers,
> David
>
>

Received on Thursday, 5 March 2009 19:52:15 UTC