provide timestamp with cookie exceptions

RESOLVED WONTFIX

Status

()

--
enhancement
RESOLVED WONTFIX
14 years ago
12 years ago

People

(Reporter: phil, Assigned: bugzilla)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
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

When you start browsing with disabled cookies, you always find web sites that
absolutely require a cookie. Then you go to the cookie exception dialog and want
to find the website that you are browsing to allow one cookie. Unfortunately,
this common task is quite tedious to achieve. A normal user is going to have 100
of sites listed here. A first solution is to provide a search dialog but this is
the object of another bug report. A second solution which does not overlap with
the first one would be to keep a timestamp of every site trying to set-up a
cookie.That way, you would just sort the list by timestamp and the first one is
the site you just tried to access. You disable it and that's ok.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
First, a "normal" user will never be aware that such a concept exists.  Lots
don't even understand what a cookie is, and don't really want to have it
explained to them.  Normal users rarely even use context menus, let alone manage
site permissions for 100+ sites.

As to the suggestion itself, this isn't supported in the backend, and probably
won't be for the forseeable future.  IMO its anything but a perfect solution. 
Something that's more like the popup blocking concept is more likely.  Being
able to set site permissions directly (for cookies/images/page style/and
*possibly* scripts) is one of the features planned for Firefox 1.5.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WONTFIX
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.