Skip to content
This repository has been archived by the owner on Aug 9, 2021. It is now read-only.

Catch errors from unsupported/disabled features in browsers #772

Closed
zachferland opened this issue Apr 22, 2020 · 1 comment
Closed

Catch errors from unsupported/disabled features in browsers #772

zachferland opened this issue Apr 22, 2020 · 1 comment

Comments

@zachferland
Copy link
Contributor

Catch and relay useful error when indexeddb, localstorage, or in general the env does not meet the requirements of our library.

Also add docs on requirements, so that devs can handle themselves and relay that error to user. We can throw it so a dev understand its better, but they have still have to consume it and relay it in a useful way to an end user, so that user can maybe try diff env.

@zachferland
Copy link
Contributor Author

Links to #759

This also applies to to iframes we are using for 3id-connect and ipfs data caching, but those are more explicitly handling this already (or will) with fallbacks

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