User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.8) Gecko/20061025 Firefox/1.5.0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.8) Gecko/20061025 Firefox/1.5.0.8 In FF2.0 it is no longer possible to block a cooky from the cooky list. This is very user unfriendly and I wonder why this has become worse with every version of FF: - In V1 I opened the cooky list, checked, "block this cooky", selected the unwanted cookie and pressed delete. Very nice when I wanted to just delete some cookies and block others. - In V1.5 I had to check the "block deleted cookies" checkbox outside the cooky list. This made it quite cumbersome because I had to switch back and forth between the outer and the inner dialog. - Now, with V2 the option to block a cooky from the cooky list is completely gone. At least, I can't find it. I have looked for an equivalent option but I can't find it. Reproducible: Always Steps to Reproduce: 1. Open Tools/options/Privacy/Cookies/Show cookies 2. 3. Actual Results: There is no option there to block an unqanted cooky from the list. Expected Results: An option to block an unwanted cooky from the cooky list I know that I can manually enter cookies in the exception list. I know that I can set FF to ask me every time about what to do with a cookie. But both of these are very *tedious* and annoying. I'll show you my use case: It is what I want to do and what worked perfectly well in V1, resonably well in V1.5 and no more in V2: - Happily surfing the web with all cookies being accepted. I'm fine with that. - One or two times a week I open Tools/Options/Privacy and open the cooky list - I then go through the list and remove unwanted cookies *and* I want some of them to be completely blocked from now on - I don't want to take a note of the unwanted cooky, close the cooky list, open the exceptions list and type in the cooky there and this is what FF 2.0 now forces me to do - I want to block unwanted cookies from the cookies list. That worked perfectly well in V1, reasonably wll in V1.5 and not at all in V2

*** This bug has been marked as a duplicate of 345989 ***