On 12/12/2014 9:10 PM, Paul B. Gallagher wrote: > This evening, I cleared all private data (including cache and cookies), > and then visited nhl.com. > > Immediately after aborting their troublesome javascript,* I inspected my > cookies and discovered that google.com had set a cookie. > > Now, my cookie policy at Edit | Preferences | Privacy & Security | > Cookies is "Allow cookies for the originating website only (no > third-party cookies)." > > So how was Google able to set a cookie if I never visited their site? > > It's bad enough that they update their dossier on me when I visit their > own sites, do they have to do it everywhere else, too?\ > > More to the point, how can I set SeaMonkey to do as it says and block > third-party cookies? > > -------------------- > * -- They have a series of annoying scripts that grind SM to a halt and > must be aborted before the site becomes usable. The URLs are constantly > changing; today's version was at > <http://cdn.nhle.com/projects/ice3-ui/com.nhl.ice3.ui.t5.components/GlobalPageImports/dist/js/GlobalPageImports.min.js?v=8.9:1>. > > And I'm constantly updating my custom filter in AdBlock Plus. That isn't > my question. >
I ignore the presence of third-party cookies. I merely mark the file cookies.sqlite as read-only. Before that, I deleted all cookies and then carefully visited only those Web sites where I wanted cookies. I terminated SeaMonkey before marking the file read-only; that assured me that session-only cookies were deleted. -- David E. Ross I am sticking with SeaMonkey 2.26.1 until saved passwords can be used when autocomplete=off. See <https://bugzilla.mozilla.org/show_bug.cgi?id=1064639>. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
