Re: [whatwg/storage] 'obtain a storage key' not currently suitable for non-storage APIs (Issue #131)

> What do you think about making this algorithm delegate to something like "obtain a non-storage storage key" that does everything apart from the "has disabled storage" check?

That works for me, although I wonder if "non-storage storage key" could be interpreted as being distinct from "storage key"?  If we instead went with something like "obtain a storage key for non-storage purposes" it avoids this problem but is also more wordy.

Another option could be to rename the existing function to something like "obtain a storage key if enabled" and move everything but the "has disabled storage" check into an "obtain a storage key" algorithm (and have the former delegate to the latter).

Any preference?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/storage/issues/131#issuecomment-1032189119
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/storage/issues/131/1032189119@github.com>