[Webkit-unassigned] [Bug 194923] AX: Treat AXChildrenInNavigationOrder as AXChildren before adding support for aria-flowto

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 22 17:51:25 PST 2019


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

--- Comment #14 from Eric Liang <ericliang at apple.com> ---
shouldBeTrue("children0[i].role == children1[i].role"); I think should be enough to test that results from AXChildren and InNavOrder are the same?
(In reply to chris fleizach from comment #12)
> Comment on attachment 362772 [details]
> Patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=362772&action=review
> 
> >>> LayoutTests/accessibility/mac/children-in-navigation-order-returns-children.html:37
> >>> +        shouldBe("children1.length", "2");
> >> 
> >> I think the 2 children in this div might be the same role already. what if you added a button in here to ensure there were different objects
> > 
> > I picked the example where AppKit reorders. And the 2 children inside this link is 1) AXStaticText 2)Group that contains another AXStaticText
> > However in DRT, we don't have AppKit that reorders it. So instead, what we are really testing, in this test case, is that asking AXChildrenInNavigationOrder gives us a non-empty array.
> > I can also add another button just to make sure.
> 
> we also want to test that the result is the same for AXChildren and
> InNavOrder

-- 
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/20190223/60fad2af/attachment.html>


More information about the webkit-unassigned mailing list