Re: [w3c/IndexedDB] Specifying "indexedDB" storage bottle deletion when data is evicted by quota (Issue #400)

Unsorted thoughts:

* Beyond quota, other cases to consider are when a user clears storage, or when Clear-Site-Data is served. I think that's what @evanstade is alluding two - there's what to remove, and then the mechanics of removing it.
* https://github.com/w3c/IndexedDB/pull/334 is an attempt to define IDB as a storage endpoint, which I think would be a prerequisite for getting everything specified accurately.
* IDB spec has: _"A connection may be closed by a user agent in exceptional circumstances, for example ... clearing of the storage key's storage."_ (see https://w3c.github.io/IndexedDB/#database-connection). If we introduce the notion of clearing a bucket to Storage, this would be where we'd want to hook it up. 

So I think the needed changes are to introduce clearing logic (as needed) and hooks into Storage, and then finish up the integration of IDB and Storage.

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

Message ID: <w3c/IndexedDB/issues/400/1480351789@github.com>