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
Localstorage is already managed by chromium, but it should be possible to access it like so:
A list per domain of everything in the localstorage, where entries can be deleted one at a time or per domain
Settings for autoclearing the localstorage when closing a tab after x seconds delay
A setting to clear everything in the localstorage when closing Vieb
Unlike cookies, electron does not provide an api for it. This means that this issue needs to be solved in one of the following ways:
Access the files directly with level (files are in /home/user/.config/Vieb/IndexedDB and /home/user/.config/Vieb/Local Storage, but it's not a proper solution I think)
Only allow a full wipe of these folders, optionally after closing Vieb and forget about displaying a proper entry list
A different approach I'm not aware of
Sadly, most npm packages claiming to access the localstorage are simply alternative implementation of the localstorage specification, which are not suitable for this use case. The packages actually accessing the localstorage are mostly based on executeJavaScript, which will only find the localstorage for the currently opened website. This method is therefor also not considered a solution to the problem.
Please feel free to suggest alternative options to access the chromium localstorage in a more fitting way, as these are the only two options I could think of. Out of these two, I would likely go for the second one, because it's much easier to implement and a lot less hacky.
The text was updated successfully, but these errors were encountered:
Localstorage is already managed by chromium, but it should be possible to access it like so:
Unlike cookies, electron does not provide an api for it. This means that this issue needs to be solved in one of the following ways:
/home/user/.config/Vieb/IndexedDB
and/home/user/.config/Vieb/Local Storage
, but it's not a proper solution I think)Sadly, most npm packages claiming to access the localstorage are simply alternative implementation of the localstorage specification, which are not suitable for this use case. The packages actually accessing the localstorage are mostly based on executeJavaScript, which will only find the localstorage for the currently opened website. This method is therefor also not considered a solution to the problem.
Please feel free to suggest alternative options to access the chromium localstorage in a more fitting way, as these are the only two options I could think of. Out of these two, I would likely go for the second one, because it's much easier to implement and a lot less hacky.
The text was updated successfully, but these errors were encountered: