Issue History

We have discussed:

• the maximum total size for storage.local at Discuss limits applied to storage.local API #351 . It is increased from 5MB to 10MB.
• the maximum total size for storage.session at Discuss limits applied to storage.session API #350 . It is increased from 1MB to 10MB.
• Proposal: Increase maximum item size in Storage sync quotas #510 concentrates on the "Maximum item size" for storage.sync, not "Maximum total size".

#351 originally discussed "Maximum total size" for storage.local and storage.sync , now leaves that issue to storage.local only.

This Issue

This issue concentrates on "Maximum total size" (QUOTA_BYTES) for storage.sync. At present, storage.sync has 100KB limit. This limitation has existed for a long time. As user devices and cloud storage capabilities improve, should it be increased now?

The browser's built-in support for data synchronization is great, because it's non-trivial for developers to create their own cloud synchronization service. This requires developers to:

• establish their own account system and/or obtain authorization from third-party storage services (e.g. Google Drive, iCloud, Dropbox).
• cloud syncing also means that extensions collects user data and storage it on extension's server, and users may be concerned about their personal privacy.
• cloud syncing have costs. Developers not only need to spend time developing, but also need to bear the corresponding costs on a long-term basis. This means that developers need to charge users, otherwise it will be difficult to provide this service.