Closed
Bug 2041836
Opened 1 month ago
Closed 1 month ago
Design tokens with nativeTheme values have Nova overrides ignored
Categories
(Toolkit :: Themes, defect, P3)
Toolkit
Themes
Tracking
()
RESOLVED
FIXED
153 Branch
| Tracking | Status | |
|---|---|---|
| firefox153 | --- | fixed |
People
(Reporter: mstriemer, Assigned: mstriemer)
References
(Blocks 1 open bug)
Details
(Whiteboard: [recomp])
Attachments
(1 file)
Design tokens that have a pre-Nova nativeTheme value are having their Nova overrides ignored. This is because without the nativeTheme key set we treat the token as always being set, but if there's a nativeTheme value then we give the light/dark/default value precedence over the foundation value
Copying the pre-Nova nativeTheme value in when it's present should fix this at Figma import time, although we could likely do something when building the CSS instead (and potentially avoid defining the nativeTheme value twice)
Updated•1 month ago
|
| Assignee | ||
Comment 1•1 month ago
|
||
This causes the value from Figma to be set for the browser theme when
necessary. We could potentially avoid some duplication by instead doing
this at CSS export time.
Pushed by mstriemer@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/5c5f41a25d8f
https://hg.mozilla.org/integration/autoland/rev/e9b3ee7b2465
Set nativeTheme values for Nova design tokens r=jooliver,desktop-theme-reviewers,akulyk,emilio,thecount
Comment 3•1 month ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 month ago
status-firefox153:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 153 Branch
Updated•29 days ago
|
QA Whiteboard: [qa-triage-done-c154/b153]
You need to log in
before you can comment on or make changes to this bug.
Description
•