[w3ctag/spec-reviews] Storage persistence and estimation APIs (#171)

Hello TAG!

I'm requesting a TAG review of:

  - Name: __Storage - persistence and quota/usage estimation APIs__
  - Specification URL: https://storage.spec.whatwg.org
  - Explainer, Requirements Doc, or Example code: [MDN](https://developer.mozilla.org/en-US/docs/Web/API/StorageManager)
  - Primary contacts: @inexorabletash

You should also know that...

The Storage spec (authored by @annevk) attempts to define web platform storage architecture - the theoretical concepts underpinning various storage APIs like DOM Storage, Indexed DB, Service Worker's Cache, notifications, etc

It also defines two new APIs: a permission for making an origin's storage persistent (two promise-based methods to request and check the permission), and a means for an origin to get an estimate of its current usage and potential quota (a single promise-based method).

Parts of this (the persistent storage permission) have [shipped in Chrome (since 55) and Opera (since 42)](https://www.chromestatus.com/features/4931497563783168). Chrome has an experimental implementation of the usage/quota estimation method. Firefox has experimental implementations of both parts. 

(Relevant history: Chrome has previously shipped usage/quota estimation APIs based on early iterations ([1](https://wiki.whatwg.org/wiki/Quota), [2](https://www.w3.org/TR/2012/WD-quota-api-20120703/)) of https://www.w3.org/TR/quota-api/ - but the current API as defined in that document was never shipped. Chrome also experimented with an earlier bifurcation between ['temporary' and 'persistent' storage](https://www.w3.org/TR/quota-api/#temporary-vs-persistent), exposed on individual storage API entry points, but that was only ever implemented for the [File System API](https://www.w3.org/TR/quota-api/#temporary-vs-persistent) that only Chrome ever shipped.)

We'd prefer the TAG provide feedback as (please select one):

  - [x] open issues in our Github repo for each point of feedback
  - [ ] open a single issue in our Github repo for the entire review
  - [ ] leave review feedback as a comment in this issue and @-notify [github usernames]


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/171