Tim Abraldes [:TimAbraldes] [:tabraldes] Reporter
	Description • 12 years ago

On first run of desktop Firefox, if the import/migration wizard is used to import data from another browser into a new desktop Firefox profile, then that data should also be imported into a new metro/immersive Firefox profile.

	Tim Abraldes [:TimAbraldes] [:tabraldes] Reporter
	Comment 1 • 11 years ago

I discussed this item with Asa and Marco.  Doing this "the right way" would be a lot of developer effort.  There are approaches that can get us most of the way (e.g. once the migration wizard has done its thing, copy the desktop profile into a new Metro profile), but we will not consider those in the immediate-term.  We can file new work items when we've decided on the stories we want.

	Asa Dotzler [:asa]
	Comment 2 • 11 years ago

Tim, is there any reason we shouldn't simply re-open this and change it's description to "Once the migration wizard has done its thing, copy the desktop profile into a new Metro profile"?  

The story end result is "Desktop Firefox and Metro Firefox profiles both contained a snapshot of the user's Internet Explorer and or Google Chrome browser's Bookmarks, History, Cookies and Settings." and I don't much care how we get there for v1.

If we can do something simple here, like a simple copy operation, then let's try for that. If there is no simple solution, then we should punt on this for v1 and just focus on making our Import from Metro UI the focus for v1.

	Tim Abraldes [:TimAbraldes] [:tabraldes] Reporter
	Comment 3 • 11 years ago

This might be possible and easy to implement, but there are some potential road blocks that could turn out to be impassable.

Basically, the approach we could take is this:
  1) At the end of the desktop migration wizard, check for the existence of ourProfileDir.parentDirectory.subDirectory("MetroFirefox").
  2) If it exists, give up.  If it does not exist, try to copy the current profile directory to that directory.

I'm not sure whether, after migration, the desktop profile directory is in a state that would allow us to copy it.  If it is copyable, then I think this approach is feasible.

There's also the issue of whether copying some elements of the desktop profile would interfere with correct operation of the metro browser (e.g. changing the dom.ipc.plugins.enabled value could be a big problem).

Mano: Do you have thoughts on this approach?  Specifically, do you know if it is possible to copy the desktop profile after importing into it?

	Asaf Romano (gone)
	Comment 4 • 11 years ago

I'm not sure about copying the profile, but copying some files over (like places.sqllite) should be possible.

	Gabriel
	Comment 5 • 11 years ago

Isn't there a fallacy in creating a separate profiles for the metro interface in the first place?  Isn't the point of creating a metro interface to provide a seamless connection between the desktop and Metro environment.  

For example, an ultra book user should be able to fold up a laptop into it's tablet configuration, switch their tabs and session over to the metro interface and have a seamless browsing experience there, now with a touch screen GUI.

I was under the impression that this was supposed to be a single, unified browser with two different GUIs.

	Brian R. Bondy [:bbondy]
	Comment 6 • 11 years ago

I don't think this is valid anymore because of shared profile work.