- From: Domenic Denicola <notifications@github.com>
- Date: Fri, 17 Apr 2020 09:17:59 -0700
- To: whatwg/storage <storage@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 17 April 2020 16:18:13 UTC
Relaying some discussion from IRC: > Let key be the result of obtaining a storage key from environment. (This should be less hand-wavy.) I assume most of the time the storage key will be an origin. But not always. In particular this step will allow us to define both double-keying and blocking of storage. Note that currently storage is blocked in opaque origins on a per-API basis (e.g. [localStorage](https://html.spec.whatwg.org/multipage/webstorage.html#storage-object-initialisation-steps), [idb.open()](https://w3c.github.io/IndexedDB/#dom-idbfactory-open)). Those mechanisms should probably be subsumed here, so that if _environment_ is an opaque origin, key is failure, and the rest of the algorithm fails. This also allows other scenarios to block storage by intervening at the "obtain a key" stage. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/storage/issues/18#issuecomment-615336554
Received on Friday, 17 April 2020 16:18:13 UTC