Parity here means that we support at least the same set of theme manifest properties that Google Chrome supports internally. This includes legacy theme properties that Chrome still supports. Properties that don’t have a canonical equivalent in Firefox will be supported as dummies; they’re there, but don’t apply any styling change. To reach parity, user stories blocking this epic need to be resolved.
mass move of existing themes bugs to new WebExtensions: Themes component
Component: WebExtensions: Frontend → WebExtensions: Themes
Comprehensive list of what chrome supports: https://cs.chromium.org/chromium/src/chrome/browser/themes/browser_theme_pack.cc?l=232&rcl=9a5ca91778f04309cb6982697ae80a2fc89fd94b
You need to log in before you can comment on or make changes to this bug.