Closed
Bug 1220926
Opened 10 years ago
Closed 10 years ago
Add or Expose Sync Setting to the About:support api
Categories
(Toolkit :: General, defect)
Toolkit
General
Tracking
()
RESOLVED
FIXED
Future
| Tracking | Status | |
|---|---|---|
| firefox45 | --- | fixed |
People
(Reporter: guigs, Assigned: markh)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
1.07 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
In order to better troubleshoot settings for users learning to use Firefox Sync Accounts, I would like to request the exposure of the sync settings in order for the SUMO troubleshooter to collect the data for Sync specific questions.
| Reporter | ||
Updated•10 years ago
|
Component: Data Collection → General
Product: Firefox Health Report → Firefox
Target Milestone: --- → Firefox 44
| Reporter | ||
Updated•10 years ago
|
Target Milestone: Firefox 44 → Future
| Assignee | ||
Updated•10 years ago
|
Product: Firefox → Toolkit
| Assignee | ||
Comment 1•10 years ago
|
||
Thanks for the bug Rachel - I think this makes alot of sense.
This patch adds a few sync preferences to about:support. The preferences are limited to those which indicate what sync engines are enabled, when the last successful sync was, and how many sync clients are associated with the account. I've explicitly avoid ones that include GUIDs, device or account names, or anything else that is clearly PII. On my test account the information includes looks like:
> services.sync.declinedEngines
> services.sync.engine.prefs.modified false
> services.sync.lastPing 1447717583
> services.sync.lastSync Tue Nov 17 2015 10:52:53 GMT+1100 (AUS Eastern Standard Time)
> services.sync.numClients 5
This reflects the default configuration - if the user explicitly declines to sync particular engines (eg, tabs), you would also expect to see, eg, "services.sync.engine.tabs.enabled false"
Flagging Benjamin for review as this is related to privacy.
Updated•10 years ago
|
Attachment #8688167 -
Flags: review?(benjamin) → review+
Comment 3•10 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox45:
--- → fixed
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•