Repository navigation
RangeSlider needs alternative input method for NavigationMode.directional #181968
Description
Use case
Before PR #181525, RangeSlider has no keyboard support at all
After PR #181525 is merged (which adds keyboard support to RangeSlider), there will be a UX issue in NavigationMode.directional mode: arrow keys will immediately control slider values, conflicting with their primary purpose of navigating between UI elements.
According to Flutter documentation in directional navigation mode, arrow keys should primarily navigate between controls, not manipulate values
Proposal
RangeSlider should require explicit activation (like pressing Enter/Select) to enter an "edit mode" where arrow keys control the slider values. When not in edit mode, arrow keys should navigate to other focusable elements.
This issue requires design discussion to determine the best UX pattern for editing RangeSlider values in directional navigation mode
Activity
chunhtai commentedon Feb 11, 2026
we probably need to test the native behavior first.
chunhtai commentedon Mar 2, 2026
asking internally, internal only link: yaqs/8123832921288081408
chunhtai commentedon Mar 3, 2026
material team suggest the following
For controller (e.g., TV remotes, gamepads):
By default, DPAD arrow keys only move focus between views.
Pressing the Enter key will toggle into a "value adjustment mode." While in this mode, the DPAD keys will control the slider value using the same logic as the alphabetic keyboard type (Left/Right for horizontal, Up/Down for vertical).
Pressing Enter again will exit the value adjustment mode, returning DPAD keys to focus navigation.
[material_ui] Add alternative input method for `RangeSlider` in `Navi…
github-actions commentedon Oct 2, 2026
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.