Open Bug 1810326 Opened 2 years ago Updated 2 years ago

Sync changes configurations on existing devices upon initial sync of new device

Categories

(Firefox :: Sync, defect, P2)

Firefox 108
defect

Tracking

()

People

(Reporter: account, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0

Steps to reproduce:

  • I have an established sync account with a lot of privacy related changes, such as disabling firefox's password manager (or at least the offer to save passwords to it) and I have noscript installed.
  • When I start using a new computer I set up firefox sync on it, to sync in those settings, and preferably the noscript whitelist I have built up over time.

(fyi. I have a rather old sync account by now, so there may be some kind of old state embedded in it that I don't know of.)

Actual results:

  • The addons are installed and most settings are synced to the new computer, but some settings don't seem to be applied to the new computer (specifically I noted noscript whitelist and whether or not to query to save passwords weren't saved).
  • Worse yet the settings that weren't applied seem to have been back-synced to all my other devices, wiping my noscript whitelist and the password setting. I don't know if anything else is affected.

(This has been consistent over my last 4 additions of desktop firefox instances to my sync account.)

Expected results:

The settings in my sync account should be applied to the new device. If they fail to apply to the new device that failure shouldn't destroy the data in my sync account.

The Bugbug bot thinks this bug should belong to the 'Firefox::Sync' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Sync

Presumably is the log from when the wrong settings started to be propagated to my other devices.

what should happen in this scenario is that all the incoming preferences are applied locally - sadly though, the logs aren't don't capture enough info to know exactly what did happen and what prefs were applied. We should fix that, and also test this scenario better.

Severity: -- → S2
Priority: -- → P2

Hello! As per the last comment I will mark it as NEW to give more visibility to this issue.

Have a nice day!

Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: