Cookie preference doesn't actually change when preference is changed




16 years ago
13 years ago


(Reporter: namoviczb, Assigned: darin.moz)


Windows XP

Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

I set preferences to reject cookies.  The NYT site, which sends me a daily
e-mail now wouldn't open from Outlook Express as it used to, on pretense that I
won't allow cookies.  This continued even after I reset preferences to accept
all cookies.  Today, the same thing happened when trying to to use PayPal:  the
PP site said my "browser would not accept cookies," even though settings accept all.

Reproducible: Always

Steps to Reproduce:
1.Seek to read a full article mentioned in the New York Time daily e-mail.
2.Seek to make a payment via PayPal.

Actual Results:  
NYT action results in cycling to find URL in window at bottom, then displays
message that it can't be done "possibly because you won't accept cookies."
PayPal stops the transaction, indorming that browser won't accept cookies.

Expected Results:  
When I change cookie behavior under preferences, Mozilla should actually change it

No crash occurs.

Comment 1

16 years ago
bob: could you try a few things for us?  first off, could you please try
creating a brand new user profile?  that will help eliminate any possibility
that this is related to settings (possibly hidden settings) in your browser.  thx!

Comment 2

16 years ago
There was a report similar to this one a few days ago; the reporter was using
firebird, and it was workforme'd since no one else could repro.

Perhaps there really is a problem here, but we've only seen two people who can
repro it so far... I'm not sure what it could be.

Comment 3

16 years ago
bug 212832 is the firebird bug

Comment 4

15 years ago
Same here.

Linux, Debian stable, Moz 1.6b (second compile)

Procedure :
1) Untar
2) Nuke ~/.mozilla
3) Run
4) Pref->Privacy->Cookies
5) Set "Disable cookies"
6) "Ok"
7) Pref->Privacy->Cookies
8) Notice that third radio box (based on privacy setting) is now gone
9) Set "Enable cookies" (doesn't matter which one)
10) "Ok"
11) Pref->Privacy->Cookies
12) Notice that cookies are still disabled
13) Accessing any web site will confirm that cookies are disabled

    Good luck...

    Jean II

Comment 5

15 years ago
   Forgot to add...
   o Work properly with 1.4 (same box, same profile).
   o Seems to work with 1.5 (did not do exaustive testing)
   o No privacy settings, no weird pref (only proxy settings)

   Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031210

   Jean II
jt: that is bug 227612, not this bug.

Comment 7

15 years ago
    Thanks Michiel, I thing bug 227612 is the one I see (even if the title of
this bug is a more accurate match).

    Jean II
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.