[Bug 13669] Indicating batch changes to the DOM

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13669

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WORKSFORME

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-05 15:40:08 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: no spec change
Rationale: 

Even with the mutation events as they are now, so long as the accessibility
tool waits for the event loop to spin, it's sufficient. This is actually
already defined in the spec: the event loop specifically says that UI is only
updated on step 5, between tasks.

Now if the issue is that a script is updating things in multiple tasks, then
that's covered by the ARIA live region feature. You would just turn the updates
in the region off for a while.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Friday, 5 August 2011 15:40:09 UTC