Closed
Bug 1905652
Opened 2 years ago
Closed 2 years ago
The user cannot selece the "Use custom settings for history" drop-down option from the browser preferences with keyboard navigation
Categories
(Firefox :: Keyboard Navigation, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1280511
| Tracking | Status | |
|---|---|---|
| firefox129 | --- | affected |
People
(Reporter: danibodea, Unassigned)
Details
(Keywords: access)
Note
- The user cannot choose the History dropdown option to "Use custom settings for history" using keyboard navigation.
Found in
- Nightly v129.0a1
Affected versions
- Nightly v129.0a1
Tested platforms
- Affected platforms: Windows 10, Ubuntu 22
- Unaffected platforms: MacOS 11
Steps to reproduce
Precondition: Use keyboard navigation!
- Launch the browser.
- Open browser preferences
- Search for "history"
- Tab down to the History section and select the "Nightly/Firefox will <<Remember history>>"
5.1 Press the Alt+Down hotkey to open the drop-down and attempt to select the "Use custom settings for history" option.
5.2 Press the Down arrow to select the 3rd option: "Use custom settings for history"
Expected result
- The user can select the "Use custom settings for history" option.
Actual result
- When selecting the 2nd option ("Never remember history"), a dialog to restart the browser is displayed, blocking the user from selecting the 3rd option ("Use custom settings for history").
Regression range
- Unknown.
Additional notes
- This issue occurs with and without a screen reader active.
- This issue does not occur while using mouse navigation.
- The dialog to restart should not trigger unless the user moved the focus away from the drop-down; Selection should only happen when moving the focus away from the combo-box.
- On Linux, the issue still reproduces if the user taps the DownArrow to select, but does NOT reproduce if the user manually opens the drop-down using the ALT+DOWN hotkey.
- This issue does NOT reproduce on MacOS since the drop-downs are opened by tapping DownArrow.
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•