Closed
Bug 1114445
Opened 10 years ago
Closed 10 years ago
Update sync migration to new UX flows
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
People
(Reporter: markh, Assigned: markh)
References
Details
Attachments
(1 file)
17.39 KB,
patch
|
adw
:
review+
|
Details | Diff | Splinter Review |
There are some relatively minor tweaks to the migration strings - http://is.gd/sync_migration_ux_pdf. While going through this I also found a few other things we weren't doing quite right (particularly around the "join the party" flows).
This bug is to update what's already landed to these new requirements.
Flags: qe-verify-
Flags: firefox-backlog+
Assignee | ||
Updated•10 years ago
|
Blocks: migratesync
Assignee | ||
Comment 1•10 years ago
|
||
Drew should be back long enough before the merge to review this - although this must land before that merge as it has strings.
Attachment #8539925 -
Flags: review?(adw)
Comment 2•10 years ago
|
||
Comment on attachment 8539925 [details] [diff] [review]
0004-Bug-1114445-update-sync-migration-flows-to-reflect-l.patch
Review of attachment 8539925 [details] [diff] [review]:
-----------------------------------------------------------------
::: browser/components/preferences/in-content/sync.js
@@ +303,5 @@
> case fxaMigrator.STATE_USER_FXA: {
> let sb = this._accountsStringBundle;
> + // There are 2 cases here - no email address means it is an offer on
> + // the first device (so the user is prompted to create an account).
> + // If there is an email address it is the "join the party" flow, so the
This comment is a better explanation than the similar comment you added in browser-fxaccounts.js IMO.
::: browser/locales/en-US/chrome/browser/accounts.properties
@@ +11,5 @@
> upgradeToFxA.accessKey = U
>
> +# LOCALIZATION NOTE (upgradeToFxASubsequent.description)
> +# %S = Email address of user's Firefox Account
> +upgradeToFxASubsequent.description = Sync was upgraded on another device by %S. Resume syncing?
Hmm, "upgradeToFxASubsequent" makes me think that these strings are still about asking the user to upgrade. It's more like "upgraded on another device" or "sign in on this device."
Attachment #8539925 -
Flags: review?(adw) → review+
Assignee | ||
Comment 3•10 years ago
|
||
(In reply to Drew Willcoxon :adw from comment #2)
> Hmm, "upgradeToFxASubsequent" makes me think that these strings are still
> about asking the user to upgrade.
But they are :) It's saying "sync was upgraded elsewhere, do you want to upgrade here too?"
> It's more like "upgraded on another
> device" or "sign in on this device."
I agree the name sucks - do you have a concrete suggestion? I spent quite a few brain-cycles trying to come up with a good name, and even with a week of reflection I'm still stuck :)
Comment 4•10 years ago
|
||
To my mind there's only one upgrade, not an upgrade per device. Once you do the upgrade, from one device, you only have to sign in on other devices.
signInAfterUpgradeOnOtherDevice? It's not a huge deal, r+ with upgradeToFxASubsequent too.
Assignee | ||
Comment 5•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → mhammond
Status: NEW → ASSIGNED
Updated•10 years ago
|
Iteration: --- → 37.3 - 12 Jan
Comment 6•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 37
You need to log in
before you can comment on or make changes to this bug.
Description
•