This has bugged me for awhile; when you 'Clear Private Data', SeaMonkey provides option check boxes for:
o Browsing History o Location Bar History o Download History o Saved Form and Search History o Cache o Cookies o Offline Website Data o Saved Passwords o Authenticated settings It is missing the Firefox option: Site Preferences This, to me, is a fairly important privacy issue. If you open the data manager (Tools|Data Manager) and click on the selection drop down, select 'Preferences Only'. There you most likely will find a list of websites that you may have used the zoom feature on. If you've no domains listed, simply go to a web page, View|Zoom and select a zoom level. Now look at the 'Preferences Only' and you'll find that website listed with your browser content zoom setting. All of the above is great & automatically saves your site zoom preferences... Until you wish to clear your private data. I checked one of my systems and it has visited domains/sites from 2 years ago. Doesn't seem to make much sense to be able to clear passwords, history, et al, and not be able to clear site preferences. The only way that I've found to do this is to load up the Mozilla, or any sqlite manager, and open the 'content-prefs.sqlite' file, and empty the groups, prefs, and settings tables. Note: Firefox also has an easy user way to clear & reset an individual page/tab during a session without using 'Tools|Clear Recent History': View|Zoom|Reset That not only restores the page to normal zoom, but also clears the entry out of the content-prefs.sqlite database. It appears there was some knowledge about the Firefox preference that cleans this: privacy.clearOnShutdown.siteSettings a few years back when porting the Sync UL over to SeaMonkey: https://bugzilla.mozilla.org/show_bug.cgi?id=576970#c29 ">+pref("services.sync.prefs.sync.privacy.clearOnShutdown.siteSettings", true); We don't have this, but we do have .item.urlbar" I've tried adding the pref privacy.clearOnShutdown.siteSettings in SeaMonkey 2.13.1 about:config and it does not work. Ping Neil & Jens: is there any workaround for this other than cleaning the content-prefs.sqlite tables directly? _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
