Chrome - FilesystemAPI - no confirm and then refresh #2
Description
The first time a page is visited, the user is prompted to allow LLS access to store files.
LLS does not initialize until the user click yes or no (which is the expected behavior), however...
If the user doesn't click either yes or no and then refreshes the page, LLS ends up initializing but with IndexedDB instead of the FilesystemAPI as the provider. If the user now clicks yes then the next time they visit the page LLS will initialize with the FilesystemAPI instead of IndexedDB. This will cause a data loss between two sessions.