Open Bug 1987677 Opened 8 months ago Updated 1 month ago

[meta] Tokenize the chrome

Categories

(Toolkit :: Themes, task, P3)

task

Tracking

()

People

(Reporter: jules, Unassigned)

References

(Depends on 4 open bugs, Blocks 2 open bugs)

Details

(Keywords: meta, Whiteboard: [recomp][acorntractors])

With more coverage of design tokens in the chrome, we can continue investing on this infrastructure for handling modes (light/dark/high contrast) and theming (addon/lightweight, OS, light/dark).

Goal

  1. Tokenize (use design tokens on) stylesheets that belong to the chrome
  2. Make sure design tokens play well with theme variables

Plan

  1. Identify variables (panels, menus, toolbar, toolbar buttons, tabs) from chrome css files that should be pulled into design tokens
    a. Identify all locations that variable is used
    b. Identify its purpose
    c. Integrate it into the design tokens system
    d. Add documentation on how it is intended to be used (where do we put docs?)
    e. Replace all uses with the token
  2. Lint under toolkit/themes/shared, browser/themes/shared, browser/components, browser/themes/shared/<operating system> for design token opportunities
  3. Integrate theme variables with design tokens
  4. Tokenize the theme_experiment object
  5. Add documentation
Depends on: 1952566
Depends on: 1987439
Summary: [Meta] Tokenize the chrome → [meta] Tokenize the chrome
Depends on: 1988296
Depends on: 1988809
Depends on: 1998564
Depends on: 2008598
Depends on: 2003084
Depends on: 2009061
Blocks: 2028894
Depends on: 2017983
Depends on: 2029958
You need to log in before you can comment on or make changes to this bug.