Closed
Bug 713995
Opened 13 years ago
Closed 12 years ago
Firefox>Preferences>Privacy>Cookie settings forgotten
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: derek, Unassigned)
Details
Attachments
(7 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0) Gecko/20100101 Firefox/10.0
Build ID: 20111221135037
Steps to reproduce:
I chose:
Firefox>Preferences>Privacy>History>Firefox will [USE CUSTOM SETTINGS FOR HISTORY]
I then checked the following:
> Remember browsing history
> Remember download history
> Remember search and form history
> Accept cookies from sites:
>> Accept third-party cookies
>>> Keep until [THEY EXPIRE]
Closed Preferences window
Reopened Preferences window
Quit Firefox
Actual results:
Cookie settings changed from those set to the following: (see screenshot coming after this)
After closing and then reopening Preferences>Privacy, the option [REMEMBER BROWSING HISTORY] had unchecked itself
After Quitting and then relaunching Firefox the same settings had changed to:
Preferences>Privacy>History>Firefox will [REMEMBER HISTORY]
Expected results:
The settings made in Preferences should have stayed the way I set them, both after closing and then reopening the Preferences window, and after Quitting and then relaunching Firefox
Reporter | ||
Updated•13 years ago
|
Summary: cookie settings forgotten → Firefox>Preferences>Privacy>Cookie settings forgotten
Reporter | ||
Comment 1•13 years ago
|
||
'Remember browsing history unchecks itself after opening and closing Preferences window
Reporter | ||
Comment 2•13 years ago
|
||
Preferences>Privacy>Cookies reset themselves forgetting Custom Settings
Reporter | ||
Comment 3•13 years ago
|
||
One apparent consequence is that this stops Firefox working properly with certain newspaper logged in comment sites such as New York Daily News and Los Angeles Times Facebook interface, according to feedback from their technical support.
Email history available as and when needed.
Severity: normal → major
Comment 4•13 years ago
|
||
Have you completed the troubleshooting steps at https://support.mozilla.com/en-US/kb/Preferences%20are%20not%20saved
Component: General → Untriaged
QA Contact: general → untriaged
Reporter | ||
Comment 5•13 years ago
|
||
I tried just now, but it said "if there is no user.js file, this won't help you". There is no 'user.js' file - screenshot attached.
Reporter | ||
Updated•13 years ago
|
Version: 10 Branch → 11 Branch
Comment 6•12 years ago
|
||
Derek -- there are other troubleshooting tips on the "Preferences are not saved" support page you might try. https://support.mozilla.org/en-US/kb/how-to-fix-preferences-wont-save
Does this error still happen with an updated version of Firefox? I could not reproduce it.
Flags: needinfo?(derek)
Whiteboard: closeme 2013-02-08
Reporter | ||
Comment 7•12 years ago
|
||
Liz the bug is still there.
I choose Firefox>Preferences>Privacy - and I note that "Firefox will remember [HISTORY]" is selected.
I change this to "Firefox will remember [USE CUSTOM SETTINGS FOR HISTORY]" and make settings as desired.
I close the Preferences window and then immediately reopen it.
I note that "Firefox will remember [HISTORY]" is re-selected instead of [USE CUSTOM SETTINGS FOR HISTORY]"
100% reproducible in current version 19.
Flags: needinfo?(derek)
Version: 11 Branch → 19 Branch
Updated•12 years ago
|
Whiteboard: closeme 2013-02-08
Comment 8•12 years ago
|
||
Note that if the custom settings selected are functionally the same as any of the non-custom settings, the preferences window intentionally reverts the selected choice to either Remember History or Never Remember History. According to the choices listed in comment 0, that is what is happening here - those choices are functionally indistinguishable from the effects of Remember History, so this seems to be working as intended.
Comment 9•12 years ago
|
||
jdm: That makes sense.
Derek: Are sure you are losing Exceptions or particular cookie information for the two news sites you mentioned? Is the issue here actually that you expect to be logged in automatically to the LA Times but that is not working?
Flags: needinfo?(derek)
Reporter | ||
Comment 10•12 years ago
|
||
If this is intentional behaviour, then I disagree with it. When the Preferences>Privacy page is opened, if the first option [REMEMBER HISTORY] is checked and the window closed and then reopened, the option remains checked. If [NEVER REMEMBER HISTORY] is checked, and then Preferences closed and the reoponed, it too remains checked.
However if the third option [USE CUSTOM SETTINGS FOR HISTORY] is checked, it remans checked only for as long as the Preferences window is open. If the Preferences window is closed and then reoponed, the checked third option is unchecked, and the first option is checked. This is inconsistent with the behaviour while the window is open, and can only lead to the assumption that the Custom Settings have been cancelled, even though they reappear as previously set if the third option for Custom Settings is again selected.
Images attached of these behaviours.
Flags: needinfo?(derek)
Reporter | ||
Comment 11•12 years ago
|
||
Reporter | ||
Comment 12•12 years ago
|
||
Comment 13•12 years ago
|
||
Agree with jdm.
there are two specific cases which one means Remember history and the other one means never remember history. If you choose these two predefined settings in custom settings, they will switch to those items.
So I think that it works properly at the moment.
Reporter | ||
Comment 14•12 years ago
|
||
Maybe it's working internally, in that the settings are being remembered, but why does the display not show that custom selection on relaunch or re-opening the window? One should not feel that one has to select the preference on every fresh launch of the browser or re-opening the Preferences window, which is the unmistakable impression created by the fact that the display always reverts to showing a setting other than that chosen by the user.
Reporter | ||
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•