:Gijs (he/him) Assignee
	Description • 8 years ago

(keeping about:home because that seems simplest for future funnelcakes etc. - the code will likely end up all being wiped in one go at some point anyway.)

	Justin Dolske [:Dolske]
	Comment 2 • 7 years ago
mozreview-review

Comment on attachment 8818953 [details]
Bug 1322730 - display undo migration message on about:newtab,

https://reviewboard.mozilla.org/r/98862/#review102354

::: browser/components/migration/AutoMigrate.jsm:322
(Diff revision 1)
>        return;
>      }
>  
>      let win = target.ownerGlobal;
>      let notificationBox = win.gBrowser.getNotificationBox(target);
> -    if (!notificationBox || notificationBox.getNotificationWithValue("abouthome-automigration-undo")) {
> +    if (!notificationBox || notificationBox.getNotificationWithValue(kNotificationId)) {

Constants, what are they good for? :)

	Pulsebot
	Comment 4 • 7 years ago

Pushed by gijskruitbosch@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/9647d2c82af4
display undo migration message on about:newtab, r=Dolske

	Pulsebot
	Comment 5 • 7 years ago

Backout by archaeopteryx@coole-files.de:
https://hg.mozilla.org/integration/autoland/rev/641dd38a2315
Backed out changeset 9647d2c82af4 for eslint failures. r=backout

	Pulsebot
	Comment 7 • 7 years ago

Pushed by gijskruitbosch@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/7e31694292a4
display undo migration message on about:newtab, r=Dolske

	Phil Ringnalda (:philor)
	Comment 8 • 7 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/7e31694292a4

	:Gijs (he/him) Assignee
	Comment 9 • 7 years ago

Comment on attachment 8818953 [details]
Bug 1322730 - display undo migration message on about:newtab,

Approval Request Comment
[Feature/Bug causing the regression]: funnelcake for bug 1322718
[User impact if declined]: impact to the funnelcake
[Is this code covered by automated tests?]: yes!
[Has the fix been verified in Nightly?]: no, because it's behind a pref
[Needs manual test from QE? If yes, steps to reproduce]: yes, but we'll need a custom build. Verification is easy: on the custom build, users should get a notification about the import on about:newtab .
[List of other uplifts needed for the feature/fix]: the other deps for bug 1322718 are related, but I don't think this particular bug will require anything else.
[Is the change risky?]: No.
[Why is the change risky/not risky?]:  it's completely behind a pref (the automigration one) so will only affect the funnelcake.
[String changes made/needed]: No.

	Liz Henry (:lizzard) (relman/hg->git project)
	Comment 10 • 7 years ago

Comment on attachment 8818953 [details]
Bug 1322730 - display undo migration message on about:newtab,

Part of funnelcake project for 51. 
I hope this can make it to beta 12 but if not, it'll be in Monday's beta 13 build.

	Ryan VanderMeulen [:RyanVM]
	Comment 11 • 7 years ago
bugherder uplift

https://hg.mozilla.org/releases/mozilla-aurora/rev/614bfd5e4212

	Ryan VanderMeulen [:RyanVM]
	Comment 12 • 7 years ago
bugherder uplift

https://hg.mozilla.org/releases/mozilla-beta/rev/fd57670a2f39

	Andrei Vaida [:avaida]
	Comment 13 • 7 years ago

Flagging this for verification based on the instructions from Comment 9. Grover -- hopefully you still have some bandwidth left to take this.

	Alexandru Simonca [:asimonca], Release Desktop QA
	Comment 14 • 7 years ago

 Hi Gijs,
Could you possibly provide a custom build for us to test this issue on? Thank you.

	:Gijs (he/him) Assignee
	Comment 15 • 7 years ago

(In reply to Alexandru Simonca, QA (:asimonca) from comment #14)
>  Hi Gijs,
> Could you possibly provide a custom build for us to test this issue on?
> Thank you.

You shouldn't need a custom build anymore - you can try current nightly (which after bug 1343076 has automigration enabled), and start it with the -migration commandline flag. You'll need to make sure another browser (IE/Edge/Chrome/Safari) is set as the default browser on the machine and has importable data (history, bookmarks, passwords) that it then automatically imports (if you see the import wizard, that bit is not working). When using Chrome as the browser to automatically import from, it also only works on machines with only 1 Chrome profile.

	Alexandru Simonca [:asimonca], Release Desktop QA
	Comment 16 • 7 years ago

I understand but I was going to verify the 52 & 53 builds since their flags are set to "fixed". Will it work on those?

	:Gijs (he/him) Assignee
	Comment 17 • 7 years ago

(In reply to Alexandru Simonca, QA (:asimonca) from comment #16)
> I understand but I was going to verify the 52 & 53 builds since their flags
> are set to "fixed". Will it work on those?

On 53 yes, because automigration is currently enabled on 53 as well. On 52 release, no, because it's been disabled there, but you could use the previously-shipped 52 beta 8 to check it there. This bug landed on 52 when it was still on aurora, and on 52 we enabled automigration for "a while". Does that help?

	:Gijs (he/him) Assignee
	Comment 18 • 7 years ago

(In reply to :Gijs from comment #17)
> on 52 we enabled automigration for "a while".

This should have read 'on 52 beta'. :-)

	Alexandru Simonca [:asimonca], Release Desktop QA
	Comment 19 • 7 years ago

I've tested this issue using Comment #15 as a guideline and managed to automigrate data from Chrome to Firefox on Beta 52.0b8 and Firefox 53.0b1 on Windows 8.1 x86 and on Beta 53.0b1 on Mac OS 10.11.6. I consider it Verified Fixed since it worked on 52 and 53. Please ni? me if there are any concerns.