User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Win64; x64; Trident/5.0; .NET CLR 2.0.50727; SLCC2; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E) Steps to reproduce: open data manager Actual results: all the websites you have ever visited are listed here Expected results: as I ask for my history to be erased this list should be blank.
It shouldn't, if you want to empty it - clear cookies, offline data and passwords
on OSX even if you clear everything the website preferences don't get cleared in the data manager. seamonkey version 2.22
It doesn't matter which OS you are using, if history is not cleared -> you have misbehaving add-on, check Safe Mode (Help - Restart with Add-ons Disabled)
history is cleared, websites preferences in the data manager are not. I don't have any add-on. I am not the only one noticing the problem, search google with: "SeaMonkey Site preferences are not cleared"
So, did you check Safe Mode?
I did try the safe mode but the websites preferences are still not cleared (and I erase every private data).
SeaMonkey 2.23 is out, is problem still present?
Confirming problem on trunk, sites Permissions and Preferences are not cleared. Steps to reproduce: 1) Visit a couple of sites which set preferences (I observe google, github, cnet and even mozilla.org/mozilla.net in data list) 2) Go to Tools - Clear Private Data, check everything, press Clear Private Data Now Expected result: Everything in Data Manager must be deleted Actual result: All sites Permissions and Preferences are still present
In Seamonkey 2.33 still some website data remains after the Clear Private Data command. At least this is: Permissions - TLS False Start using RSA Preferences - browser.content-full-zoom Passwords and Cookies seem to be cleared now.
I fixed some preferences problems in Bug 1269195. There was at least one index which was wrong / undefined. Could you recheck if this problem still is valid when 2.45 becomes available. The latest linux nightlys would also work.
No response. I assume its fixed in 2.45+ for now. Please reopen if this is not the case.