New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 745708 link

Starred by 0 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature



Sign in to add a comment

[local-sync] FR Extension state not synced across computers

Reported by san...@goudswaard.nl, Jul 18 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Enable the local sync backend
2. Install extensions: LastPass, uBlock Origin
3. Log into LastPass; make changes to uBlock Origin. E.g. enable cloud support; select additional lists
4. Close browser, logoff Windows, login to another desktop
5. Open Chrome. Notice that extensions are re-added after about a minute.
6. Notice that LastPass does not remember your e-mail address. uBlock has not saved any settings you made before.

What is the expected behavior?
Extensions should save user data across sessions, using the roaming profile support.

What went wrong?
Nothing was saved from the extension data, only the fact that the extension itself is part of the profile and must be re-added to the new session.

For our users, local-sync is unusable because having to type their e-mail address in LastPass and adjusting extension settings every day is not expected or desirable.

Did this work before? No 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version:
 

Comment 1 by s...@chromium.org, Jul 18 2017

Cc: rdevlin....@chromium.org pastarmovj@chromium.org
Does this work if you aren't using local/roaming profile sync? Fiddling with settings for uBlock Origin, I see that toggling the 'Allow in incognito' checkbox on chrome://extensions triggers a change in sync data, but changing things from chrome-extension://cjpalhdlnbpafiamejdnhcphjbkeiagm/dashboard.html does not seem to affect sync data.

You can view sync data at chrome://sync-internals . If you go to the 'Sync Node Browser' tab you can inspect what the data looks like. I'm not sure exactly what a well behaving extension looks like and how it can/should sync data, but if the change isn't making it to chrome://sync-internals, it's not going to get synced across your device.

+pastarmovj in case this turns out to be a roaming profile issue, which it doesn't seem like.
+rdevlin.cronin to weigh in on how extensions are supposed to (can they even) sync custom settings.
Extensions can choose to use chrome sync by using the chrome.storage.sync API; data stored in there should sync across devices (just as the extension installation does).  If the extension is not using chrome.storage.sync (and instead is using LocalStorage, server side storage, chrome.storage.local, or any other storage solution), chrome will not sync the data.
Cc: blumberg@chromium.org
Sky, I guess the comparison here is to the full profile (if it is roamed between machines) in which case obviously the extension internal state is fully preserved. I think Lastpass does not use sync storage for its master password as I have been using the extension as well and it does ask for its password on every machine. This is indeed something that roaming profiles can not help with at this stage.

I think this bug should be seen as a feature request for roaming profiles to support extensions local storage. This seems like something that needs to be done outside of the sync engine though as it doesn't fit in its philosophy. It goes close to another feature request for roaming profiles which is to cache extension crx files so that they get reinstalled faster when roaming to new machines.

If you agree with this analysis feel free to remove the sync component from this bug and assign to me instead.
I can confirm LastPass does not sync anything. I contacted them about this. Users would have to do all settings (including typing their entire long e-mail adddress and setting idle timeouts) every day.

uBlock Origin does sync some settings, but not the most important one to use cloud storage. Hence it does not restore the saved settings in the new profile.

We are currently using profiles on network drives which works fine except for  issue 674076 . We won't migrate to local-sync until extensions local storage will be made possible.

Thank you for your feedback +pastarmovj. I have no permission to change components but please go ahead and assign it to yourself.

Cc: -rdevlin....@chromium.org georgesak@chromium.org
Components: Enterprise
Labels: -Type-Bug -Arch-x86_64 Arch-All Type-Feature
Status: Available (was: Unconfirmed)
Summary: [local-sync] FR Extension state not synced across computers (was: [local-sync] Extension state not synced across computers)
Thanks for confirming this.

I will keep the sync component for now but as I said the actual implementation would most probably be unrelated to the sync client.
Labels: Enterprise-Triaged

Comment 7 by s...@chromium.org, Jan 17 2018

Cc: s...@chromium.org
Labels: Sync-Triaged SyncHandoff2018
It's unclear to me who the owner of this should be. It seems almost as if this should be closed as WontFix, since the extension is not syncing its data, there is no "bug", right?
Re #7
Agreed.
Components: -Services>Sync
Removing Sync component per the above comments. Leaving it open as a feature request for enterprise/roaming profile support.

Sign in to add a comment