Open Bug 1339962 Opened 7 years ago Updated 2 years ago

ContextualIdentity API color isn't a css color

Categories

(WebExtensions :: Frontend, defect, P5)

Product:
WebExtensions
Component:
Frontend
Type:
defect

Tracking

(firefox54 affected, firefox57 fix-optional)

Tracking Flags:
Tracking Status
firefox54 --- affected
firefox57 --- fix-optional

People

(Reporter: andy+bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [contextualIdentities], triaged) 

In bug 1339610 comment 2 it was pointed out that the contextualIdentity color from the API is something like "blue". But that isn't the exact colour used in the visual identity. You can see an example of this here:

https://github.com/mdn/webextensions-examples/pull/179
Summary: ContextualIdentity API colour isn't a css colour → ContextualIdentity API colour isn't a css color
Summary: ContextualIdentity API colour isn't a css color → ContextualIdentity API color isn't a css color
Priority: -- → P5
Whiteboard: [contextualIdentities] → [contextualIdentities], triaged
Has there been any movement on theme colours at all? I'm hesitant to hardcode these colours due to visibility issues with themes.

Our test pilot also changes the shade of blue slightly etc. There is also a slight difference between text colour and icon colour for visibility purposes however I suspect we can ignore that.

The other issue with these colours is they might clash with extensions colours themselves, I'm not really sure how to suggest mitigating that.

Is there an ability to expose css custom properties to web extensions? Would that get messy if they wanted to do something in a content script?

At least with colour names... the extension author can actually fix these issues, granted it is still horrible.
Product: Toolkit → WebExtensions
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.