Consider adding progress indicator or throbber for initial sync

RESOLVED WONTFIX

Status

defect
P3
normal
RESOLVED WONTFIX
6 years ago
5 years ago

People

(Reporter: TimAbraldes, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Follow-up from https://bugzilla.mozilla.org/show_bug.cgi?id=845468#c33

For UX/product consideration:
  The initial sync, especially on slow machines, can take quite a long time.  Users see a message indicating that their remote tabs should be available, but the tabs may not actually be available immediately.  Should we provide some kind of indication that the initial sync is in progress and that the user's data might not be fully available immediately?
Hi Asa, need your input on priority.
Flags: needinfo?(asa)
In the prior implementation of the ui, we took the status indicator out due to issues with the sync service taking a long time, exiting uncleanly from a sync (partial sync), and other issues. What we did was display a last sync date instead. This let us close out a number of qa bugs related to sync service lag.
Summary: Consider adding progress indicator or throbber for initial sync → Change - Consider adding progress indicator or throbber for initial sync
Whiteboard: feature=change c=tbd u=tbd p=0
Flags: needinfo?(asa)
Priority: -- → P3
No longer blocks: metrov2defect&change
Summary: Change - Consider adding progress indicator or throbber for initial sync → Consider adding progress indicator or throbber for initial sync
Whiteboard: feature=change c=tbd u=tbd p=0 → [feature] p=0
No longer blocks: metrobacklog
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
Whiteboard: [feature] p=0
OS: Windows 8 Metro → Windows 8.1
You need to log in before you can comment on or make changes to this bug.