Closed GoogleCodeExporter closed 8 years ago
Original comment by fcap...@gmail.com
on 4 Jan 2011 at 1:52
Original comment by fcap...@gmail.com
on 5 Jan 2011 at 5:34
It's not fixed yet. If I visit chrome.google.com, I get all cookies from
different google subdomains. Still the same issue as before.
Original comment by tystre@gmail.com
on 7 Jan 2011 at 5:01
I don't understand the problem you're having.
Steps I made:
1. Go to http://chrome.google.com/extensions/
2. Show the details of a cookie having as domain ".google.com"
3. Click filter cookie
4. Uncheck name filter (only domain selected)
5. Submit filter
6. Et voila, all the cookies have been deleted, including the ones that were
subdomains of ".google.com"
Is it not working for you? Have you given enough time to chrome to update the
extension?
Original comment by fcap...@gmail.com
on 7 Jan 2011 at 11:56
If I go to http://chrome.google.com/extensions/, i see ".chrome.google.com" as
opposed to your ".google.com".
I also tried manually adding "google.com" and ".google.com" into blocklist.
Visiting http://chrome.google.com/extensions/, places google's cookies except
for chrome.google.com. I don't know what's exactly the problem here. But there
is something wrong. I am using the latest version of this extension, v0.13.2.
Original comment by tystre@gmail.com
on 10 Jan 2011 at 2:29
mmm...ok i'll try to find out what is the problem...thanks for the feedback!
Original comment by fcap...@gmail.com
on 10 Jan 2011 at 5:49
I see the same problem. Some cookies do not get deleted. For instance at ft.com.
Original comment by robotp...@gmail.com
on 24 Feb 2011 at 6:08
I still cannot reproduce the problem. If I go to ft.com, click on the cookie
"ftmd" and blacklist all cookies from ".ft.com" everything gets deleted. You
probably clicked on "trk_ref" whose domain is "www.ft.com", thus all cookies
whose domain is the more generic ".ft.com" are not deleted. This is normal,
because they have different domains. You can create two different rules in
order to delete all the cookies.
Original comment by fcap...@gmail.com
on 26 Feb 2011 at 3:54
Original issue reported on code.google.com by
tystre@gmail.com
on 4 Jan 2011 at 10:09