Feature request: sync local origin data (indexeddb, localstorage, etc)
Reported by
remysh...@gmail.com,
Oct 12 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: A logged in chrome account allows for syncing of bookmarks and extensions, but it would be hugely useful for the indexeddb and localstorage (and others?) to be synced from an origin. What is the expected behavior? What went wrong? It's not sync'ed (sorry, nothing really went wrong). Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.10.3 Flash Version: I've not fully thought through the security implications or whether there's a potential problem syncing app state vs. against the server, etc. but wanted to start conversation.
,
Oct 12 2017
,
Oct 12 2017
I think there are security implications with doing this. zea@ - is this something we've looked at in the past?
,
Oct 12 2017
+IndexDB and LocalStorage folks. Is this something you all have thought about? My hunch is that, similar to syncing cookies, there's too much potential for state that is specific to that device which would be incompatible with another device, causing problems for users on that page. Blink folks, thoughts?
,
Oct 12 2017
They're also huge - even hundreds of MBs on phones to tens of GBs on desktop. And you can't sync a subset or you leave the app in an inconsistent state. We also can't distinguish how a site is using storage - as a cache (which as noted may be device-specific) or as application state. It's something we'll keep in mind when looking at future storage APIs - are there ways to declare how it's used, bucketing data into syncable vs. local, etc.
,
Oct 12 2017
Makes sense. And agreed that having an explicitly syncable API would likely be safer. That's the route that was taken with extensions as well (the chrome.storage.sync API is separate from the local storage api). It sounds like for now these two local stores are not good candidates for syncing, but perhaps in the future we can have something more targeted that could enable the same cross-device functionality. |
||||
►
Sign in to add a comment |
||||
Comment 1 by mathias@chromium.org
, Oct 12 2017Status: Untriaged (was: Unconfirmed)