Closed Bug 1539444 Opened 7 years ago Closed 6 years ago

Theme sync disabling preference (services.sync) broke somewhere around Firefox v65/v66

Categories

(Firefox :: Sync, defect)

66 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: andri, Unassigned)

Details

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

Steps to reproduce:

Hey,

I'm using Firefox both on a Mac and on a Linux system with different themes and disabled syncing the configured theme a few years ago through disabling services.sync.prefs.sync.lightweightThemes.usedThemes and services.sync.prefs.sync.lightweightThemes.selectedThemeID so they'd stay separate. Somewhere around Firefox v65 or v66 this broke, and a selected theme on one machine is reflected on the other.

Curiously, the "Default" theme on the Mac has now switched to black hinting that something else is possibly being synced from the dark-themed Linux to the otherwise-light Mac, but I care more about disabling theme syncing than fixing the default theme on a Mac. ^_^

Has this preference been deprecated or renamed?

Thanks!

Summary: Theme sync preference (services.sync) broke somewhere around Firefox v65/v66 → Theme sync disabling preference (services.sync) broke somewhere around Firefox v65/v66
Has STR: --- → yes
Component: Untriaged → Sync

Hi Andri! Could you please paste the values of the lightweightThemes.usedThemes and lightweightThemes.selectedThemeID prefs themselves, on both Mac and Linux? Thanks!

Flags: needinfo?(andri)

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: 6 years ago
Flags: needinfo?(andri)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.