Skip to content
This repository was archived by the owner on May 3, 2022. It is now read-only.

Secure contexts only? #16

Closed
inexorabletash opened this issue Feb 26, 2018 · 1 comment
Closed

Secure contexts only? #16

inexorabletash opened this issue Feb 26, 2018 · 1 comment

Comments

@inexorabletash
Copy link
Member

While Indexed DB is usable in non-secure contexts, we are likely to offer new native storage APIs only in secure contexts since storage is a "powerful feature". We followed that path for SW's Cache API.

This might be predicated on whether we expose the layered web API concept in all contexts. If that's already been decided in favor of restricting, then this is implicitly resolved. Otherwise... could go either way IMHO.

@domenic
Copy link
Collaborator

domenic commented Mar 16, 2018

I think this should be restricted, as a new way to store persistent data. I added a step that makes importing this module in non-secure contexts throw. Alternately we could make any usage of a StorageArea in a non-secure context throw, but this seemed to make more sense at least to me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants