[Windows] Keyboard navigation order is not honored in the WebRTC Permission Panel
Categories
(Toolkit :: PopupNotifications and Notification Bars, defect, P3)
Tracking
()
People
(Reporter: tbabos, Unassigned)
References
Details
Attachments
(1 file)
32.08 KB,
video/mp4
|
Details |
Tested on:
Nightly 89.0a1
Tested Platforms:
Windows 7/10
Have the following prefs enabled (optional)
browser.proton.enabled
browser.proton.doorhangers.enabled
Steps to reproduce:
- Open https://mozilla.github.io/webrtc-landing/gum_test.html
- Click on the Camera or Microphone button
- Check the Permission Panel -> navigate within it using the Tab and Alt+Tab combination
Expected Results:
The focus order should follow the visual order of elements, as it is also mentioned in Figma doc, Accessibility Notes: https://www.figma.com/file/FjUe6ORvXZgJvI3rPuTV33/Desktop-UI-(Mozilla-Confidential-)?node-id=4%3A1
Actual Results:
The "Block" button is focused before the "Allow" one.
Notes:
Note that this is also reproducible on the old UX (ex: Release 86 - "don't allow is focused before "allow") but it should be fixed - or adapted for Windows - if we were to follow the logic stated in Figma.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Removing Proton door hanger flag since this is not a Proton regression.
Comment 2•3 years ago
|
||
On Linux this works as expected. I'm assuming it has something to do with how we flip the button order on Windows.
I can also reproduce this behavior with other PopupNotifications (e.g. addon installation) so I'm moving it to Toolkit.
Is this perhaps expected behavior, because we always want to move focus to the cancel option first?
Updated•3 years ago
|
Updated•9 months ago
|
Description
•