Closed Bug 1311516 Opened 8 years ago Closed 4 years ago

chrome.storage.sync: implement client-side quotas

Categories

(WebExtensions :: Storage, defect, P3)

Product:
WebExtensions
Component:
Storage
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1637166

People

(Reporter: glasserc, Unassigned)

References

Details

(Whiteboard: [storage]triaged)

Right now, Kinto supports server-side quotas, and while this should be enabled on the production stack by bug 1311507, there are also client-side quotas that we should probably implement. In particular, https://developer.chrome.com/extensions/storage lists 1800 writes per hour.
Blocks: 1311710
Component: WebExtensions: Untriaged → WebExtensions: General
Priority: -- → P3
Whiteboard: [storage]triaged
Component: WebExtensions: General → WebExtensions: Storage
Product: Toolkit → WebExtensions
Blocks: 1484968

As mentioned in Bug 1413949 comment 5, as part of the client-side quotas we should check the byte-per-object limit on the client side to give the caller extension the opportunity to know that the per-object limit is being exceeded (by returning a rejected promise when the value is being set), so that the extension itself can detect the issue and be able to handle it.

Client-side quota has been implemented as part of the new storage.sync rust-based implementation.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.