Open Bug 1163644 (edge-migration) Opened 5 years ago Updated Last year

Data importers/migrators for Microsoft Edge browser

Categories

(Firefox :: Migration, defect, P2)

Unspecified
Windows 10
defect

Tracking

()

Tracking Status
firefox39 + wontfix
firefox38.0.5 --- wontfix
firefox40 + wontfix
firefox41 - affected

People

(Reporter: phlsa, Unassigned)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: [windows10])

Our import wizard on Windows currently doesn't show Microsoft Edge/Spartan as an option. It should really be in there, potentially at the very top.
Component: General → Migration
Blocks: windows-10
Tracking for 39 and 40 from discussion on release-drivers about possible uplift of support for Windows 10.
So, rumors say Win10 could be released in july, users will take at least one month before building data they might be interested into migrating (basically they have to use Edge for at least one month and decide they don't like it), that pushes the date to August, more realistically September.
Having a migrator for Firefox 41 (released on 22nd of September) should cover vast majority of use-cases.
(In reply to Marco Bonardo [::mak] from comment #2)
> So, rumors say Win10 could be released in july, users will take at least one
> month before building data they might be interested into migrating
> (basically they have to use Edge for at least one month and decide they
> don't like it), that pushes the date to August, more realistically September.
> Having a migrator for Firefox 41 (released on 22nd of September) should
> cover vast majority of use-cases.

I'll circle back with Philipp and Dolske, but I agree that the data importer seems like a feature we can hold off on until we assume our users have some data and are migrating over.
At first glance, the bookmarks from Edge/Spartan are shared with IE and stored in the same directory in the profile folder.

History, cookies, and settings are the other data types we currently import and I didn't look much at them yet.
Are you looking at the older build? Edge has different bookmarks from what IE has for me.
I'm running the version with Windows 10 TP.
Please try with the latest "Insider" Preview (no longer TP). The latest build is 10130.
Spartan's favorites is under Spartan APPX's data folder.  I don't know the package folder name is kept even if RTM.

%HOME%/AppData/Local/Packages/Microsoft.Windows.Spartan_cw5n1h2txyewy/AC/Spartan/User/Default/Favorites
Edge is a universal app so it acts a lot like metro apps do. I'd bet that this directory can be difference per machine: 'Microsoft.Windows.Spartan_cw5n1h2txyewy'

IMO we shouldn't waste any time on this bug. There are far more serious issues on win10 to deal with.
Changing to P3 after discussion -- this will be important to do eventually, but it's not critical to have immediately for the Windows 10 release. Worst case until this is we import a slightly-stale version of the user's IE data (if they've been using Edge, and if it stays separate).
Priority: P1 → P3
OK. Glad to know this isn't going to block release. Marking wontfix for 39.
A documented way to get a folder for AppContainer (or a Metro app or a universal app) is the GetAppContainerFolderPath function:
https://msdn.microsoft.com/en-us/library/windows/desktop/hh448543%28v=vs.85%29.aspx
The DeriveAppContainerSidFromAppContainerName function will return an app container sid from an AppContainerName (or a "Moniker") such as "Microsoft.Windows.Spartan_cw5n1h2txyewy":
https://msdn.microsoft.com/en-us/library/windows/desktop/hh448541%28v=vs.85%29.aspx
NetworkIsolationEnumAppContainers will enumerate all AppContainers on the system:
https://msdn.microsoft.com/en-us/library/windows/desktop/hh447479%28v=vs.85%29.aspx
http://blogs.windows.com/bloggingwindows/2015/06/19/upcoming-changes-to-windows-10-insider-preview-builds/ indicates they're changing the app ID and people will lose all the stuff they don't actively back up and restore (and they're only providing instructions for restoring favorites).
It means that they can't change the app ID lightly (otherwise users will lose favorites and other settings again). So we can use the new app ID as a stable import source.
We need at least bookmarks migration for Firefox 41, provided the strings are approved to land in Aurora in bug 1179346.
Priority: P3 → P2
fyi - the passwords team (rchtara/rittme) is taking password specific importing off our backlog.
Blocks: 1191384
Duplicate of this bug: 1191406
Keywords: meta
Summary: Data Importer can't import from Edge/Spartan → Data importers/migrators for Microsoft Edge browser
Depends on: 1192032
Depends on: 1192034
Depends on: 1192035
Depends on: 1192036
Depends on: 1192037
Depends on: 1192039
I've made this a metabug, and split out the different migrator types into subbugs since they are at least somewhat independent of each other. (Feel free to continue to use this one for discussing shared issues.)
Depends on: 1193387
Depends on: 1199678
Depends on: 1200849
I don't see a reason to track this meta bug going forward. I am hoping that devs/Sheila/RelMan team will track individual bugs targeting specific releases.
Depends on: 1205053
Depends on: 1225466
Depends on: 1225798
Depends on: 1225800
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
(In reply to Sylvestre Ledru [:sylvestre] from comment #20)
> Moving to p3 because no activity for at least 1 year(s).
> See
> https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.
> md#how-do-you-triage for more information

Those definitions don't reflect when a component isn't resourced. Moving back to P2.
Priority: P3 → P2
You need to log in before you can comment on or make changes to this bug.