ContextualIdentity API color isn't a css color

NEW
Unassigned

Status

()

Toolkit
WebExtensions: Frontend
P5
normal
3 months ago
8 days ago

People

(Reporter: andym, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---

Firefox Tracking Flags

(firefox54 affected)

Details

(Whiteboard: [contextualIdentities], triaged)

(Reporter)

Description

3 months ago
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

Updated

3 months ago
Priority: -- → P5
Whiteboard: [contextualIdentities] → [contextualIdentities], triaged
Blocks: 1191418
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.
You need to log in before you can comment on or make changes to this bug.