Repository navigation
Focus-based navigation #1608
Description
We should implement next/prev (tab) and direction (d-pad) navigation of focusable controls, and ensure that everything is keyboard-accessible.
From http://developer.android.com/guide/topics/ui/accessibility/checklist.html:
Make sure users can navigate your screen layouts using hardware-based or software directional controls (D-pads, trackballs, keyboards and navigation gestures). In a few cases, you may need to make user interface components focusable or change the focus order to be more logical for user actions.
Activity
Hixie commentedon Feb 4, 2016
See also parts of http://developer.android.com/guide/topics/ui/accessibility/apps.html
jonahwilliams commentedon Aug 23, 2018
Is focus order the same as the traversal order? If so, we can simply reuse the semantics tree to handle focus traversal, with an additional focus state. Although I am concerned we would end up with two different concepts of focus.
cc @jslavitz
Hixie commentedon Aug 24, 2018
We can't use the semantics tree, it's not created if semantics are disabled.
jonahwilliams commentedon Aug 24, 2018
Turning on semantics when we detect tab navigation seems reasonable to me. The information needed to do focus based navigation is the same.
12 remaining items
gspencergoog commentedon Oct 9, 2019
#40186 had to be reverted :-( . Will close this again as soon as #42278 lands.
gspencergoog commentedon Oct 15, 2019
This has re-landed in #42278
andredealmei commentedon Dec 7, 2019
on web , tab not focus next textfield
dudeofawesome commentedon Feb 18, 2020
Tab focus also seems to not work on macOS builds on v1.15.4-pre.83
SimonAmpleman commentedon Feb 28, 2020
Android with external keyboard : When I press tab on the keyboard, it sometime jumps to the next field, sometime add a tab spacing in the field, and sometime add a tab spacing in the field and jump to the next field.
gspencergoog commentedon Feb 28, 2020
@SimonAmpleman, yes, this is a known issue that will be addressed. See #33521 for progress. Unfortunately, to fix this problem, it's a pretty big change. What's happening is because of two problems: there's no synchronous key handling, so we can't stop propagation of key events when an action handles them (and so the text field eventually gets them too), and there's not one source of truth for the state of a text edit, so editing updates are racy. These will both be addressed. I can't give an exact timeline, but they are a priority.
SimonAmpleman commentedon Feb 28, 2020
Timmmm commentedon Mar 8, 2021
Am I right in thinking that this adds best-guess automatic tab ordering? There doesn't seem to be any way to specify the tab order manually. I guess that's decent for simple apps but it can give pretty weird results:
flutter_tabs.mp4
We need a way to specify the tab order manually. Is there an issue for this already or should I open one?
gspencergoog commentedon Mar 8, 2021
@Timmmm No, we already have that. Check out FocusTraversalGroup and OrderedTraversalPolicy.
Timmmm commentedon Mar 10, 2021
FocusTraversalGroupworked perfectly and is very elegant and easy to use (like most things in Flutter). Nice one!github-actions commentedon Aug 4, 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.