Closed
Bug 80712
Opened 23 years ago
Closed 21 years ago
Reject all cookies from this second level domain
Categories
(Core :: Networking: Cookies, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 176950
Future
People
(Reporter: guanxi_i, Assigned: morse)
Details
The cookie manager could use this additional functionality: The option to 'remember this decision for all cookies from this second level domain'. It would need to be reworded of course. Wildcards would be useful and flexible: the user could accept/reject cookies from *.yahoo.com, *.foo.yahoo.com, etc. The problem: Some cookie sources, hitbox.com being a particularly problematic example, place cookies from many different hosts (e.g. host1.hitbox.com, host2.hitbox.com, etc.). In those cases, 'remember this decision' doesn't do much good, because the host is different everytime anyway. Also, non-tech users may get confused by the current setup: 'didn't I tell it to remember this decision (to reject a cookie from hitbox.com)? This feature isn't working.' Those who don't understand how hosts are named, which probably describes most web users, may not notice or understand the differences between host1495.hibox.com and host1352.hitbox.com.
Similar enough, perhaps. My apologies. Mine's more along the lines of Matthew Mastracci's comment on <a href="show_bug.cgi?id=52168" title="NEW - Right clicking in cookie manager should block site">bug 52168</a>. When I scanned through the list of bugs, 52168 looked like it referred to changing the interface for a feature in Preferences | Advanced | Cookies | Viewed Stored Cookies. I mean that the 'confirm this cookie' dialog box would benefit greatly from the suggested feature. Perhaps these two can be consolidated under a clear Summary.
Bugzilla is more efficient than I thought. Sorry for the newbie mess.
Comment 4•23 years ago
|
||
Over to User interface design.
Assignee: morse → mpt
Status: UNCONFIRMED → NEW
Component: Cookies → User Interface Design
Ever confirmed: true
QA Contact: tever → zach
BTW - this isn't a UI issue. The functionality doesn't exist, unless it's hidden for some reason. How do I tell Moz to reject all cookies from any (e.g.) yahoo.com host (i.e. *.yahoo.com)?
Component -> Cookies. As I said, not a UI issue.
Component: User Interface Design → Cookies
it's a UIDesign issue until UID tells us that it's worth spending time on. if they say it's totally foolish then we're not going to bother an overburdenned developer to implement something which UID would refuse to allow into the UI once it was developed.
Component: Cookies → User Interface Design
Comment 8•22 years ago
|
||
> it's a UIDesign issue until UID tells us that it's worth spending time on
Not anymore it isn't :-)
Assignee: mpt → morse
Component: User Interface Design → Cookies
QA Contact: zach → tever
Assignee | ||
Updated•22 years ago
|
Target Milestone: --- → Future
Back end for this is part of bug 78104. Maybe a dependancy should be added ?
Comment 10•21 years ago
|
||
bug 78104 is for blocking based on regexps or paths in URLs. the original report here only talks about hosts and domains, which I think is bug 176950, and that's just been fixed. *** This bug has been marked as a duplicate of 176950 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•