Comment #8 on issue 16658 by saso.badovinac: Cross-Context Leakage of First-party cookies to Third-party cookies http://code.google.com/p/chromium/issues/detail?id=16658
Well, maybe this is really more a improvement then a bigfix, but from how I can see it an needed improvement because I see no sense in not blocking also to read cookies when the restricted third-party cookies option is set, since the above test shows very nicely how it can work around this setting and by this around the user privacy. And I cannot think of any explanation/reason why this should stay as it is, while on the other had we get the beneficial of improved user privacy... Or is there a possible issue that you might be breaking some internet infrastructure that might be relying on this trick, including maybe some of Google services, like ads,... ? Well what ever you decide to do with this now, I suspect that sooner or later there will be more demand for it. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
