Closed
Bug 1818208
Opened 2 years ago
Closed 2 years ago
The CBH doorhanger's buttons cannot be targeted using keyboard navigation
Categories
(Firefox :: Messaging System, defect)
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | unaffected |
| firefox111 | --- | affected |
| firefox112 | --- | affected |
People
(Reporter: ppop, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
988.09 KB,
image/gif
|
Details |
[Affected versions]:
- Firefox Beta 111.0b4 (Build ID 20230221190142)
- Firefox Nightly 112.0a1 (Build ID 20230221212648)
[Affected platforms]:
- Windows 10 x64
- macOS 12.5
- Ubuntu 22.04 x64
[Prerequisites]:
Have the following preferences set:
- cookiebanners.service.mode set to 1
- cookiebanners.service.mode.privateBrowsing set to 1
- cookiebanners.ui.desktop.cfrVariant set to 1
- cookiebanners.ui.desktop.enabled set to true
- cookiebanners.service.detectOnly set to true
[Steps to reproduce]:
- Open the browser with the profile from prerequisites.
- Navigate to a website with cookie banners (e.g. cnn.com).
- Press the "Tab" key to cycle between the selectable elements.
[Expected result]:
- The CBH doorhanger's buttons are selected and can be pressed.
[Actual result]:
- The CBH doorhanger buttons cannot be selected.
[Notes]:
- The issue is also reproducible when pressing the F6 key to highlight the address before cycling between the elements with the "Tab" key.
- Attached a screen recording of the issue:
Comment 1•2 years ago
|
||
Not a platform bug. Moving to messaging system, please correct if that's not the right component.
Component: Privacy: Anti-Tracking → Messaging System
Product: Core → Firefox
| Reporter | ||
Comment 2•2 years ago
|
||
After further investigation, it appears that the doorhanger can be focused after pressing the "F6" key twice, and the buttons can be targeted with the "ALT+N"/"ALT+R" combinations. I will close this issue as Resolved: WORKSFORME.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•