Closed Joel889 closed 6 years ago
This is currently intended behavior, as tabs that are still open are in a protected state and people usually want their open tabs to keep working properly. I guess I could add an extra checkbox to apply the cleanup even to websites that are still open in a tab.
That makes sense, although I would imagine someone who is running "Clean All" manually (as opposed to using the time-based cleaner functionality), would specifically want to clean everything.
Yes, I understand the confusion and it should be improved.
This is still a bug (version 0.9). IMHO, instead of having two "Clean Now!" buttons in different tabs, why not add a checkbox to the "manual cleanup" tab that reads "Clean active tabs" or "Active Tabs" or similar.
Did you uncheck the "protect the currently open domains if..." checkbox? Because I did not change the default behavior. I just added an option to do change this behavior.
You are right, that fixes it. :)
I did notice that "current tab" cleaning won't delete subdomain cookies and also won't delete local storage for that domain. I know some of it is due to API limitations, I'm just not sure what the application would be to delete cookies only from that domain (but keeping subdomain cookies and local storage), nor whether it is clear to the user what is being done.
Subdomains are currently not cleaned, no. This is actually something that could be changed, but I haven't decided how to fix this yet. To understand why I haven't decided, understand, that there are two ways to look at cookie storage:
This could of course be solved by adding two buttons.. one for clean the current domain and one for clean the current domain and its subdomains. But then it'd be confusing to the user why this would only affect cookies and not local storage.
Localstorage should currently be cleaned, if it is the exact domain where the localstorage was saved on. If the localstorage was saved on a subdomain, then it won't be cleaned. This is actually due to limitations in the API, as there is (currently) no way to actually see which domains or subdomains have something in local storage. So at best, I could remember all domains the user was on so I can delete them later (which is what I do for the cleanup on start bit).
If you have a case, where local storage does not get cleaned with the "clean now" button on the "current tab" page, then please give me more information.
So, you see both of these issues are not just a simple decision and a couple of hours coding effort.
If you have a case, where local storage does not get cleaned with the "clean now" button on the "current tab" page, then please give me more information.
Perhaps I'm mixing up localstorage and IndexedDB. What isn't getting deleted on the "current tab" page is stored inside the profile folder under storage/default. I would imagine someone manually cleaning cookies from "current tab" would want everything deleted, not just cookies.
Did you uncheck the "protect the currently open domains if..." checkbox?
Perhaps the wording could be changed so that everything is deleted when the box is checked. This would be consistent with the wording scheme on the tab (box checked = things get deleted).
I've created an issue for that
I'm actually not sure myself where the files are stored. Are you sure the localstorage was stored on the exact domain? as said, subdomain cleaning is not as easy to solve with the currently available API.
I will investigate this further once I've finished moving to my new city. Saturday is the moving day, but getting settled in and having everything set up will take some more time.
I'm actually not sure myself where the files are stored. Are you sure the localstorage was stored on the exact domain? as said, subdomain cleaning is not as easy to solve with the currently available API.
youtube might be a good example. It creates files under
Thanks for the example, I'll try to reproduce it.
For the record, Indexed DB is what I'm referring to located inside your Firefox profile folder, under \storage\default.
Go to any webpage that sets cookies (verify with Firefox cookie manager). Click "Clean Now" under "Cleanup" (all boxes are selected). Cookie is still there. Clicking "This tab" clean now, will delete it. No domain rules have been set.