Add typography design tokens
Categories
(Toolkit :: Themes, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox119 | --- | fixed |
People
(Reporter: jules, Assigned: jules)
References
(Blocks 1 open bug)
Details
(Whiteboard: [recomp])
Attachments
(8 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
We should add our remaining font sizes, and our font weights under in-content typography tokens in design-tokens-brand.css
.
We've had teams ask for our standard type scale, so we should host the remaining source of truth in tokens so that everyone can have access to our type scale, and avoid unique type styling decisions in-content.
Since there are a few inconsistencies in heading size application between preferences.css
, common-shared.css
, activity-stream.css
, firefoxview.css
, protections.css
, and therefore no standard, we've been following the in-content type scale set by preferences.css
:
Heading 1: 1.46rem (~22px)
Heading 2: 1.14rem (~17px)
Font weights needed:
Heading 1 styling uses 300, Heading 2 uses 600, and our default font weight is 400.
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D182115
Assignee | ||
Comment 3•2 years ago
|
||
Depends on D186031
Assignee | ||
Comment 4•2 years ago
|
||
Depends on D186032
Assignee | ||
Comment 5•2 years ago
|
||
Depends on D186033
Assignee | ||
Comment 6•2 years ago
|
||
Depends on D186034
Assignee | ||
Comment 7•2 years ago
|
||
Depends on D186035
Assignee | ||
Comment 8•2 years ago
|
||
In part 1, I am helping standardize our line heights, and this has affected our text based inputs and buttons. I am proposing we stick to a standard of 28px
for the min-height of small buttons. Both the line height and min-height changes has affected how buttons display on the Infobar, per Tim's review in part 1. In this change I do some small tweaks to make sure the Infobar supports a 28px
tall small button. The button changes are a consequence of the line height typography tokens. Since we have a few different heights going on that slightly fluctuate between values, I figured I'd help standardize our button and small button heights. The small button min-height change, which is applicable to this part, improves the accessibility of our buttons due to28px
being a bigger hit target than the button on the Infobar today, 24.5px
Depends on D186036
Comment 10•2 years ago
|
||
Backed out for dt failure on browser_styleeditor_fission_switch_target.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/feb01960f7e10a66b10928129bf6e623142eee16
Log link: https://treeherder.mozilla.org/logviewer?job_id=429684668&repo=autoland&lineNumber=6550
Comment 11•2 years ago
|
||
Comment 12•1 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3e70bbbc530d
https://hg.mozilla.org/mozilla-central/rev/12661dcdb47e
https://hg.mozilla.org/mozilla-central/rev/bace4dd5c836
https://hg.mozilla.org/mozilla-central/rev/8709a5dc0358
https://hg.mozilla.org/mozilla-central/rev/db2a07894d25
https://hg.mozilla.org/mozilla-central/rev/d7c87724e11c
https://hg.mozilla.org/mozilla-central/rev/776274de26bb
https://hg.mozilla.org/mozilla-central/rev/77fcb77e6acc
Assignee | ||
Updated•1 years ago
|
Updated•1 year ago
|
Description
•