Include Firefox DOM storage in cleaner

CCleaner for Windows CCleaner Windows Suggestions
1

I suggest CCleaner expand its cleaning of privacy-related files to include Firefox's DOM storage, which is like cookies. See https://developer.mozilla.org/En/DOM:Storage and the Security section of http://ejohn.org/blog/dom-storage/

http://kb.mozillazine.org/Webappsstore.sqlite states "Deleting webappsstore.sqlite will delete any data web sites have stored there. A new file will be created when it is needed."

Today, I can add C:\Users\user_name\AppData\Roaming\Mozilla\Firefox\Profiles\profile_name\webappsstore.sqlite under Options\Include. If the file has already been deleted, I have to create a dummy file before including it in CCleaner. Adding a checkbox under Firefox for the Cleaner would make this privacy protection more accessible to the public.

2

CCLeaner Already cleans that (AFAIK) however with sqlite files they aren't removed (deleted) they are emptied (vaccumed) thus they don't show up on your detailed report after a clean.

3

Does anybody have a test web site that causes Firefox to update webappsstore.sqlite after closing? With this, I could test what CCleaner does. So far, I have only found sites that use session DOM storage, which does not cause an update to or creation of webappsstore.sqlite.

Also, which Cleaner checkbox under Firefox/Mozilla on the Applications tab affects webappsstore.sqlite?

4

I believe DOM files are handled by the Cookies Checkbox (at least for Internet Explorer they are)

5

I can confirm that it is indeed the cookies checkbox. (I simply ran just the cookies checkbox and checked the modified time of the file.)

6

My Firefox cross-session DOM storage file webappsstore.sqlite contains no cross-session info. When I used all the CCleaner v3.08.1475 checkboxes for Firefox v3.6.18, the data and time for webappsstore.sqlite did not change. Thus, I have no evidence that CCleaner cleans Firefox's DOM storage.

7

I cannot comment on 3.6.18 because I used Aurora (7.0a2) to test this.

8

webappsstore.sqlite contains no cross-session info. ... I have no evidence that CCleaner cleans Firefox's DOM storage.

Also no evidence that it fails to clean if there is nothing in there to be cleaned.

9

I propose to improve users' choice and understanding of CCleaner's action:

1. A separate checkbox under Firefox for DOM storage allows users to clean it without cleaning cookies. (I have cookies from my bank that I don't want to delete, and Firefox already has a mechanism for specifying which cookies are not deleted at the end of the session).

2. Showing the DOM storage file (webappsstore.sqlite) in the analysis details gives the user the choice of changing their mind about cleaning it, and it also alerts the user to the fact that some site created cross-session DOM storage.

3. Deleting webappsstore.sqlite (instead of vacuuming it) makes it easy for average users to understand that CCleaner cleaned it.

4. Deleting webappsstore.sqlite makes it easier to detect if CCleaner has a bug that prevents cleaning of DOM storage

5. Deleting webappsstore.sqlite reduces the average number of files on the hard disk, which increases backup speed.

Note that Firefox does not re-create webappsstore.sqlite until some visited site creates cross-session DOM storage. So there is no penalty in Firefox startup speed in deleting it.