Open
Bug 1399259
Opened 7 years ago
Updated 2 years ago
WebExtension popup difficult to read if the desktop environment uses a dark OS theme
Categories
(WebExtensions :: Frontend, defect, P3)
Tracking
(firefox57 wontfix)
NEW
Tracking | Status | |
---|---|---|
firefox57 | --- | wontfix |
People
(Reporter: arnaud.jacquemin+bugzilla, Unassigned)
References
Details
(Keywords: nightly-community)
Attachments
(3 files)
When I use a dark theme on my desktop environment, I can't read the texts in the popups opened by browser actions icons, because the text color is dark on a dark background.
This happens independently of the Firefox theme I'm using.
It looks like the text color is hard-coded to #222426 (dark grey) by a rule in chrome://browser/content/extension.css (I used the add-on debugger to inspect the text using this trick : https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Debugging#Debugging_popups)
The background color of the popup seems to be set by the desktop environment (GTK3 theme on Linux) because it changes if I change the desktop theme.
I think the default text color of the extension's popup should follow the main text color of the desktop environment.
Keywords: nightly-community
Updated•7 years ago
|
Component: Theme → WebExtensions: Frontend
Product: Firefox → Toolkit
Summary: WebExtension popup difficult to read if the desktop environment uses a dark theme → WebExtension popup difficult to read if the desktop environment uses a dark gtk theme
This bug is not specific to Linux : here is a screenshot of the same issue using a dark (OS) theme on Windows 7.
Updated•7 years ago
|
Summary: WebExtension popup difficult to read if the desktop environment uses a dark gtk theme → WebExtension popup difficult to read if the desktop environment uses a dark OS theme
Updated•7 years ago
|
OS: Linux → All
Hardware: Unspecified → All
Updated•7 years ago
|
Priority: -- → P3
Comment hidden (advocacy) |
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•