You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
a11y traversal order top left to bottom right not always giving great results #12187
I would expect SHRINE to come after the back button. However, the shipping cart button's bounding box has its top higher than the SHRINE title and is therefore traversed first in the current top left to bottom right approach.
I think this is what Android uses. It looks like they basically do left to right, top to bottom, but then allow the developer to move object hierarchies around by saying "this tree goes before this one" or "this tree goes after this one" in the traversal order. They prioritize the "goes before" setting over the "goes after" setting (so "goes after" doesn't happen if "goes before" exists).
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
goderbauer commentedon Sep 27, 2017
As an idea to make this better: we could see if we can find out how Android defines traversal order for native apps.
gspencergoog commentedon Oct 13, 2017
I think this is what Android uses. It looks like they basically do left to right, top to bottom, but then allow the developer to move object hierarchies around by saying "this tree goes before this one" or "this tree goes after this one" in the traversal order. They prioritize the "goes before" setting over the "goes after" setting (so "goes after" doesn't happen if "goes before" exists).
Adding semantics traversal order support (#4540)
Hixie commentedon Mar 7, 2018
For the AppBar specifically, let's just use our ordering API to set the order correctly.
goderbauer commentedon Mar 7, 2018
Similar bug for tab bar: #14375
github-actions commentedon Aug 16, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.