Closed Bug 302553 Opened 19 years ago Closed 19 years ago

Enabled "Cookie Warning" Option on Pref Bar Does Not Stick Window-to-Window or Session-to-Sesson

Categories

(Firefox :: Settings UI, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: rjemery, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.8) Gecko/20050511 MultiZilla/1.6.3.0e
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.8) Gecko/20050511 MultiZilla/1.6.3.0e

I use the latest versions of FireFox on both my W98 and Linux FC3 machines.  I
also have the Preferences Bar installed on each.  On the Preferances Bar, I
usually have Cookies disabled and Cookie Warning enabled.  It is the latter that
does not hold.

With FireFox open, the Pref Bar showing, and Cookie Warning enabled, if I then
open a new window, the Cookie Warning box will be unchecked in the new window. 
The Cookie Warning box, if enabled, only holds true for the window that is open
and not any subsequent new windows.  If I were to close FireFox then reopen it,
the Cookie Warning box will similarly be disabled.

I have tried various settings under Tools > Options but none or combination
thereof seem to have an effect on retaining Cookie Warning once set.

This problem does not exist with Mozilla, where I also have the Preferences Bar
installed and Cookie Warning enabled.  There, the option holds true for any new
window opened or whenever Moz is reinvoked.

Reproducible: Always

Steps to Reproduce:
1.Open FireFox.
2.Enable Preferences Bar
3.Enable Cookie Warning
4.Open new window -OR- close FireFox and reinvoke FireFox.

Actual Results:  
Cookie Warning will be disabled.

Expected Results:  
Retain the Cookie Warning enabled setting.
This sounds like a bug in the extension and not in firefox. Please contact the
extension author about extension bugs -> Invalid

Please reopen if you are able to explain how this is a firefox bug and not an
extension bug.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.