You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
publicstaticisAvailable(): boolean {// In Safari's private browsing mode, indexedDB.open returns NULL.// In Firefox, it throws an exception.// In Chrome, it "just works", and clears the database when you leave the page.// Untested: Opera, IE.try{returntypeofindexedDB!=='undefined'&&null!==indexedDB.open("__browserfs_test__");}catch(e){returnfalse;}}
The library should clean up after itself.
The text was updated successfully, but these errors were encountered:
dr-vortex
changed the title
BrowserFS create empty __browserfs_test__ indexedDB database
BrowserFS doesn't delete empty __browserfs_test__ indexedDB database
Sep 15, 2023
dr-vortex
changed the title
BrowserFS doesn't delete empty __browserfs_test__ indexedDB database
Empty __browserfs_test__ indexedDB database is not deleted
Sep 15, 2023
dr-vortex
changed the title
Empty __browserfs_test__ indexedDB database is not deleted
Empty __browserfs_test__ indexedDB database is not deleted
Oct 25, 2023
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: