Open
Bug 1347171
(themingapi-chrome)
Opened 8 years ago
Updated 2 years ago
Theming API - Google Chrome theme parity
Categories
(WebExtensions :: Themes, enhancement, P5)
WebExtensions
Themes
Tracking
(Not tracked)
NEW
People
(Reporter: mikedeboer, Unassigned)
References
(Depends on 5 open bugs, Blocks 2 open bugs, )
Details
(Whiteboard: epic, triaged)
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.
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Blocks: themingapi-in-content
Updated•8 years ago
|
webextensions: --- → ?
Updated•8 years ago
|
webextensions: ? → ---
Updated•7 years ago
|
Priority: -- → P5
Updated•7 years ago
|
Alias: themingapi-chrome
Updated•7 years ago
|
No longer blocks: themingapi-in-content
Updated•7 years ago
|
No longer depends on: themingapi-framework
Comment 1•7 years ago
|
||
mass move of existing themes bugs to new WebExtensions: Themes component
Component: WebExtensions: Frontend → WebExtensions: Themes
Comment 2•7 years ago
|
||
Comprehensive list of what chrome supports: https://cs.chromium.org/chromium/src/chrome/browser/themes/browser_theme_pack.cc?l=232&rcl=9a5ca91778f04309cb6982697ae80a2fc89fd94b
Updated•7 years ago
|
Blocks: webextensions-chrome-gaps
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•