User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:188.8.131.52) Gecko/20060508 Firefox/184.108.40.206 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:220.127.116.11) Gecko/20060508 Firefox/18.104.22.168 Hi! In previous versions (<1.5) there was a button on the Cookie viewer window to block the site of the selected cookie. I suggest to recover this button and in the same action delete the cookie or cookies selected. Reproducible: Always Steps to Reproduce: This it's a wish. I normally check and delete the cookies I don't want to have in my firefox. Now it's very difficult to delete a cookie AND Block the site for future cookies.
*** Bug 360153 has been marked as a duplicate of this bug. ***
In 1.5 there was a checkbox saying "Don't allow sites that set removed cookies to set future cookies". Admittedly cumbersome. In 2.0 the possibility to block 3rd party cookies has been dropped, which feels like a major privacy loss. Until we have good blacklists setup, at a very minimum we'd like to be able to build our own easily. Please, automatically add removed sites to the "Exception - Cookies" list!! (A checkbox to inhibit such behavior is optional)
well, the checkbox isn't coming back, but perhaps a less intrusive solution is simply to have a context menu - right click on a cookie in the cookie manager, and select 'block cookies from this site'.
Related or duplicate: #408735 I suppoort doing something about this. I'm fine with restoring the checkbox, but a button or right click option next to each site in the "Cookies" dialog, to remove all cookies from that site and block all future ones, would be great.
I submitted Bug 408735, which I closed as a duplicate of this. The Firefox 1.5 block sites while removing cookies functionality needs to be restored. I don't care if the check box is brought back or a context menu added. I've had to resort to COPYING THE SITE OF THE COOKIE I'M REMOVING TO A PIECE OF PAPER, AND THEN BLOCKING THAT SITE USING A DIFFERENT MODAL WINDOW to accomplish the same effect, and this is extremely awkward, annoying, and inefficient. It was certainly a step backward to remove the check box from Firefox 2.0 without introducing a better method.
The following addons are good for this problem Web Developer https://addons.mozilla.org/en-US/firefox/addon/60 CookieSafe https://addons.mozilla.org/en-US/firefox/addon/2497 I don't mean those addons completely solve the problem, although I don't want to mean the opposite either. However, adding one or both of those certainly helps.
I think an additional UI element is needed in the Tools|Options|Privacy|Show Cookies dialog. A button named Delete Cookie and Block (see attached jpg image) would offer the user pretty atomic control over 3rd party cookies without the necessity of a blanket setting. I think the underlying behavior is obvious.
Would the "Remove and Block" cookie be context sensitive as to whether the user had highlighted a host (thus blocking all cookies from the host, or perhaps domain?), or a particular cookie emanating originating in that host or domain? If so, that'd be a super way to address this bug.
jayhenn, I'd prefer it be simple. Block the whole domain/host, not individual cookies within that domain/host.
I can only support this: Make it simple and block the whole domain/host. That's what is expected.
Abe Klag: The button in your proposed UI is *exactly* where I want to see it, too. Jayhenn, Frank: Each item on the Exceptions list is a site/host/domain. When the "Block" button is selected, whether the Site heading is highlighted or an individual cookie, the only thing that can get added to the Exceptions list is the site/host/domain name. That said, it leaves open the question of just what gets removed. I'm thinking it might be easier to have the new button just be "Block" and leave the "Remove" to a second click of the existing "Remove" button, but I'm not satisfied with that, either; it seems inelegant. Perhaps the button should become active only when the Site heading is highlighted... Ideas?
What about a "Block domain" checkbox on the cookie dialog? When checked, every "Remove" also adds a block entry for the appropriate domain unless the host has already been blocked. Just a thought...
Yes, this will be a very useful feature. It takes too many steps to see a cookie in the list and to block it from a different window.
I deleted my paypal and ebay cookies because I was getting an error at the paypal site. Doing so fixed the problem with Paypal, but now I can't login to ebay at all. I get a "Your web browser settings are blocking cookies." message when I try. Now, I have no idea how to allow Firefox to allow the ebay site to set cookies because the "Don't allow sites that set removed cookies to set future cookies" option is gone from the UI... There doesn't even seem to be a setting in about:config to fix it. I can't fathom what the devs were thinking... J Nonamano writes above: I submitted Bug 408735, which I closed as a duplicate of this. How is it a duplicate?
And isn't <Restore the "Don't allow sites that set removed cookies to set future cookies" option> a bug fix, not an enhancement? AHA! It's a bug, IMO. My ESP kicked in and I figured out that the solution to my problem was to use my ESP to figure out (!!!) that I needed to change <Firefox will "remember history"> to <Firefox will "use custom settings for history"> !! That un-hid the "Exceptions" button, which popped up the window allowing me to re-allow cookies from various paypal and ebay sites. (OMFG!) Any thoughts? If not, I intend to re-categorize this as a bug. (Sorry for the double post)
Has anyone looked at this, since 2009 ? I miss the capacity to delete a cookie and have it automatically appear on the block list found on the block dialog.
(In reply to john ruskin from comment #21) > Has anyone looked at this, since 2009 ? > > I miss the capacity to delete a cookie and have it automatically appear on > the block list found on the block dialog. I've come the other route - FF30 with a "real old profile" exhibited the behavior asked for in this bug, annoying the user. In the end, it was because FF 30 still recognized the "network.cookie.blockFutureCookies" preference (type boolean) - in our case, it was set to "true". So to me it seems that only the UI element is missing, the functionality is still in the code :)