Open
Bug 1459504
Opened 6 years ago
Updated 2 years ago
Allow changing the content area background/text colors
Categories
(WebExtensions :: Frontend, enhancement, P3)
WebExtensions
Frontend
Tracking
(Not tracked)
NEW
People
(Reporter: ntim, Unassigned)
References
Details
Selectors it should target:
- #tabbrowser-tabpanels (depends on bug 1440865)
- #customization-container
- ???
+ in-content pages (can be a separate bug, since that work depends on bug 1444459)
Use case: create a full dark theme and reduce the amount of white as much as possible.
The properties can be called: colors.content_area and colors.content_area_text.
Since the built-in dark theme uses a different background for #tabbrowser-tabpanels and #customization-container, it might be worth creating different properties for the customize mode, not sure.
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Comment 1•6 years ago
|
||
(In reply to Tim Nguyen :ntim from comment #0)
> Use case: create a full dark theme and reduce the amount of white as much as
> possible.
Themes generally can't access web content, and that's where this default background mostly matters.
I believe the main use case here is extensions making web content dark. We can probably provide an API tailored for that, independently from webextension themes.
Component: Themes → Frontend
Priority: P3 → --
Reporter | ||
Updated•6 years ago
|
No longer blocks: themingapi-more-ui
Updated•6 years ago
|
Component: Frontend → Themes
Priority: -- → P3
Comment 2•6 years ago
|
||
See comment 1 for why this should not be part of the theming API.
Component: Themes → Frontend
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•