Open Bug 770322 Opened 10 years ago Updated 9 years ago

expose "accept third-party cookies" choice in Data Manager (about:data)


(SeaMonkey :: Passwords & Permissions, defect)

SeaMonkey 2.11 Branch
Not set


(Not tracked)


(Reporter: info, Unassigned)


User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120621 Firefox/14.0 SeaMonkey/2.11
Build ID: 20120621204936

Steps to reproduce:

I tried to comment on a site ( the awesome post ) using Disqus.  Disqus helpfully warns "A browser setting is preventing you from logging in. Fix this setting to log in" and talks about third-party cookies:

  In order to properly log you in, your browser needs to accept cookies from all domains.
  Open up Settings > Privacy. Then, make sure Accept cookies from sites is checked. Also, make sure Accept third-party is checked as well.
  After closing your settings, you may try logging in again.
  Optional: If you would rather add an exception just for Disqus, click “Exceptions...” and add as an allowed domain.

I do indeed block third-party cookies: Edit > Preferences > Cookies > "Allow cookies for the originating site only" is checked and my about:config has a network.cookie.thirdparty.sessionOnly set to true. So I need to make an exception for Disqus, so I visit about:data

Actual results:

The choices for Set Cookies in Data Manager's Permissions tab are only Allow, Allow for Session, and Block. If I add a cookie permission and set it to Allow, next time I look at permissions for it's gone, I think because this is the default.

Expected results:

Data Manager needs a way to set an exception "accept third-party cookies for (from?) this site".  I'm pretty sure you used to be able to set this in SeaMonkey.
Ever confirmed: true
IMO this is WMF, perhaps it is not clear how this works, but it does.

> "accept third-party cookies"

The Allow (or Allow for Session) selections "accept all cookies" which includes "third-party cookies".

(Now that may not be obvious from the terminology used in about:data either.)

Now when you uncheck 'Use Default', the selection then defaults to Allow, but in doing so, it does not actually effect anything (AFAICT).

What you must do is to select some other setting first, then the setting you wish to set, & at that point your selections should be saved.  (/Now that behavior should be changed as it is not clear at all./)  So if after unchecking 'Use Default', you clicked 'Block', then 'Allow', the 'Allow' selection would be enforced, allowing third-party cookies.
	<therube>	skierpage: i think it is WFM as is ?
	<therube>	network.cookie.thirdparty.sessionOnly;true
	<therube>	Privacy & Security | Cookies -> Allow cookies for the originating website only
	<therube>	then go to about:data, add, uncheck Use Default, check Block, check Allow
	<therube>	load & (disqus) login
	<therube>	username/password dialog pops up
	<therube>	(now granted the about:data part of it is a pita & like who would ever figure it out, but it looks to work)
	<NeilAway>	therube: he shouldn't have to check Block
	<therube>	i agree, but that doesn't seem to be what the bug is about?
Thanks for your comments. I hope someone can improve the procedure to override cookies in SeaMonkey. I just spent twenty minutes trying to get YouTube commenting to work, struggling to apply the Firefox "Just add exceptions for" workaround in SeaMonkey. When I searched for help... I came across my own 2-year old bug post :-)  I found trying to add cookie permissions for when I already had settings for confusing and bug-ridden, even following your instructions.

Anyway, I mentioned "allow" means third-party, and put the SeaMonkey-specific procedure, at
You need to log in before you can comment on or make changes to this bug.