Re: [w3c/ServiceWorker] Mixed feelings about ServiceWorker for module loader (#1203)

> I thought it was only Edge that still had separate limits per storage, but I may be wrong.

Firefox has separate limits for cookies, localStorage, sessionStorage, and the unified-by-"Quota Manager" IndexedDB/Cache API APIs.  We are migrating localStorage to operate with the unified "Quota Manager" framework and its generous storage budgets, but plan to maintain localStorage's per-origin rough 5MB limit counted over len(key)+len(value) for all stored tuples that ignores actual on-disk costs.   We do plan to relax our stricter "group" TLD+1 accounting for localStorage that is the source of the *.wikipedia.org problems to Quota Manager's more forgiving "group" TLD+1 accounting, however.

The reason we're keeping the limit intact is that we currently load and retain-in-memory the entirety of an origin's LocalStorage when we decide to load it at all.  Even if we further optimized our localStorage implementation to be more strategic in key loading and retention, more quota for localStorage is just more problems.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1203#issuecomment-336741050