Bug 1347171 (themingapi-chrome)

Theming API - Google Chrome theme parity

NEW
Unassigned

Status

P5
normal
2 years ago
5 months ago

People

(Reporter: mikedeboer, Unassigned)

Tracking

(Depends on: 5 bugs, Blocks: 2 bugs)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: epic, triaged, URL)

(Reporter)

Description

2 years ago
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

2 years ago
Depends on: 1347182
(Reporter)

Updated

2 years ago
Depends on: 1347184
(Reporter)

Updated

2 years ago
Depends on: 1347188
(Reporter)

Updated

2 years ago
Depends on: 1347190
(Reporter)

Updated

2 years ago
Blocks: 1347201

Updated

2 years ago
webextensions: --- → ?

Updated

2 years ago
webextensions: ? → ---

Updated

a year ago
Priority: -- → P5
Alias: themingapi-chrome
(Reporter)

Updated

a year ago
Depends on: 1415878
No longer blocks: 1347201
No longer depends on: 1330335
No longer depends on: 1387582
No longer depends on: 1347184
No longer depends on: 1347190
No longer depends on: 1426686

Comment 1

10 months ago
mass move of existing themes bugs to new WebExtensions: Themes component
Component: WebExtensions: Frontend → WebExtensions: Themes
Blocks: 1161828

Updated

5 months ago
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.