1610985 - Hide the Microsoft Edge Legacy migrator when the browser isn't accessible to users

Status: NEW

(Firefox :: Migration, defect, P2)

Description

[Matthew N. [:MattN]]

(Quoting Matthew N. [:MattN] from bug 1608513 comment #4)

There's not an easy way to support all the possible configurations (Legacy Edge, side-by-side [SxS], and new Edge) on all Windows versions we support. I think the simplest path is to rename the legacy migrator to "Microsoft Edge Legacy" on all Windows versions. This may cause some confusion for users who are still migrating from it and don't have the Chromium Edge but I'm not sure addressing that is worth the complexity/time.

One thing that probably wouldn't be hard to implement would be hiding the legacy migrator when the application is hidden from the user. Unfortunately the registry key mentioned at https://docs.microsoft.com/en-us/deployedge/microsoft-edge-sysupdate-access-old-edge#how-operating-system-os-changes-are-triggered (SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}\BrowserReplacement) doesn't exactly match the one set on my Windows 10 VM (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}\BrowserReplacement) so I think we should ask Microsoft how best to detect when Microsoft Edge Legacy should be hidden.

Mike, should I join the Microsoft-Mozilla mailing list or would you prefer to send an email asking how to detect when the old Microsoft Edge is hidden (due to the new Edge being installed without SxS mode) on Windows 7 - 10? Thanks

Comment 1

[Mike Taylor [:miketaylr]]

Let me invite you to the list, it's probably useful for you in the future at some point as well.

Comment 2

[Matthew N. [:MattN]]

Attachment: Bug 1610985 - Return chromium-edge instead of edge from getMigratorKeyForDefaultBrowser, when available. r=Gijs

Comment 3

[Matthew N. [:MattN]]

I just attached an old patch to prefer the new Edge for the default browser selection upon import. I didn't look more into the core issue of this bug.