Disable the legacy Edge migrator
Categories
(Firefox :: Migration, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox152 | --- | fixed |
People
(Reporter: mconley, Assigned: adylanmclamb, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug, Whiteboard: [lang=js])
Attachments
(1 file)
Before we do a removal, we can start by disabling the Edge Legacy migrator by default. This migrator is controlled via browser.migrate.edge.enabled.
Comment 1•1 month ago
|
||
Is this actionable today? Should/could it be a mentored bug?
| Reporter | ||
Comment 2•1 month ago
|
||
I got the go-ahead from Ania to start with disablement. I'll go ahead and mark this as mentorable.
Hello interested contributor! This should be a very straight-forward bug, involving a default pref flip. Mainly, we aim to flip this value to false: https://searchfox.org/firefox-main/rev/23974e2d947e31e4ae42ae2758a4416c9a6d8671/browser/app/profile/firefox.js#2725
We'll also want to re-enable it for these two tests by adding this line below each Edge test entry here and here
prefs = ["browser.migrate.edge.enabled=true"]
And finally, we'll need to re-enable the migrator for this test, by adding this to the top of the test file, after the "use strict" line:
add_setup(async () => {
// The EdgeHTML Edge migrator is disabled by default.
await SpecialPowers.pushPrefEnv({
set: [["browser.migrate.edge.enabled", true]],
});
});
| Assignee | ||
Comment 3•1 month ago
|
||
Updated•1 month ago
|
Comment 5•1 month ago
|
||
| bugherder | ||
Updated•11 days ago
|
Description
•