Closed
Bug 1453035
Opened 7 years ago
Closed 7 years ago
--lwt-text-color fallback doesn't work
Categories
(Toolkit :: Themes, defect, P1)
Toolkit
Themes
Tracking
()
VERIFIED
FIXED
mozilla62
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox-esr60 | --- | unaffected |
firefox59 | --- | unaffected |
firefox60 | --- | unaffected |
firefox61 | + | verified |
firefox62 | --- | verified |
People
(Reporter: ntim, Assigned: Gijs)
References
Details
(Keywords: regression)
Attachments
(1 file)
Comment 1•7 years ago
|
||
Is someone still available to fix this?
status-firefox60:
--- → unaffected
status-firefox61:
--- → affected
Flags: needinfo?(jaws)
Keywords: regression
Priority: -- → P1
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → ntim.bugs
Flags: needinfo?(jaws)
Comment hidden (mozreview-request) |
Comment 3•7 years ago
|
||
mozreview-review |
Comment on attachment 8971176 [details]
Bug 1453035 - Fix textcolor theme fallback.
https://reviewboard.mozilla.org/r/239974/#review245714
::: toolkit/modules/LightweightThemeConsumer.jsm:27
(Diff revision 1)
> }],
> ["--lwt-text-color", {
> lwtProperty: "textcolor",
> processColor(rgbaChannels, element) {
> - if (!rgbaChannels) {
> + if (!rgbaChannels || rgbaChannels.a == 0) {
> element.removeAttribute("lwthemetextcolor");
So this means we could activate a lwtheme without setting --lwt-text-color and the lwthemetextcolor attribute. I don't think we want that.
::: toolkit/modules/LightweightThemeConsumer.jsm:33
(Diff revision 1)
> return null;
> }
> const {r, g, b, a} = rgbaChannels;
> const luminance = _getLuminance(r, g, b);
> element.setAttribute("lwthemetextcolor", luminance <= 110 ? "dark" : "bright");
> - element.setAttribute("lwtheme", "true");
> + return `rgba(${r}, ${g}, ${b}, ${a})`;
Can we just drop the alpha channel here?
Attachment #8971176 -
Flags: review?(dao+bmo) → review-
Updated•7 years ago
|
status-firefox59:
--- → unaffected
status-firefox-esr52:
--- → unaffected
status-firefox-esr60:
--- → unaffected
tracking-firefox61:
--- → +
Updated•7 years ago
|
Flags: needinfo?(dao+bmo) → needinfo?(jaws)
Reporter | ||
Comment 6•7 years ago
|
||
A newer version of this patch is in bug 1460287 (and fixes both this bug and bug 1460287). Thanks Gijs!
Assignee: ntim.bugs → gijskruitbosch+bugs
Flags: needinfo?(ntim.bugs)
Flags: needinfo?(jaws)
Assignee | ||
Comment 7•7 years ago
|
||
Fixed in bug 1460287.
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
Updated•7 years ago
|
Flags: qe-verify+
Reporter | ||
Comment 8•7 years ago
|
||
needinfo? myself to provide manual testing instructions
Flags: needinfo?(ntim.bugs)
Reporter | ||
Comment 9•7 years ago
|
||
Testing instructions:
1. create a webextension with:
"theme": {
"colors": {
"accentcolor": "orange",
"textcolor": "transparent",
},
}
in the manifest.
2. check that the text color is black and not transparent
Flags: needinfo?(ntim.bugs)
Comment 10•7 years ago
|
||
Following steps from comment 9 I reproduced this issue using Fx 61.0a1 (20180410100115)on Windows 10 x64.
I can confirm this issue is fixed, I verified using Fx 61.0 and Fx 62.0a1, on Windows 10 x64, mac os X 10.12.6 and Ubuntu 14.04 LTS.
Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•