Open
Bug 1427435
Opened 7 years ago
Updated 2 years ago
Allow changing the background tab hover text color and background color
Categories
(WebExtensions :: Frontend, enhancement, P5)
WebExtensions
Frontend
Tracking
(Not tracked)
NEW
People
(Reporter: ntim, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [design-decision-needed] [needs-follow-up])
Add the ability to style the hover background and text color of background tabs.
something like:
colors/background_tab_hover
colors/background_tab_hover_text
Updated•7 years ago
|
Component: WebExtensions: General → WebExtensions: Frontend
Reporter | ||
Updated•7 years ago
|
Summary: Allow changing the background tab hover color and background color → Allow changing the background tab hover text color and background color
Updated•7 years ago
|
Priority: -- → P5
Comment 1•7 years ago
|
||
Hi Tim, this has been added to the agenda for the January 23, 2018 WebExtensions APIs triage meeting. Would you be able to join us?
Here’s a quick overview of what to expect at the triage:
* We normally spend 5 minutes per bug
* The more information in the bug, the better
* The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details
Relevant Links:
* Wiki for the meeting: https://wiki.mozilla.org/WebExtensions/Triage#Next_Meeting
* Meeting agenda: https://docs.google.com/document/d/1Mc0h5OVd30WBjCORssdifZRXYQrk6WcTqX1cw6ADO9k/edit#
* Vision doc for WebExtensions: https://wiki.mozilla.org/WebExtensions/Vision
Updated•7 years ago
|
Depends on: dark-theme-darkening
Updated•7 years ago
|
Blocks: dark-theme-darkening
No longer depends on: dark-theme-darkening
Comment 2•7 years ago
|
||
Adding features like this isn't free, e.g. it adds complexity for our "brighttext" detection. Please explain why we should do this.
Comment 3•7 years ago
|
||
Hey Tim and Jaws, I'm needinfo'ing you for a response to Dao's comment above. :) This is currently on hold for a design decision.
Flags: needinfo?(ntim.bugs)
Flags: needinfo?(jaws)
Reporter | ||
Comment 4•7 years ago
|
||
(In reply to Dão Gottwald [::dao] from comment #2)
> Adding features like this isn't free, e.g. it adds complexity for our
> "brighttext" detection. Please explain why we should do this.
Theme developers want this (an example is the FT Deep Dark theme).
Flags: needinfo?(ntim.bugs)
Comment 5•7 years ago
|
||
I agree that this makes our brighttext detection code more difficult. I wonder if we can sidestep that by requiring that either both background_tab_hover and background_tab_hover_text are set or neither.
Hmmm... but this might make our [brighttext] CSS selector more complicated to write since we might not want it to apply on hovered tabs when the variables are set.
Until I see a proof-of-concept patch I'm not convinced we should do this.
Flags: needinfo?(jaws)
Comment 7•7 years ago
|
||
(In reply to Tim Nguyen :ntim from comment #4)
> (In reply to Dão Gottwald [::dao] from comment #2)
> > Adding features like this isn't free, e.g. it adds complexity for our
> > "brighttext" detection. Please explain why we should do this.
>
> Theme developers want this (an example is the FT Deep Dark theme).
When we dropped support for full themes in favor of a simpler model, it was clear that there would be no feature parity. There are things that full themes could do that the theming API won't support. At the same time, theme developers would obviously prefer to be able customize the look freely, so our goals are a bit at odds. The mere fact that there's some demand is not enough to get features added to the API.
Updated•7 years ago
|
Whiteboard: [design-decision-needed] → [design-decision-needed] [needs-follow-up]
Comment 8•7 years ago
|
||
One thing making the cost/benefit ratio a bit more favorable is that this could also be useful to extensions beyond themes; that's bug 1320585.
See Also: → 1320585
To expand and make more flexible the standard bar for the different needs of all kinds of developers it seems to me more complicated than just giving the ability to create/replace additions to your custom css+html panel anywhere in the browser.
For example, when using horizontal tabs tabs, me a very important multiline. But FF57+ when creating multiline via userChrome.css lost the ability to sort the tabs using drag and drop on the second and subsequent rows. This, again, further development and support. It is easier to take a third-party addition and modify it yourself, than to constantly refer to the support.
Updated•7 years ago
|
Assignee: ntim.bugs → vivek3zero
Updated•7 years ago
|
Assignee: vivek3zero → ntim.bugs
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Reporter | ||
Updated•6 years ago
|
No longer blocks: dark-theme-darkening
Reporter | ||
Updated•6 years ago
|
Assignee: ntim.bugs → nobody
Comment 10•5 years ago
|
||
Anything new? Default firefox themes change background tab color on hover so why don't give developers and theme creators ability to do this?
Comment 11•5 years ago
|
||
You can easily observe this on light theme (on default and dark it's very subtle).
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•