"Reload" button margins from Reduced page protection infobar are not visible in HCM on Windows
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox151 | --- | verified |
People
(Reporter: snegritas, Assigned: manuel)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
Found in
- 151.0a1(2026-04-09)
Affected versions
- 151.0a1(2026-04-09)
Tested platforms
- Affected platforms: Windows 10
Preconditions
- Set: privacy.reducePageProtection.infobar.enabled.pbmode to true
- Have High Contrast enabled at OS level.
Steps to reproduce
- Open a Private Brosing Window
- Navigate to https://www.pcgamer.com/games/rpg/borderlands-3-sometimes-felt-like-parody-of-itself-say-writers-but-4-aims-to-fix-that-if-i-tried-to-put-a-meme-in-the-game-he-would-come-to-my-house-with-a-baseball-bat/?__vfz=medium%253Dtray_notification#vf-e237d039-f241-47ef-bbcd-48108962ff73 and refresh once to trigger the Reduce page protection infobar.
- Observe the "Reload" button from the infobar
Expected result
- The "Reload" button margins are visible in the high contrast as the close button .
Actual result
- The "Reload" button margins from the infobar are not visible.
| Assignee | ||
Comment 1•2 months ago
|
||
I've previously constructed the in a non-default way due to having
trouble with getting the formatting working. This doesn't seem to be a
problem, so reverting to the pattern how it is meant to be done.
Updated•2 months ago
|
Comment 2•2 months ago
|
||
Comment on attachment 9571127 [details]
Bug 2030701 - Reduce Page Protection: Make strings in infobar captureable by screenreader r=#anti-tracking
Revision D294976 was moved to bug 2030652. Setting attachment 9571127 [details] to obsolete.
| Assignee | ||
Comment 3•2 months ago
•
|
||
Attaching screenshot of how it looks in Linux Gnome High Constrat Mode. Before / After for the infobar with the patch that I'm about to attach.
| Assignee | ||
Comment 4•2 months ago
|
||
Comment 6•2 months ago
|
||
| bugherder | ||
Updated•2 months ago
|
| Reporter | ||
Comment 7•2 months ago
|
||
Hello! I can confirm that the issue is fixed with firefox 151.0b6 on Windows 10
| Reporter | ||
Updated•2 months ago
|
| Assignee | ||
Updated•2 months ago
|
Description
•