Migrate fission.autostart to StaticPrefList.yaml to make it available in the compositor process
Categories
(Core :: Preferences: Backend, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: hsivonen, Assigned: hsivonen)
References
Details
Attachments
(1 file)
To enable bug 1574089, fission.autostart should be in StaticPrefList.yaml.
Can StaticPrefList.yaml represent prefs that are locked in beta or release?
Comment 1•6 years ago
|
||
Can
StaticPrefList.yamlrepresent prefs that are locked in beta or release?
No. In the long-term this capability should be added.
For now, if you keep the entry in all.js with the locked attribute, and also add an entry to the YAML file, I think it will work the way you want. But I would test it carefully, because it's not a well-tested configuration.
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Comment 3•6 years ago
|
||
(In reply to Nicholas Nethercote [:njn] from comment #1)
For now, if you keep the entry in
all.jswith thelockedattribute, and also add an entry to the YAML file, I think it will work the way you want. But I would test it carefully, because it's not a well-tested configuration.
OK. The patch here seems to work.
| Assignee | ||
Updated•6 years ago
|
Comment 5•6 years ago
|
||
| bugherder | ||
Comment 6•6 years ago
|
||
Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
Description
•