[Webkit-unassigned] [Bug 241694] AX: Consider re-implementing aria-owns to reorder the accessibility tree (to match Gecko and the more recent implementation of Chromium)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=241694

Brennan Young <brennan.young at laerdal.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brennan.young at laerdal.com

--- Comment #6 from Brennan Young <brennan.young at laerdal.com> ---
Strong approval for making this happen. 

A possible side effect of basing the AX tree off the DOM tree will be that Webkit will have fewer quirks in relation to Gecko/Chromium. (Wishful thinking?).

I also assume that the original DOM location should be removed from the AX tree. I can't see any reason why the original location should be maintained, especially as the DOM reference will remain for cases that need it (e.g. CSS cascade).

Regarding the question of order/sequence. As an author, I would expect that aria-owns would cause the node to be appended to the end of the 'owner', and this would certainly be a viable mechanism for reordering (similar to appendChild in DOM). 

Not really sure how reordering might work otherwise.

The reverse order thing might have a use case that eludes me, but it seems counterintuitive.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220617/699d1786/attachment.htm>