+++ This bug was initially created as a clone of Bug #480892 +++ Chris, in bug 480892: > 3) Remove all (*.)foo.com cookies when "remove and block all" is chosen from > the CM on a .foo.com cookie. (In reply to comment #1) > (3) is gonna be a little tricky because nsCookieService doesn't have any way to > remove all cookies matching a given host. nsCookieService can only delete > cookies one at a time or all at once. --- Note our menu item actually reads "Remove and Block Cookies from Sites Matching “foo.tld”", no "all" in there at all. However, if you want to block cookies from a site and remove the one you've clicked on, wouldn't you want to remove all the cookies from that site? Otherwise, why not do "Block" and then delete the single cookie? It always confuses me that "Remove and Block" only removes the selected cookie(s), even without "all" in the command name, so I think if we can figure out how to make this work, we should change the behavior (rather than adding an alternate for "all").
Created attachment 596418 [details] [diff] [review] WIP patch This does what it's supposed to, but for some reason, table data reload and row selection doesn't seem to work properly. Ideas welcome.
Assignee: nobody → cl-bugs-new2
Status: NEW → ASSIGNED
6 years ago
Duplicate of this bug: 459149
You need to log in before you can comment on or make changes to this bug.