-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty __browserfs_test__
indexedDB database is not deleted
#317
Comments
@jcubic Is this error still around? If so I can take a look at having BrowserFS clean it up after checking that IndexedDB works. |
I will test if the debug database is still there. I will need to check the latest version, will try when I found some free time, maybe on the weekend. |
james-pre
changed the title
BrowserFS create empty __browserfs_test__ indexedDB database
BrowserFS doesn't delete empty __browserfs_test__ indexedDB database
Sep 15, 2023
james-pre
changed the title
BrowserFS doesn't delete empty __browserfs_test__ indexedDB database
Empty __browserfs_test__ indexedDB database is not deleted
Sep 15, 2023
james-pre
changed the title
Empty __browserfs_test__ indexedDB database is not deleted
Empty Oct 25, 2023
__browserfs_test__
indexedDB database is not deleted
Please use zen-fs/core#21 |
Repository owner
locked and limited conversation to collaborators
Oct 25, 2023
Repository owner
unlocked this conversation
May 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you use browserFS you end up with two indexedDB databases one is empty and it looks like debug code.
It's because of the code that tests if indexedDB is supported:
The library should clean up after itself.
The text was updated successfully, but these errors were encountered: