Closed Bug 322199 Opened 19 years ago Closed 1 month ago

Visual feedback when cookies are denied

Categories

(Camino Graveyard :: General, enhancement)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE
Milestone:
Future

People

(Reporter: mg_list, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060102 Camino/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060102 Camino/1.0+

Similar to the popup warning icon appearing in the lower left corner I suggest adding a similar icon which shows a denied cookie. Clicking on it shows an option to add it to the appropriate allow list.

Reproducible: Always

Steps to Reproduce:
1. Select preference "deny all cookies"
2. Navigate to site which needs cookies
Actual Results:  
Site may not work correctly

Expected Results:  
3. Icon in lower left corner shows that cookie was denied
4. Click on it and select "allow cookies for this site"
5. Reload site, now it should work correctly
Confirming as valid enhancement request; this has potential to be a LOT more useful than our popup-denied feedback.

Jasper, wanna see what you can come up with for an icon?

cl
Severity: minor → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → Camino1.1
"What does Fx do?"

The reason I ask is this: Adding more and more icons to the status bar seems against our overall "message" of Camino. This is definitely a valid RFE, but it doesn't seem like it's something most of our users would need or use.

Mike, what do you think about this?
FWIW, although the functionality could be useful to me *some* of the time, I'm with Sam on this one...it makes our status bar (which some people already want to hide, meaning we'd have to come up with another place to show this) even more crowded.
IMHO if people like to hide the status bar they loose the notification facility - I wouldn't move that somewhere else.

I suggest adding a label next to the icon which contains the same text which is shown if hovering over the icon, this would clarify the meaning of the icon. 

A few unsolved issue: What happens if both the popup window and the cookie was denied? What happens if several cookies are denied?
I see this as an interesting challenge:

We have different events that we want to notify the user of. One example is cookie blocking, another (to me more critical) is popup blocking.

Unless we want to "solve" it by cluttering the status bar with icons or (a classic) adding preferences for it, we need to be a little innovative here. 

How about trying something new? I don't know what that'd be, but I think we should see this as a challenge of being creative with our UI + keeping Camino as simple and slick as it is today.
Also remember that for a given page, there could be a dozen different sites whose cookies are blocked (ads), and dozens of total cookies.
(In reply to comment #6)
> Also remember that for a given page, there could be a dozen different sites
> whose cookies are blocked (ads), and dozens of total cookies.
 
Couldn't we handle this about the same way Nick is handling multiple RSS feeds on one page?

cl
This would be very helpful. The current cookie-pop-up is quite disturbing as it pops up all the time because the whole web wants to set cookies. In consequence, no one uses it and the cookie list gets either crowded, or many sites don’t work (and it is not possible in Camino to add a site manually to the cookie permissions list).
There is a Firefox extension (Extended Cookie Manager) that adds some basic version of this, though being far from perfect and adding a icon to the status bar.
(In reply to comment #8)
> and it is not possible in Camino to add a site manually to
> the cookie permissions list

Sure it is, as long as that site has succeeded in setting a cookie that still lives in your cookies.txt file.

Prefs -> Privacy -> Show Cookies, then select a cookie from the desired site. Click the tool menu, or right-click the cookie, and you can add its host to the exceptions list. Right now, what you *have* to do is to *block* that host (currently the only way of putting the site on the exceptions list), then go into the exceptions list and set the *desired* policy.

We should probably consider adding a couple items to that menu (at minimum, an "Allow cookies from sites matching %@" item, and possibly a "Force %@ cookies to expire at the end of each browsing session" item), but that's a discussion for a new bug, which someone should go file. (Hint, hint.)

cl
How about using the new "attention bar" for this (which is now only used in 1.1 builds for popup blocking)?
*** Bug 348406 has been marked as a duplicate of this bug. ***
*If* anywhere, this belongs in the status bar, but see comment 2.
Assignee: mikepinkerton → nobody
QA Contact: general
Target Milestone: Camino1.1 → Future
After reading the comments, I understand if there is any issue of where to put the UI or an icon.  This is a tough problem.  But this bug seems to come up every few months -- someone else phrases it in a different way.  Seems like there is a valid demand for some sort of selective cookie functionality.

If the fear is that most users won't use it and it will clutter the UI of a browser window, maybe there is a different way to hide it from the main UI.  Could a menu option (with cmd key) but added, somewhere buried, that could open up a drop-down sheet with a list of cookies?  Then the user could select one and move right along.  How would a user know when to do this?  When a site says "we require cookies..."

(I don't know if this is against Camino's ethos, but there could be a hidden "Advanced" menu that you turn on in preferences, that exposes this and some other features. Otherwise, maybe this could go in the Edit menu along with Fill Form.)

Maybe not perfect, but I'd like to throw out another option to discuss, with hopes of adding this feature somehow.  thanks!
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.