Double border on keyboard navigation for Search Engine Switcher engines in Alpenglow theme
Categories
(Toolkit :: Themes, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox152 | --- | wontfix |
| firefox153 | --- | verified |
| firefox154 | --- | verified |
People
(Reporter: phorea, Assigned: daisuke)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression)
Attachments
(3 files)
Notes
Reproduces also when Nova is enabled.
Found in
- Firefox 154.0a1
Affected versions
- Firefox Nightly 154.0a1;
- Firefox 153 beta 4;
- Firefox 152.0.3 RC.
Tested platforms
- Affected platform: Windows 11, Ubuntu 24, macOS 15;
- Unaffected platforms: N/A;
Steps to reproduce
- Go to about:addons > Themes and enable Alpenglow theme
- Open Search Engine Switcher from address bar
- Use Down arrow to navigate between the listed search engines
Expected result
- Uncertain what the expected result is: Before bug 1998985, hover and keyboard navigation on search engines from Search Mode Switcher had the same visual effect. Now, the keyboard navigation displays a border. If this is expected, Alpenglow should not have a double border. Otherwise, keyboard selection should have the same effect as hover, with a slightly different color.
Actual result
- Alpenglow theme for all platforms and System Default theme - Ubuntu display a double border on keyboard selection.
Regression range
Comment 1•22 days ago
|
||
:mbeier, since you are the author of the regressor, bug 1998985, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•19 days ago
|
Updated•19 days ago
|
Updated•10 days ago
|
Updated•10 days ago
|
Updated•10 days ago
|
| Assignee | ||
Comment 2•9 days ago
|
||
Hi Dão!
I looked into this one. The focus ring here is shown via :focus-visible. In panel-item.css we only set outline-offset and none of the other outline properties, so outline-style ends up as auto.
https://searchfox.org/firefox-main/rev/a07b2cb8ff33387a81968a7ed9d59ebdc4dad607/toolkit/content/widgets/panel-list/panel-item.css#47-49
For auto, Theme intentionally draws a two-tone double ring (PaintAutoStyleOutline: an inner 2px stroke plus an outer 1px stroke).
https://searchfox.org/firefox-main/rev/a07b2cb8ff33387a81968a7ed9d59ebdc4dad607/widget/Theme.cpp#1323-1332
It uses the accent color, but Alpenglow doesn't specify one, so the default colors are used (primary: blue, secondary: white). That's why it shows up like this here.
So, this might not really be a bug, but rather intentional behavior. How do you think we should handle it?
FWIW, setting outline-style to solid gives single white line border with this theme.
Comment 3•9 days ago
|
||
Thanks Daisuke, I also just looked into it but could not figure out why it didn't respect the outline-color property.
Comment 4•9 days ago
|
||
(In reply to Daisuke Akatsuka (:daisuke) from comment #2)
Hi Dão!
I looked into this one. The focus ring here is shown via
:focus-visible. Inpanel-item.csswe only setoutline-offsetand none of the other outline properties, sooutline-styleends up asauto.
https://searchfox.org/firefox-main/rev/a07b2cb8ff33387a81968a7ed9d59ebdc4dad607/toolkit/content/widgets/panel-list/panel-item.css#47-49
auto is a safe default for the web, erring on the side of making sure it's visible. We don't need that here. I think outline: var(--focus-outline); outline-offset: var(--focus-outline-inset); should do the trick?
| Assignee | ||
Comment 5•8 days ago
|
||
Thank you very much, Moritz and Dão!
(In reply to Dão Gottwald [:dao] from comment #4)
I think
outline: var(--focus-outline); outline-offset: var(--focus-outline-inset);should do the trick?
Okay, I will try it.
| Assignee | ||
Comment 6•8 days ago
|
||
Updated•8 days ago
|
Comment 8•6 days ago
|
||
| bugherder | ||
Comment 9•5 days ago
|
||
The patch landed in nightly and beta is affected.
:daisuke, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox153towontfix.
For more information, please visit BugBot documentation.
Updated•4 days ago
|
Comment 10•4 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D311469
Updated•4 days ago
|
Comment 11•4 days ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Recent cosmetic regression from bug 1998985
- Code covered by automated testing?: no
- Fix verified in Nightly?: yes
- Needs manual QE testing?: yes
- Steps to reproduce for manual QE testing: see comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: Trivial CSS fix
- String changes made/needed?: none
- Is Android affected?: no
Updated•4 days ago
|
Updated•4 days ago
|
Updated•4 days ago
|
Comment 12•4 days ago
|
||
| uplift | ||
Reproducible on a 2026-06-26 Firefox Nightly build on Windows 11.
Verified as fixed on Firefox Nightly 154.0a1 on Windows 11, macOS 13, Ubuntu 24.
Verified as fixed on Firefox 153.0b13 (treeherder build) on Windows 11, macOS 13, Ubuntu 22.
Description
•