Closed Bug 210659 Opened 22 years ago Closed 22 years ago

No way to reject cookies except from some sites

Categories

(Firefox :: Settings UI, enhancement)

x86
Windows 98
enhancement
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 178048

People

(Reporter: mrdicemail, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6 In Explorer I'm used to the following (and several other people I know): I reject all cookies, except from a few sites I visit regularly. Google.com needs cookies to remember it's preferences, and Yahoo Mail needs them to let me login. The problem with Firebird is, that it's not possible to reject cookies except from some sites. When I edit the cookperm.txt file, it still refects ALL cookies when I disallow them in preferences. When I set preferences to "this session", it deletes ALL cookies including the sites allowed in cookperm.txt. Summery: there has to be a way to either reject or set to session ALL sites EXCEPT some specific sites. It would be elegant to have a "allow cookies" checkbox in the bookmarks properties. Reproducible: Always Steps to Reproduce: 1. 2. 3.
duplicate of bug 75915
*** This bug has been marked as a duplicate of 178048 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Jesse: Why dupe this against a bug already marked as a duplicate of the bug I mentioned? Shouldn't the bug be duped against the original bug?
Because bug 178048 was reported against Firebird. This way, if bug 178048 is reopened (unlikely but possible), everything will be as it should be.
taking QA contact, sorry about the bugspam
QA Contact: asa → mconnor
mass verification of dupes
Status: RESOLVED → VERIFIED
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.