Closed
Bug 259208
Opened 21 years ago
Closed 20 years ago
Cookie preference to ask before setting a cookie is confusing in 0.10 (1.0PR)
Categories
(Firefox :: Settings UI, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: kberk.spamaway, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040911 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040911 Firefox/0.10
Maybe I just need to get a good nights sleep, but I don't remember being
confused by the wording in the cookie privacy settings until now when I
installed 0.10 (1.0PR) and almost freeked out thinking the cookie management
features had been cut down from .93.
Basically, the wording "keep cookies" really confused me. I always set Firefox
and Mozilla before it to ask me before setting a cookie. I normally then tell
it to make my decision persistent.
With 0.10 (1.0PR), I got confused because "keep cookies" did not mean the same
thing to me as setting them in the first place. I just happend to look through
it and see "ask every time", but then I was wondering why I'd want to be asked
every time if I wanted to keep a cookie? I wanted to just be asked if I wanted
the cookie set in the first place. I don't know if the wording changed between
.93 and this new release, but it confused me as to what it was going to do. When
I read it, it didn't sound like it was the same feature I was looking for.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
| Reporter | ||
Updated•21 years ago
|
Severity: major → normal
Comment 1•20 years ago
|
||
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:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•20 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Comment 3•19 years ago
|
||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in
before you can comment on or make changes to this bug.
Description
•