Closed Bug 1192037 Opened 4 years ago Closed 4 years ago

Import settings from Microsoft Edge

Categories

(Firefox :: Migration, defect, P3)

defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox42 --- affected

People

(Reporter: Dolske, Unassigned)

References

(Blocks 1 open bug)

Details

We need a migrator that can import a user's existing Edge settings. (In migrator-speak, these would be various browser settings/preferences.)

As a first step we should see what's involved and how difficult it is, this migrator is likely less important to users than other data types.
Edge's settings are fairly spartan (swidt?), so the list of things a user might want imported to Firefox is fairly short.

- Zoom
Edge has a global zoom level exposed at the top of their menu panel. We only really expose a per-site zoom level, so this doesn't map well to Firefox. (I think we have a hidden global setting, requires broader discussion we want to expose that.) Also, oddly Edge seems to default the zoom level to the Windows monitor scaling, which seem like a terrible idea. (My Surface Pro screen is at 150% scaling, and so edge defaults everything to 150% -- 100% is ridiculously tiny.)

- Light (default) / Dark theme
We don't really support this, but could activate a simple black LWT?

- Showing the Favorites bar (defaults to off)
This would be showing our bookmark toolbar

- Open with start page (default) / new tab page / previous pages / specific page
These closely match our existing settings. Although our "start page" is a much simpler about:home.

- Open new tabs with top sites (default) / top + suggested content / blank page
This is just about:newtab vs a blank tab. We don't have a "suggested content" flavor. (Which is the user's news feed, appended to the bottom of Edge's usual "top sites" page.

- Reading view style (default / light / medium / dark)
This can map to our Reader View style for sepia / light / sepia / dark. (We don't have an equivalent to "medium", which is a light grey in Edge)

- Reading view font size (S / M / L / XL)

Edge defaults to Medium for me. Not sure what exact Reader View zoom the other should map to.


Under Advanced Settings are more:

- Show the home button (off by default)
- Block popups (on by default)
- Use Adobe Flash (on by default)
- Always use caret browsing (off by default)
- Offer to save passwords (on by default)
- Send Do Not Track (off by default)
- Have Cortana assist me in Edge (on by default)
- Search in the address bar with $SEARCH_ENGINE (Bing by default)
- Show search suggestions (on by default)
- Block cookies 
  Don't block (default), Block all, Block only 3rd party
- Let sites save protected media licenses (on by default)
- Use page prediction (on by default)
- SmartScreen filter sites/downloads (on by default)


We should carefully consider which (if any!) of the these settings we want to import... The problem with importing things is that some users may have these things hijacked, or set to values that cause problems (cookie blocking being the most obvious), and so if they're trying to switch to Firefox we don't want to offer the same broken experience. Or the reason the user disabled something in Edge might not apply to Firefox.

I don't think we should import any of the Advanced settings. These are seldom going to be changed, and I'd expect a user who considers these things important to be going through Firefox's prefs after the migration anyway.
Flags: needinfo?(gijskruitbosch+bugs)
Flags: needinfo?(gijskruitbosch+bugs)
Priority: -- → P3
I've looked into the homepage here, which I think is arguably the most important out of all the non-advanced prefs.

Frustratingly, it seems like:
1) there were open registry keys that we use for IE
2) as of IE11 and maybe IE10, I don't think those even work anymore, though I've not checked. They use an opaque binary registry key that I don't know how to read
3) there are APIs for IE11 to:
  - check if your homepage is X
  - ask the user to set their homepage to X
... but apparently not to just ask "what is the user's homepage?"

4) Edge and IE definitely do not share a homepage preference, so that kind of moots most of that.
5) Edge has the same kind of unreadable binary registry key
6) I've verified that that gets written to if you change your homepage

Considering that the registry itself is in a folder that indicates you are not under any circumstances allowed to mess with it (https://twitter.com/gijskruitbosch/status/631763783636123649 , https://twitter.com/gijskruitbosch/status/631763994869633024 ), I wouldn't be surprised if the value was encrypted. (yes, I found that a while back - I was looking for History at the time, so since the reading list patch was written I've been looking at this / other ways of determining the home page.

Considering how hard MS makes it to change your homepage in Edge to anything other than the default about:start page, or MSN or Bing (something like 5 clicks to get to an input box where you can do that), I'm not sure how much time I should spend on trying to figure out anything else about that registry key...

Of course, if other people have found API information to retrieve this value, that would be quite useful!



At least some of the other settings seem to still be under 'Main' in the key HKCU\SOFTWARE\Classes\Local Settings\(...)\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge... I mostly spotted the home button one, I'll have to try and look for the other stuff (writing this on my mac).
(In reply to :Gijs Kruitbosch from comment #2)
> I've looked into the homepage here, which I think is arguably the most
> important out of all the non-advanced prefs. [...]

I'm starting to lean towards just WONTFIXing this whole bug. The homepage and search engine do seem like things a user would be more interested in having carry over (assuming they customized them). But they're also the things that, historically, tend to be hijacked the most. (I will be pessimistic and assume malware will still find a way around Edge's protections).

In any case, as with most of these settings, they're easy to change in Firefox. That, plus the general risk of users users switching to Firefox _because_ their IE settings are messed up, makes me think we just shouldn't attempt to do this without some careful user-research that the gains outweigh the risks...
(In reply to Justin Dolske [:Dolske] from comment #3)
> (In reply to :Gijs Kruitbosch from comment #2)
> > I've looked into the homepage here, which I think is arguably the most
> > important out of all the non-advanced prefs. [...]
> 
> I'm starting to lean towards just WONTFIXing this whole bug. [...]

That sounds fair to me, let's do it.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
(In reply to Justin Dolske [:Dolske] from comment #3)
> (In reply to :Gijs Kruitbosch from comment #2)
> > I've looked into the homepage here, which I think is arguably the most
> > important out of all the non-advanced prefs. [...]
> 
> I'm starting to lean towards just WONTFIXing this whole bug. The homepage
> and search engine do seem like things a user would be more interested in
> having carry over (assuming they customized them). But they're also the
> things that, historically, tend to be hijacked the most.

Verdi pointed out this morning that our migrator actually asks the user if they want to use their migrated page or Firefox's. So I went ahead and filed bug 1200849 for specifically migrating just the homepage.
You need to log in before you can comment on or make changes to this bug.