Closed Bug 1776531 Opened 3 years ago Closed 3 years ago

Firefox synced default settings of Nightly to Stable

Categories

(Firefox :: Sync, defect)

Firefox 101
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: pythagorians07, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:101.0) Gecko/20100101 Firefox/101.0

Steps to reproduce:

I have an account with all of my settings, shortcuts etc. on the stable version of Firefox. And I installed the Nightly version to test some features, then I log in my firefox account to the Nightly browser so I can use all my shortcuts and settings that I previously made from the stable browser.

Actual results:

Firefox synced the Nightly browser instead, it synced the default settings of the Nightly version to my Stable version and all of my settings and shortcuts were change to default in the Stable version

Expected results:

The Nightly version should have sync the settings from the stable version because its the one with a custom settings and not the default one. Right now I dont know how to revert the settings that have been change in the Stable version

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
Summary: Firefox synced the wrong data → Firefox synced default settings of Nightly to Stable

Which preferences were impacted here? There are very very few preferences which have different values between Nightly and Release.

Regardless, this is by design - If you do not change a value from the default and the default differs, each channel will keep its different default value., However, if you change a value, that preference value is synced across all channels regardless of what the default is.

Flags: needinfo?(pythagorians07)

Sorry, there was a problem with the detection of inactive users. I'm reverting the change.

Flags: needinfo?(markh) → needinfo?(pythagorians07)

Thanks again for reporting this issue, but we are unable to determine the cause of the problem without the requested information. If you are able to provide this information, please just add a comment in this bug with that information and we'll get back to you as soon as we can, but in the meantime we are closing this bug so we can focus on the issues which we can address.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(pythagorians07)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.