Closed
Bug 174556
Opened 22 years ago
Closed 22 years ago
whitelisting cookies
Categories
(Firefox :: Settings UI, defect)
Firefox
Settings UI
Tracking
()
People
(Reporter: moxfox, Assigned: bugzilla)
Details
The one thing I've never quite understood is that,(especially since there is no P3P policy in use), why is it not possible to whitelist some of the cookies, similarly to popups (as possible in Phoenix 0.3)? For me, I'd rather have cookies turned off (well, per session, anyways) for the 90% of the time, but for couple of sites, this causes annoyance, since those sites store information that I have to input every time I visit them. To me it seems that all the 3, cookies, images and popups, should be controlled similarly, rather than differently. One could even use the [i] -icon for all of them...
Comment 1•22 years ago
|
||
Warn me before accepting cookies covers this functionality. This functionality exists and will be returned or not returned in the work going on at bug 161749 *** This bug has been marked as a duplicate of 161749 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•22 years ago
|
Summary: [RFE] whitelisting cookies → whitelisting cookies
Umm, I don't think "warn me before accepting cookies" cuts the cake. While it's technically possible to arrive at the same state concerning the cookies, it definately isn't the same workload. Correct me, if I'm wrong, but isn't it that if "warn me..." is turned on, the browser keeps asking for acknowledgement for cookies on every new site I visit? Since ~90% of the (say, 20-30 sites... an average for a week) sites I visit should not store cookies and only ~10% (2-5 sites) should, it's annoyingly much work, to accept/deny each cookie for each of those sites (with advertisements on sites, it can be up to 5 hosts per single webpage). Sure, one does not have to do that more than once per site, but I visit all kinds of new sites every now and then and 99,9% of them should not store cookies. So, for me, the "it should just work" -idea is that cookies should be denied by default and just a few of them should be whitelisted.
Comment 3•22 years ago
|
||
I made a similar suggestion in bug 67580 ("[RFE] cookie-managing ui with fewer dialogs"). Once the user checks a box in prefs, the following would happen: * The default for cookies from new sites would be "session only". * There would be a cookie indicator in the status bar, and clicking the indicator would turn the cookie into a permanent cookie. The icon would change to reflect that the cookie had been accepted. * Double-clicking the cookie would open a dialog listing the cookies and values for the site. (Or, it might open the cookie manager and select the relevant cookies.) * Any new cookies set by the same site would be permanent cookies. This way, if you never double-click the cookie indicator, you don't have to deal with the fact that some sites store multiple cookies and other sites store the same information in a single cookie. I agree with Mox that duping this against bug 161749 ("finish tearing prefs UI to pieces and then make it not suck") doesn't make sense.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 4•22 years ago
|
||
*** This bug has been marked as a duplicate of 75915 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•