Closed Bug 979432 Opened 9 years ago Closed 7 years ago

Remove all Sync notification bars which don't require user action to resolve.

Categories

(Firefox :: Sync, defect, P1)

x86
All
defect

Tracking

()

RESOLVED DUPLICATE of bug 1180587

People

(Reporter: johnath, Unassigned)

References

Details

Without user action, this is just worrying user without benefit. Discussed in today's sync stand up, not an FF29 blocker, but I sure would like to see us just remove it.
Blocks: 969593
Priority: -- → P2
Is the goal of this bug to remove the sync notification bar? To remove the notification bar when sync failed due to network outage?

There is a whole lot of other possible failures, like login failures, being over quota, the client being too old, being forced to back off, etc.
The proximate goal is to stop showing a notify bar on network outages.

If there are other notification bars that alert the user to a situation they can do nothing to resolve (maybe back off fits into this camp?) killing those is gravy, but not strictly the scope of this bug.

This is not a request to remove useful, actionable errors around, e.g., bad credentials.
Summary: The "sync is failing" notification bar is unneeded UI → Remove all Sync notification bars which don't require user action to resolve.
Note that Sync is more aggressive about reporting errors when the user selects "Sync Now" - so many errors that wouldn't cause a notification bar during regularly scheduled syncs *will* cause the notification bar when the user explicitly requests a sync.

For now, I'm going to assume that this behaviour is acceptable - that this bug is really only concerned with errors bars that pop-up without the user explicitly requesting a sync.  If you disagree with this, please speak up!
Flags: firefox-backlog+
Priority: P2 → P1
See Also: → 1177589
Markh, can we close this one now? If so, please do.
Flags: needinfo?(markh)
We are doing all this in bug 1180587
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(markh)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.