This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From 7/13/09 ARIA TF meeting: (James Craig) Browser developer will have to provide source text. Follow along wording of text equivalent computation.
July 22, F2F in Boston: Should go in error handling discussion. Don't get stuck in a loop. Track id of every node you visit. If you come back to one you've already visited, you stop. If get to an id that doesn't exist, stop at the last one. ARIA TF July 13th minutes: http://www.w3.org/2009/07/13-pf-minutes.html
Don't want a child to be a parent of itself - makes tree walking take forever. IE changes the accessible tree based on ARIA-OWNS. FF and Apple disagree. Probably have diverging implementations - need to research what each browser is doing, develop some test cases, and determine how big this issue is
*** Bug 8421 has been marked as a duplicate of this bug. ***
Related to issue 379: http://www.w3.org/WAI/PF/Group/track/issues/379 David and Cynthia to bring this to the ARIA TF.
Options are: * take the text "the structure should be reflected in the accessible tree as directed by aria-owns." out of the spec and say nothing. * have different mappings for MSAA-only and UIA and a different mapping for IAccessible2. David, which do you prefer?
(In reply to comment #5) > Options are: > > * take the text "the structure should be reflected in the accessible tree as > directed by aria-owns." out of the spec and say nothing. > * have different mappings for MSAA-only and UIA and a different mapping for > IAccessible2. > > David, which do you prefer? > I prefer the first, removing that sentence.
in MSAA column, "if MSAA-only, modify the tree. If MSAA plus an API that supports relationships, don't modify the tree