Closed Bug 2094109 Opened 4 days ago Closed 3 days ago

Unexpected preference change upon re-enabling sync after disconnect

Categories

(Firefox :: Sync, defect)

Firefox 162
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox162 --- affected

People

(Reporter: rpopovici, Unassigned)

References

(Blocks 1 open bug)

Details

Found in:
Nightly version: 162.0a1(Build ID: 20261116204239)

Affected versions:
Nightly versions: 162.0a1(Build ID: 20261116204239)

Tested platforms:
Affected platforms: Windows 11 and Ubuntu 26

Preconditions:
Have the following prefs set to true in about:config:
services.sync.perDeviceEngineChoices = true (PDS profile)
Profile 1 with PDS(pref on): is signed into sync account.
Profile 2 with Legacy(pref off): is signed into the same sync account.

Steps to reproduce:

  1. Open Profile 1 (PDS) and go to about:preferences#sync.
  2. Click the Disconnect button from sync settings page.
  3. Click the Disconnect button.
  4. Click avatar icon and select "Turn on".
  5. Click "Turn on syncing" button.
  6. Go to about:config and verify the pref "services.sync.perDeviceEngineChoices".

Expected result:
The pref "services.sync.perDeviceEngineChoices" is set to true after re-enabling sync.

Actual result:
The pref "services.sync.perDeviceEngineChoices" is set to false after re-enabling sync.

Regression range:
Not a regression as recently implemented.

Has STR: --- → yes
QA Whiteboard: [QA-45954][qa-found-in-c162][S3]
QA Whiteboard: [QA-45954][qa-found-in-c162][S3] → [QA-5954][qa-found-in-c162][S3]
Blocks: 2072032

Apologies, this was a subtle omission from our test plan, which has been updated. It said:

Set the pref before every sign-in, because signing out resets it. Never set it back to false yourself on a profile that has synced.

And it has been updated to say:

Set the pref before every sign-in, because signing out or disconnecting resets it. Never set it back to false yourself on a profile that has synced.

Because both signing out AND disconnecting will reset the pref to its default state (which is still "off").

Status: NEW → RESOLVED
Closed: 3 days ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.