173521 - Expand "allow cookies" dialog sheet

Status: RESOLVED WONTFIX

(Camino Graveyard :: General, enhancement)

Description

[Matt Fago]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722

Expand dialog to allow/deny cookies, especially add an option to allow cookie,
but keep in only until end of session or only for a specified time (eg 30 days).
This would be similar to what Omniweb and iCab do.

I would love to see more detail about the cookie in question (ala iCab) revealed
by a "details triangle" (what is the correct name for this widget?).

I realize that cookies are still under construction...

Reproducible: Always

Steps to Reproduce:

Comment 1

[Simon Fraser [no longer active]]

Expire on quit is bug 174070. Displaying cookies is bug 182540. So I think we're
covered here.

Comment 2

[Stuart Morgan]

Maybe re-open this bug for discussion? Bug 174070 is to remove *all* cookies on
quit, which is substantially different (and less useful) than doing so on a
per-site basis; setting the option for bug 174070 means it's impossible to have
any sites with long-term cookies.

This could be a very powerful option for people who want to use cookie-requiring
sites without opening themselves to long-term tracking. It wouldn't require any
additional prefs, as it would be only a button on the sheet and another option
in the Edit Site allow/deny column.  Non-trivial to implement, but certainly
worth thinking about.

Comment 3

[Stuart Morgan]

Reopening, since bug 174070 is specifically a request for a GUI for
user_pref("network.cookie.lifetime.enabled", true);, whereas this is about
cookie-specific expiration control.  Also, cookie info disclosure *before*
accepting the cookie definitely isn't covered by bug 182540.  This seems
distinct enough to get it's own RFE for discussion.

Comment 4

[Oscar van Vliet]

Mozilla has a feature for downgrading all cookies from a site to session cookies.
I would really like that. It is the main reason why I don't want to use Camino
right now.

Also, from what I can see, the other bugs do not cover giving extra information
on a cookie in the requester window. The code for retrieving this info is
available in Mozilla (QED) so I hope the interface can be made without too much
effort.

Thanks for the hard work!

Comment 5

[Samuel Sidler (old account; do not CC)]

I'm pretty sure that adding an interface for this would take away some of the
simplicity. I'll keep this, however, just target it for Future. My suggestion is
WONTFIX.

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

*** Bug 289657 has been marked as a duplicate of this bug. ***

Comment 7

[Joel Siegel]

FWIW, I'd be really happy if the "allow cookie" sheet simply reproduced the
functionality currently available in Seamonkey and Firefox.  It may be ugly and
some may complain it's too complicated and confusing especially for novice
users, but it gets the job done.  Since it's off by default, the user has to
jump through several hoops to even see the "allow cookie" sheet.  I'd argue that
most such users will tolerate some visual complexity as a tradeoff for increased
functionality and control.

Comment 8

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Erm, assigning to Mike so this has an active owner ;)

Comment 9

[hahn]

I would highly appreciate a button "session only" or alternatively have Camino
honor network.cookie.lifetimePolicy=2, i.e. delete all cookies on exit.
Simplicity is good, but there is absolutely no point targeting software at
novices and ignoring expert users.

IMHO, Camino (or any other software) should NOT be designed to be simple, but
rather usable. That means that functionality that is needed frequently should be
easily accessible and functionality that is needed less frequently should be
hidden somewhere.

Comment 10

[Samuel Sidler (old account; do not CC)]

Per conversation with Mike, WONTFIX.

The relevant bug for session cookies is now bug 174070.