comment box requires 3rd party cookie acceptance

UNCONFIRMED
Unassigned

Status

()

--
enhancement
UNCONFIRMED
8 years ago
7 years ago

People

(Reporter: JimScott, Unassigned)

Tracking

3.5 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101130 Firefox/3.5.16 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101130 Firefox/3.5.16 ( .NET CLR 3.5.30729)

I am finding more and more comment boxes are requiring the browser to accept 3rd party cookies (presumably as the site owner farms out the comment handling to a ... 3rd party).

Reproducible: Always

Steps to Reproduce:
1. Load site.

2. Comment box header warns:
Warning: A browser setting is preventing you from logging in. [[Fix this setting to log in.]]

3. the link activates a child window superimposed over the main window reading:

Help: Enabling 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 disqus.com as an allowed domain.


Actual Results:  
User unable to log in to make comments (not that that is necessarily a bad thing ...).

Expected Results:  
Could we have a list, similar to the Exception List for accepting cookies; except in this case it would list 3rd party cookies to be accepted even if Accept 3rd Party Cookies is un-checked (ie, disallowed). And, for the purists, it's own expiration pull-down list I suppose.

I have been seeing more and more comment boxes doing this. It is only a matter of time before it's a wide-spread problem <quote>with Firefox<unquote>. Strictly it isn't a bug per se as it is a reaction a new programming paradigm that makes everyone's life more difficult but must be dealt with.

The work-around is to just accept 3rd party cookies willy-nilly; a solution I abhor with all the advertising and tracking junk out there.
(Reporter)

Comment 1

8 years ago
Created attachment 501581 [details]
shows typical comment box (p1) and popup message (p2)
Not sure what to say to this since it's not a Firefox bug.  Perhaps envangelism?
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 3

8 years ago
My apologies. As usual, my verbosity obscured my point.

Which is, could we have added an Exceptions button and internal list next to the "Accept third-party cookies" check box (Tools | Options | Privacy tab | History section)?

This would allow one to specify ONLY those third-party cookies that would be acceptable, per se.

The present "Exceptions" button / internal list presumably does not override the "Accept third-party cookies" check box setting and therefore does not work for this.

As such, this wasn't intended as a "bug" per se but rather a feature; which I estimated would be easy to add since it essentially uses the same code just for a different list.

Did I get the importance wrong? Should it be set to "enhancement"??
> Did I get the importance wrong? Should it be set to "enhancement"??

Yeah, that sounds more like a feature request; it belongs under enhancement.  I've made that change, thanks.
Severity: minor → enhancement
Status: NEW → UNCONFIRMED
Ever confirmed: false

Updated

8 years ago
Version: unspecified → 3.5 Branch

Comment 5

8 years ago
Voting for this enhancement because NextBus on http://www.wmata.com also requires third-party cookies in order to work properly.

Comment 6

7 years ago
I think I can further strip down the request text:

In cookies manager, display a working check box for each cookie domain, reading:

"[ ] Let them track my whereabouts in all the web."

--
You need to log in before you can comment on or make changes to this bug.