Consider allowing the '-moz-context-properties' property to be used by all WebExtension
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox57 | --- | wontfix |
People
(Reporter: jwatt, Assigned: emilio)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
Updated•7 years ago
|
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Comment 3•7 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
I was writing an extension today, and I
was a bit annoyed that the state of the art to support light and dark themes
means I need eigth (!) variants of each icon (disabled/enabled/hovered/active *
light/dark).
I'm not 100% sure it is worth it, both because of the concerns in the bug, and
because other browsers don't support this, and thus add-on developers that would
want their extension to work in every browser would still need to do the eigth
icons...
But I wrote it so I may as well submit it; your call whether we should take
this. There doesn't seem to be any progress on the alternatives both spec and
implementation-wise.
Updated•5 years ago
|
because other browsers don't support this, and thus add-on developers that would
want their extension to work in every browser would still need to do the eigth
icons...
Well, a lot of cross-platform extensions already handle a few use cases and I’m pretty sure it’s possible to use a fallback.
In my use case (Tab Center Reborn, but IIRC Tree Style Tab has the same problem with icons), the extension is already Firefox-only because it uses and needs APIs not available in other browsers, and it would make it easier for me to provide icons using the theme colors and so always readable and which feels native/quantum.
Updated•3 years ago
|
Comment 8•2 years ago
|
||
I think we can WONTFIX this, now that we have a working-group-approved approach that's being tracked in bug 1782815. (See https://github.com/w3c/csswg-drafts/issues/6988 / https://tabatkins.github.io/specs/svg-params/ ) That feature will address this use-case, so we won't need to address it via exposing this internal non-standard -moz-context-properties
hack.
(In fact, we'll plan to remove -moz-context-properties entirely as soon as we can, once we've got the new mechanism implemented and we've migrated our existing icons to use it. So we can consider this and any other associated bugs as "wontfix", in favor of the new thing, barring any showstopper-type stuff that we happen to run across in the meantime).
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•