Firefox screenshots preview image is barely visible in Windows high contrast mode
Categories
(Firefox :: Screenshots, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | affected |
firefox94 | --- | wontfix |
firefox95 | --- | wontfix |
firefox96 | --- | wontfix |
firefox97 | --- | fix-optional |
People
(Reporter: emilghitta, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [screenshots-extension])
Attachments
(1 file)
(deleted),
image/png
|
Details |
Affected versions
- Firefox 96.0a1 (BuildId:20211125214104)
- Firefox 95.0b12 (BuildId:20211125185815)
- Firefox 94.0.2 (BuildId:20211119140621)
- Firefox 91.3.0esr (BuildId:20211028170545)
Affected platforms
- Windows 10 64bit.
Preconditions:
- Enable high contrast themes from Windows system settings.
Steps to reproduce
- Launch Firefox.
- Access the following link.
- Right click on the page and select the "Take Screenshot" context menu option.
- Click the "Save full page" option.
Expected result
- The screenshot preview image is successfully displayed.
Actual result
- The screenshot preview image is barely visible.
Regression Range
This seems to be a regression.
Possible regressor: Bug 1667887
Reporter | ||
Comment 1•3 years ago
|
||
Hi falgunimst95,
It seems that mozregression pointed out Bug 1667887 for causing this regression.
Can you please take a look?
Thank you!
Updated•3 years ago
|
Updated•3 years ago
|
Comment 2•3 years ago
|
||
The solution here is likely to be different for the browser component implementation in bug 1696573, but in the meantime it would be good to get a fix for this. Patches welcome.
Updated•3 years ago
|
Comment 3•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:sfoster, since the bug has recent activity, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•2 years ago
|
||
This isn't reproducible with the in-progress Screenshots browser component (bug 1696573). We'd accept a patch to fix this in the extension.
Updated•2 years ago
|
Description
•