Closed
Bug 1016806
Opened 10 years ago
Closed 10 years ago
Update Sync "end of life" notifications to suit migration UX requirements
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
WORKSFORME
Iteration:
36.1
People
(Reporter: markh, Assigned: markh)
References
Details
Attachments
(1 file)
89.38 KB,
image/png
|
Details |
The sync servers can be configured to send "end of life" notifications, which currently causes an "info bar" at the bottom of the browser. This info bar currently has fixed strings (one for "soft" eol - "sync is going away soon", and one for "hard" eol - "sync is no longer working") and a button which opens a new tab in the browser.
For reference, an example of a "soft-eol" warning is attached.
The current system seems suitable for "old" firefox versions where the migration code isn't in-place - it tells you to upgrade Firefox itself.
For sync migration, I suspect we will want at least:
* A new string to indicate you need to migrate your Sync account rather than to upgrade Firefox.
* A button (either replacing or in addition to the existing one) which actually starts the migration process rather than taking you to a page with more information.
Flags: firefox-backlog+
Assignee | ||
Comment 1•10 years ago
|
||
One other consideration that we might as well handle in this bug: do we display a different message in the infobar if we have determined the user has migrated other devices? Or maybe the infobar text is identical and only the (TBD) "migration ui" changes based on this fact?
See also bug 1016825 for engineering considerations around this.
Updated•10 years ago
|
Whiteboard: p=5 → p=5 [qa?]
Updated•10 years ago
|
Assignee: nobody → mhammond
Status: NEW → ASSIGNED
Whiteboard: p=5 [qa?] → p=5 s=33.1 [qa+]
Updated•10 years ago
|
Iteration: --- → 33.2
Points: --- → 5
QA Whiteboard: [qa+]
Whiteboard: p=5 s=33.1 [qa+]
Updated•10 years ago
|
Iteration: 33.2 → ---
Assignee | ||
Comment 2•10 years ago
|
||
The current UX flow handles this.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Iteration: --- → 36.1
QA Whiteboard: [qa+]
Flags: qe-verify+
Comment 3•10 years ago
|
||
(In reply to Mark Hammond [:markh] from comment #2)
> The current UX flow handles this.
Is there any additional verification needed here? The comment from Mark seems to imply that this was already verified as working.
Assignee | ||
Comment 4•10 years ago
|
||
Sorry for the confusion.
Flags: qe-verify+ → qe-verify-
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•