Some preliminary clean-ups to our theming infrastructure
Categories
(Firefox :: Theme, task, P3)
Tracking
()
People
(Reporter: emilio, Assigned: emilio)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Bug 2003921 wants to force a particular window type to have a particular theme. For now, this theme is not overridable, but it will be in the future.
It would be easy to implement in LightWeightThemeConsumer, except for the fact that there's no great way of applying the theme data without the extensions code around.
I have some clean-ups that make doing this trivial-ish, and also should be better and less confusing. Right now the startup data for a theme contains a lot of duplicated data and this cleans it up while at it.
| Assignee | ||
Comment 1•1 day ago
|
||
No behavior change, this is just unused code.
| Assignee | ||
Comment 2•1 day ago
|
||
No behavior change. This is in preparation to be able to pull theme
data from a built-in manifest without involving instantiating an
extension, see bug 2003921 for context.
While at it, reduce the amount of startup data we store. lwtData already
includes the light / dark styles, and experiment too, so no need to store
them separately.
| Assignee | ||
Updated•18 hours ago
|
Comment 5•4 hours ago
|
||
| bugherder | ||
| Assignee | ||
Updated•12 minutes ago
|
Description
•