Open Bug 943182 Opened 7 years ago Updated 2 months ago

Consider syncing CustomizableUI state (toolbar customization) between devices


(Firefox :: Toolbars and Customization, enhancement, P5)





(Reporter: Unfocused, Unassigned)


(Blocks 2 open bugs)


(Whiteboard: [Australis:P-])

One of the use-cases I originally wanted to solve with CustomizableUI was to make it simple to sync UI customization between devices. 

To achieve that, we'd need to:
* Hook up pref observers
* Split out the extra stuff from browser.customizableui.state, so it doesn't contain things like the array of seen widgets (which would act weird if we're not syncing addons)
* Set the relevant pref to sync browser.customizableui.state
* Decide whether we want UI to toggle it. ie, is UI customization included in what people consider "settings", or is it separate?
I would like it very much if firefox synch the custom UI (toolbars)
I'm not opposed to this, but I'm marking this as P- considering this is something that the current customization mode doesn't offer and I'm trying to reduce scope creep. But this is a great idea for a v2!
Whiteboard: [Australis:M?] → [Australis:P-]
Duplicate of this bug: 1007268
Duplicate of this bug: 1018231
Any news?
(In reply to Daniel "warmth" Delgado from comment #5)
> Any news?

No news yet. If work is started on this you'll see the activity in this bug. I don't expect it will be worked on soon, but if you or someone else would like to work on it that would be great! :)
Duplicate of this bug: 1270796
Duplicate of this bug: 1256443
Duplicate of this bug: 1431359
To all the people in CC and duplicated bugs, please consider voting for this issue, in order to increase its visibility, and improve chances of being fixed.
Duplicate of this bug: 1502091

(CustomizableUI controls toolbar visibility state, too. That's persisted in XUL store, which will need changes to Sync:

I would like to have this feature, too. Whenever I install a new device, I have to re-customise the toolbar, which is quite boring. :)

Anyway, it still is an issue on FF 65.0.2 (64-bit) on any OS (just to note).

Duplicate of this bug: 1546379

Would also be keen to see this feature. First thing I do after sync is to move my toolbar around.

Duplicate of this bug: 761938
Duplicate of this bug: 1562434
Type: defect → enhancement
Duplicate of this bug: 1567501
Duplicate of this bug: 1576362

6 years. wow.

(In reply to Daniel from comment #20)

6 years. wow.

It's not clear exactly how we should do this, or even if we should do it at all. My customizations tend to be based on the size of the screen the device has, so personally I would consider it broken if syncing "preferences" meant my toolbars were identical across all devices - and I'd be forced to turn off preference syncing, so I'd get no preferences synced at all.

One way could be renaming preferences into "settings", and create a new Sync option "User Interface". Would it then be a problem in your use case?

Flags: needinfo?(markh)

That would certainly be an improvement. We really need to look at everything which hangs off and see if there is a sane, small number of additional options we could add which could handle most things there, or some other way to capture this "long tail" of things some people would like synced, but which some other people would find strange if they were.

Flags: needinfo?(markh)

But it could be disabled by default, so other people who find it strange wouldn't notice?

Flags: needinfo?(markh)

I don't think this alone is enough to justify a new setting without considering all the other things hanging off that bug.

Flags: needinfo?(markh)

Which "other things" are hanging off this bug? o_O

Flags: needinfo?(markh)

I was referring to the "syncmore" bug. You continuing to needinfo me isn't going to make this happen any time soon.

Flags: needinfo?(markh)
Duplicate of this bug: 1597164
Summary: Consider syncing CustomizableUI state between devices → Consider syncing CustomizableUI state (toolbar customization) between devices
Priority: -- → P5
Duplicate of this bug: 1604403
Duplicate of this bug: 1674567
You need to log in before you can comment on or make changes to this bug.