Basically you have to compromise with IE. Make sure the "enable DOM storage" box is ticked (so the websies will render properly), then add that setting VanguardLH mentioned in CCleaner and periodically clean it out. Not an ideal solution since I'd want it disabled all the time, but there you have it.
That said, this option should also be added to CCleaner for both Firefox and Chrome since disabling DOM storage in those browsers also makes certain websites both unreadable and unusable. Any solutions for that?
I don't think compromise is the right word here. DOM Storage is set enabled by default and rightly so, since you would Not want it disabled all the time since it would cause problems with some websites not rendering properly. We've confirmed and found that out the hard way.
It's already been expressed that we would like Cleaner engineers to add a check box for DOM Storage cleaning for those that use Internet Explorer so that it would clear itself automatically during a regular run cleaner session.
In the meantime, for IE users on Windows 7 anyway, it's so darn easy to add that checkbox yourself !!!
Simply download the attached winapp2.txt file from post 11, rename its extension to winapp2.ini, and place it in your programs folder:
C:\Program Files\CCleaner
Next time you open CCleaner click the tabs of: Cleaner> Applications>
...and you will see at the very bottom under the Internet Explorer listing, an entry called:
DOMStore*
...just put a checkmark in the box, and that's all there is to it.
...you can right click on it and click Analyze if you want and you'll see all the things listed.
Next time and from now on Every time, you run CCleaner it will automatically clear all that out.
I never think about this subject anymore, it just automatically gets taken care of when I run CCleaner
I don't think compromise is the right word here. DOM Storage is set enabled by default and rightly so,
There are many defaults configured for each web browser but that does not mean they are oriented to the user's preferences. In fact, and sad to say, rare few users visit their web browsers settings (all of them) because they don't care, assume the vendor is producing a product in the user's interest rather than some web sites, or don't understand the settings. Most web browsers come pre-configured with the option enabled to support the meta tag that will automatically redirect them to another page or even another domain without ever informing the user. All come pre-configured to allow mixed content (HTTPS and HTTP) within what should be a secured (all HTTPS) web page. Users because so infuriated with the abuse or misuse of cookies that web browsers added cleanup options for those but that occurred long after the abuse started.
DOM storage became an alternative to cookies because the users didn't know about it or understand it. Web sites got themselves a "cheat" to workaround cookies. DOM storage was to permit web sites to have even larger storage since cookies could only hold something like 4KB of data. Yes, it has some very good uses but web sites have used DOM storage in place of cookies not solely because of larger storage but also because web browser come pre-configured with DOM storage enabled by default, not enabled and disabled when the user chooses.
Then users started to wise up to how DOM storage is also abused just like cookies were and are. Some web browsers now include overt options to purge DOM storage on exit; however, that is not the default configuration so users are still leaving it enabled (unpurged) on exit. Putting a cigarette lighter hidden within the spare tire compartment means, yes, you have the option to use it but most car owners would assume there isn't one.
since you would Not want it disabled all the time since it would cause problems with some websites not rendering properly. We've confirmed and found that out the hard way.
I see you are on the side of web sites storing what they want on your host. The rest of us are not so inclined. Web browsers should default to disable DOM storage. Web sites should *ASK* their visitors if they want DOM storage enabled and explain why the site would like to store data on your host or, at least, warn you that the lack of DOM storage on your host means their web site may not be fully functional. It is easy enough to test if DOM storage is available just by trying to store a value/data pair there and then retrieve it to see if the value retrieved is what was attempted to save. So we should surrender privacy because they're too stupid or lazy to ask or warn? They don't tell because it's become their cheat to cookies.
It's already been expressed that we would like Cleaner engineers to add a check box for DOM Storage cleaning for those that use Internet Explorer so that it would clear itself automatically during a regular run cleaner session.
The supposed request is how old and still not available in CCleaner? Creating noise is about the only way users will get authors to modify their wares. Consider it a means of voting for a feature, enhancement, or change.
In the meantime, for IE users on Windows 7 anyway, it's so darn easy to add that checkbox yourself !!!
Simply download the attached winapp2.txt file from post 11, rename its extension to winapp2.ini, and place it in your programs folder:
C:\Program Files\CCleaner
Next time you open CCleaner click the tabs of: Cleaner> Applications>
...and you will see at the very bottom under the Internet Explorer listing, an entry called:
DOMStore*
...just put a checkmark in the box, and that's all there is to it.
...you can right click on it and click Analyze if you want and you'll see all the things listed.
Next time and from now on Every time, you run CCleaner it will automatically clear all that out.
Even easier is just to add the folder to the Include option in CCleaner to eradicate the contents of that folder. Yet this is a workaround and not considered as feature to clear DOM storage. A similar workaround is to tell users to just delete the folder, too, but that does not equate to a feature (option) within CCleaner whose purpose is to provide utility and ease of use in performing the cleanups, not in users having to do the research themselves to incorporate a workaround within CCleaner.
Plus, as you, I, and others have mentioned, DOM storage cleanup for Internet Explorer is simple (once known). For other web browsers, it's not so easy. Perhaps with Firefox the SQLite database file can simply be deleted where DOM storage is kept yet code is needed to interrogate where is the profile folder for Firefox (and there can be more than one so how to pick which one?).
If this is such an old topic covered so many times before then either Piriform is slow to act to add the option or really doesn't consider it a primary task. It is meant to be a cleanup tool that facilitates ease-of-use, not to require in-depth knowledge by its users to accomplish workarounds.
I never think about this subject anymore, it just automatically gets taken care of when I run CCleaner
Lucky you (and me and other Internet Explorer users) that the workaround to get CCleaner to cleanup DOM storage is easy. Do you think the majority of IE users visit here to even consider DOM storage or learn the workarounds? Getting an RFE (request for enhancement) to add DOM storage cleanup to CCleaner isn't just about you, me, and the few that visit here. RFE's (notice its use in the subject for this discussion) aren't about solving a problem just for yourself.
For what it's worth, I was mildly curious that although I had DOM store enabled I had nothing in the LocalAppData DomStore folder. So I did a little Googling and found that the DomStore on my box - Win8 with IE10 - was at C:\Users\Me\AppData\LocalLow\Microsoft\Internet Explorer\DOMStore.
Disappointingly there wasn't much in it, about twenty folders, some empty, holding around 50 files with a total of 7k of data. What's more I ran CC Cookies clean and all the files were deleted, except for container.dat which was emptied.
So I'm happy with the current setup. CC does remove Dom store - in my case.
I think that where the DomStore is located is set at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\LowCache\Extensible Cache\DOMStore\CachePath, Whether the value in this entry is what CC uses is anyone's guess.
I see you are on the side of web sites storing what they want on your host. The rest of us are not so inclined.
Hey not so fast - I am absolutely not on any websites side in any way shape or form, and did not intend for it to sound that way. I said that it needs to be enabled by default since some sites I need to visit don't work right otherwise, and so in the thought to have a decent browsing experience and work right I need it to be set enabled and rightly so. The problem with websites using DOM Storage for cheating to get information, well I Always try very hard Not to let that happen since I run CCleaner a lot ! ..especially after I make a purchase, visit any of my financial, or anything half important, etc, I run it; even at that I run CCleaner at least once a day anyway.
You 'may' have a tone with your post, but I am not going to take it personal because I like what your information stands for and so in that light I do support the technical information of what you've said, which is good stuff. My intentions are and always will be totally toward privacy and at the same time user functionality.
Yes it's slightly easier to use the 'Include' function to include the option, however without question I like to see the DOMStore* entry Listed in CCleaner even more, and is why I prefer it, after all it only takes 2 seconds to copy/paste the winapp2.ini file, done.
Anyway, all good stuff, and it's all good.
Yes CCleaner's owners/coders should absolutely have this option already included, but I'm not waiting around for them to see something so obvious; not to mention it would one more accomplishment to add to the list of good marketing promotion of the product.
For what it's worth, I was mildly curious that although I had DOM store enabled I had nothing in the LocalAppData DomStore folder. So I did a little Googling and found that the DomStore on my box - Win8 with IE10 - was at C:\Users\Me\AppData\LocalLow\Microsoft\Internet Explorer\DOMStore.
Disappointingly there wasn't much in it, about twenty folders, some empty, holding around 50 files with a total of 7k of data. What's more I ran CC Cookies clean and all the files were deleted, except for container.dat which was emptied.
So I'm happy with the current setup. CC does remove Dom store - in my case.
I think that where the DomStore is located is set at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\LowCache\Extensible Cache\DOMStore\CachePath, Whether the value in this entry is what CC uses is anyone's guess.
did you find out what happen after you clean Cookies?
What's more I ran CC Cookies clean and all the files were deleted, except for container.dat which was emptied.
did you find out what happen after you clean Cookies?
I'm not sure what you mean, after I ran a cookies clean all the cookies in the DomStore location were deleted and the folders left empty.
I have no Winapp2 or anything: my point is that bog standard CC (portable) does remove DomStore cookies, contrary to what others are reporting (on IE10 anyway). I don't know why there is this discrepancy, I have read reports that the DS location can be corrupted in the registry, but knowing what's going off on others' pc's is not easy.
Of course any cookies in CC's exclude section will not be removed from DomStore.
Disappointingly there wasn't much in it, about twenty folders, some empty, holding around 50 files with a total of 7k of data. What's more I ran CC Cookies clean and all the files were deleted, except for container.dat which was emptied.
you have about twenty empty folder where normally there should be only 4 folder with an index.dat (normally for IE8 and IE9)
by running Cookies cleaning in IE8 and IE9, each used folder will be left empty and new folder will be created and use
this will repeat for every cleaning till i don't know how much is the maximum folder can be create before maybe IE itself delete the folder
that why i put that link and ask if you can find whether the duplicate problem happen in IE10..if you read the thread, you'll know the problem
for IE10, probably index.dat change to container.dat..i don't know cause i only have IE8 and IE9 to test..will test on ie10
That folder location can be added into CCleaner's 'Options->Include' to add the folder location, however that isn't the only folder where DOMStorage resides. It's also in the SystemProfile located in C:\Windows - both areas accumulate data.
Looks like everyone or most respondents focused on just Internet Explorer. I said "All web browsers have had the DOM Storage feature for many years now." Each web browser (that CCleaner supports) is listed as a separate program under the Applications tab (with the exception for IE which is shown under the Windows tab). Each web browser has its own location for its DOM storage whether that be in a folder or within a database file.
If DOM storage is saved in a folder, tis easy to eradicate outside of the web browser, like adding the folder to the option in CCleaner to delete files in that folder. If DOM storage is saved in a database, it must be determined if that database contains only DOM storage or other data for the web browser. If only DOM storage is stored in the database file then the file could be deleted by CCleaner. However, if other data is stored in the database file then unwanted side effects happen by deleting that database file. Piriform probably won't write scripts in CCleaner to run SQL commands to modify the database file to remove DOM storage. So if DOM storage cleanup is added for a web browser that combines DOM storage and other client data inside the same database then CCleaner would need to show "DOM Storage + <listOther>" for the option to have CCleaner delete the database file.
While includes can be added within CCleaner to delete data that it does not currently cover, that was not the intent of CCleaner or its use by users. Users could probably defined includes for everything that CCleaner now cleans up. Who want to do that? There would be no point in installing CCleaner to do all those user-specified cleanups. Users could write a batch file for that. CCleaner is a convenience tool. It is NOT convenient to keep defining workarounds using includes on what to cleanup.