6653 2009-03-05 15:46:53 +0000 [ARIA 2.0] How should web devs monitor attribute changes? 2013-03-22 18:04:28 +0000 1 1 1 Unclassified ARIA Core AAM 1.0 PC All RESOLVED FIXED P3 normal Last Call 1 dbolter dbolter andi.snowweaver bugs m_a_s_7 rayrayray111 aria-ua-impl oldest_to_newest 24055 0 dbolter 2009-03-05 15:46:53 +0000 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. 24724 1 dbolter 2009-04-14 19:28:02 +0000 For those with access, please note: http://www.w3.org/WAI/PF/Group/track/issues/201 24898 2 dbolter 2009-04-22 01:20:05 +0000 I'm not sure if this is a priority, since I'm not convinced of the use cases yet. It really boils down to whether we think AT will make use of setting ARIA attributes to drive DHTML behaviour. I personally would like WAI-ARIA to provide state information passively, and I don't expect web authors to list for ARIA attr dom mutation, or to handle them appropriately. 25554 3 andi.snowweaver 2009-06-12 15:09:39 +0000 Might discuss with aria-activedescendent or in section 4 on Managed states. Best Practices Guide discusses so we probably should address in UAIG. 30534 4 andi.snowweaver 2010-01-05 15:16:04 +0000 Not something the AAPI group can solve. Needs to be taken up by the DOM events group. David to contact them. 30547 5 dbolter 2010-01-05 18:21:38 +0000 Hmm, okay so I spoke to a DOM guy and he suggested we should define our own event if we need it. 30982 6 andi.snowweaver 2010-01-12 16:39:13 +0000 So what's the next step David? Is this something the API owners have to do? 30987 7 dbolter 2010-01-12 17:31:25 +0000 This bug isn't high priority for browsers that already implement DOMAttrModified. (http://www.quirksmode.org/dom/events/) Also: it is only really necessary to make aria-activedescendant more usable by web developers; where an alternative for them is to poll in js. 31023 8 dbolter 2010-01-13 20:46:33 +0000 Interesting: http://www.w3.org/2008/webapps/wiki/Selector-based_Mutation_Events 31667 9 andi.snowweaver 2010-02-09 16:51:31 +0000 See e-mail thread on DOMAttrModified being deprecated starting at: http://lists.w3.org/Archives/Member/w3c-wai-pf/2010JanMar/0084.html 31668 10 andi.snowweaver 2010-02-09 16:52:14 +0000 See e-mail thread on DOMAttrModified being deprecated starting at: http://lists.w3.org/Archives/Member/w3c-wai-pf/2010JanMar/0084.html 51388 11 dbolter 2011-07-22 19:47:32 +0000 Olli, any news on this topic? I've not followed it. 84864 12 dbolter 2013-03-22 18:04:02 +0000 https://developer.mozilla.org/en-US/docs/DOM/MutationObserver 84865 13 dbolter 2013-03-22 18:04:28 +0000 https://developer.mozilla.org/en-US/docs/DOM/MutationObserver