Closed
Bug 1282972
Opened 8 years ago
Closed 5 years ago
Handle storage quotas for extension origins
Categories
(WebExtensions :: Storage, defect, P2)
WebExtensions
Storage
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mattw, Assigned: rpl)
References
Details
(Whiteboard: triaged)
Chrome documentation: https://developer.chrome.com/extensions/declare_permissions#unlimitedStorage
Reporter | ||
Updated•8 years ago
|
Whiteboard: [webNavigation] triaged → triaged
Reporter | ||
Updated•8 years ago
|
Blocks: webext-port-shop-at-home
Comment 1•8 years ago
|
||
This includes adding support for the "unlimitedStorage" permission.
I've noticed some errors generated by quota checking code for extension origins, so those will have to be fixed first.
Summary: Implement "unlimitedStorage" permission → Handle storage quotas for extension origins
Updated•8 years ago
|
webextensions: --- → ?
Updated•8 years ago
|
webextensions: ? → ---
Updated•7 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: Storage
Comment 4•7 years ago
|
||
Assuming that this could be easier as part of the storage.local to indexed DB changes. Might even come for free.
Assignee: nobody → lgreco
Depends on: 1406181
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Assignee | ||
Comment 5•5 years ago
|
||
I'm closing this issue, the storage quota is now checked by extension origin as part of the storage.local IndexedDB backend.
In Bug 1555491 we also added some additional tests explicitly related to the QuotaExceededError scenarios.
You need to log in
before you can comment on or make changes to this bug.
Description
•