Content illegible in High contrast mode on Windows

NEW
Unassigned

Status

()

2 years ago
2 years ago

People

(Reporter: simona.marcu, Unassigned)

Tracking

(Blocks: 1 bug, {access, regression})

Trunk
All
Windows
access, regression
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox49 unaffected, firefox50 disabled, firefox51 disabled, firefox52 disabled, firefox53 wontfix)

Details

Attachments

(1 attachment)

Created attachment 8802873 [details]
highContrast.mp4

[Affected versions]:
- Nightly 52.0a1

[Affected platforms]:
- Windows 10, Windows 7

[Prerequisites]:
Activate a high contrast theme.
- "Windows: Go to Personalize> Themes> Theme Settings and activate a High Contrast Theme.

[Steps to reproduce]:
1. Launch Firefox
2. Navigate to https://developer.mozilla.org/en-US/docs/Web/HTML
3. Press Ctrl+F to open the find bar
4. Search for anything present on the page (e.g "HTML")

[Expected result]:
- The searched term should be properly found and highlighted. 

[Actual result]:
- Only the matching terms are visible, the rest of the content is illegible. Please see the screen cast for more details.

[Regression range]:
Last good revision: dad39cae4473549bdf2677997f268541559a9b55
First bad revision: aa06902082204ca95b5d02790b44deb93910dfcf
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=dad39cae4473549bdf2677997f268541559a9b55&tochange=aa06902082204ca95b5d02790b44deb93910dfcf

[Additional notes]:
-This issue is not reproducible on Ubuntu.
Summary: Content illegible in High contrast mode → Content illegible in High contrast mode on Windows
status-firefox52: affected → disabled
status-firefox53: --- → affected
Dolske is this filed in the right component?
Flags: needinfo?(dolske)
Keywords: access
Yes. But the new find UI is still Nightly-only, and this correctly blocks the bug (1291278) for shipping it. So this doesn't need to be tracked, as we're not going to uplift any fix (because it's Nightly-only).
status-firefox53: affected → wontfix
Flags: needinfo?(dolske)
You need to log in before you can comment on or make changes to this bug.