1156075 - Message when tab sync has been remotely disabled

Status: NEW

(Firefox for iOS :: Sync, defect)

Description

[Richard Newman [:rnewman]]

When we support datatype elections on iOS, we'll be doing per-device choices. That leads to its own problems with meta/global.

But until then, we have to handle a meta/global with no "tabs" entry -- i.e., the user has turned off tab sync, and that's why we'll (fail|null-succeed) to fetch any.

In the short term we could treat this simply as "No tabs from other devices" -- i.e., synced successfully, but no tabs. IIRC we have assets for this in Bug 1144760.

If there's small-print, we could do better, explaining *why*. There's probably a decent-sized set of users who turned off tab sync in the single-device case, and now have a reason to turn it on.

Comment 1

[Nick Alexander :nalexander [he/him]]

Given kar's support for shipping iOS v1 without being able to configure the set of synced datatypes, this becomes relatively more important.  See also Bug 1139038 and Bug 1139045.

Comment 2

[Richard Newman [:rnewman]]

After Bug 1167824 this will be due to one of two things:

* A FatalError raised from ClientsSynchronizer. This is not common.
* An EngineNotEnabledError raised from TabsSynchronizer.