846350 - upgrading to version 22 changes user-set global cookie setting

Status: RESOLVED WONTFIX

(Core :: Networking: Cookies, defect)

Description

[Sid Stamm [:geekboy or :sstamm]]

In bug 818340 comment #84,  Ian Nartowicz writes:
> When I upgraded a profile from FF21 to FF22, cookie setting permissions were
> "downgraded".  A behaviour of "never allow 3rd party cookies" was changed to
> "allow third party for visited".  Possibly non-default cookie permissions
> shouldn't be touched at all.

Comment 1

[Jonathan Mayer]

I wasn't able to reproduce. If anyone is, could you please check the pref in about:config before checking it in the privacy preferences dialog? It'd be helpful to know if we're dealing with UI bustage. Thanks!

Comment 2

[Ian Nartowicz]

I couldn't reproduce this with a clean profile and now the profile that it did happen with is gone.  The only way I've found to reproduce the symptoms is if the pref cookieBehavior had the value 3 *before* I migrated to FF22, not really the fault of bug 818340.

Comment 3

[Daniel Veditz [:dveditz]]

This happened to me, too. I've blocked 3rd party cookies for years and after this change the value was set to allow "from visited". I did not check the about:config value before opening the options dialog so I don't know whether the underlying pref was changed or whether it was just the UI, and if it was just the UI I don't know if it would have saved the new value had I made any other changes.

Comment 4

[Daniel Veditz [:dveditz]]

I also couldn't reproduce by creating a fresh profile in an Aurora build, setting the cookie prefs, then opening that profile in Nightly.

Comment 5

[Jonathan Mayer]

Perhaps something like this is going on with network.cookie.cookieBehavior:

-Start with a pref to entirely block third-party cookies (1).
-Run a test build or Nightly and fiddle with the new cookie policy (3).
-Return to a version of Firefox from before the new cookie policy (default/0, since older versions don't know what to do with 3).
-Go back to a test build or Nightly (default/3).

Comment 6

[Ian Nartowicz]

Sorry, I missed the bugmail about the latest reply.  Fiddling the cookieBehavior preference will cause this, and it isn't necessary to install the new version and go back.  That still seems an unlikely thing to have happened to two different people.  I'll test some more, because I've updated my addon now to support this new setting.