Andrew Sutherland
Andrew Sutherland
Firefox's storage implementation originally intended to queue storage events but the naive implementation logic for that never actually worked, just temporarily consumed memory as it buffered the events without coalescing,...
I believe that already happens. The current spec mutates the single [map](https://html.spec.whatwg.org/multipage/webstorage.html#concept-storage-map) and calls [broadcast which queues a task](https://html.spec.whatwg.org/multipage/webstorage.html#concept-storage-broadcast). This works in a straightforward fashion under a single-process model assuming...
I defer to @annevk in all things; my key concern in general would be that anything in BFCache should not accumulate an unbounded list of changes that could result in...
It sounds like the storage would be keyed per-tab (top-level browsing context). Would the "session" bucket also share the existing SessionStorage semantics where the existing storage is forked whenever new...
I also don't like the idea of expanding the copying semantics beyond sessionStorage. There are both implementation and conceptual complexities that would be hard to be address and don't seem...
> Then developers could store session data in normal indexeddb, and manually delete old sessions. I think it would be preferable to bias things so that extra manual bookkeeping that...
This seems desirable and has indeed come up before. Specifically, in terms of allowing structured serialized storage of data on things like ServiceWorker registrations and related data (ex: [Notification.data](https://notifications.spec.whatwg.org/#dom-notification-data)) where...
@pwnall Your simplifying proposal in https://github.com/whatwg/storage/issues/110#issuecomment-662493325 sounds good to me. Also, it's very consistent with reality, as Mozilla's Servo project is an example of bringing up a browser from scratch-ish...
The current Firefox/Gecko thinking here is: - (Versus storage pressure events) We strongly prefer exposing a mechanism to create multiple storage buckets to content where content can expose some eviction...
That's consistent with my understanding. I think we also discussed that it might make sense to generate courtesy events to update origins on when their usage crosses certain thresholds so...