Blocking third-party cookies causes some cookies to be displayed as both blocked and accepted
Reported by
khym.cha...@gmail.com,
Jun 15 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 Example URL: https://www.netflix.com/ Steps to reproduce the problem: 1. Disable third-party cookies at chrome://settings/content/cookies 2. Login to Netflix 3. Click the "blocked cookies" icon in the omnibar. What is the expected behavior? No netflix.com cookies should show up in the list of blocked cookies. What went wrong? The blocked cookies list claims that some netflix.com cookies are blocked, and looking at cookies in the list show some of the same cookies as area listed as accepted. Did this work before? N/A Chrome version: 67.0.3396.87 Channel: stable OS Version: Fedora 28 Flash Version: None of the following makes the problem go away: * Deleting all Netflix cookies and logging in again. * Starting the browser with experiments disabled. * Starting the browser with extensions disabled. * Logging in under a brand new profile.
,
Jun 15 2018
As per comment #0 As we don't have "https://www.netflix.com/" account credentials.Hence forwarding this issue to Inhouse and any one form team have a look on this for further traiging this issue. Thanks.!
,
Jun 15 2018
I was able to reproduce the problem. The same netflix.com cookies are shown simultaneously as accepted and blocked. There is no need in netflix account. The problem can be reproduced just by opening netflix.com. I will check whether the cookies are indeed blocked or not.
,
Jun 15 2018
Checked that the cookies are not actually blocked. All cookies, that appeared as accepted and blocked, were sent to the server. Looks like it is a UI issue.
,
Jun 15 2018
,
Jun 20 2018
It's possible for the same cookie to be blocked for some requests and not for others, depending on the context of the request - that may be what's happening here.
,
Oct 18
As explained in #6, this is not necessarily wrong. E.g. a request to netflix.com from a third-party iframe would not get cookie access. Netflix is creating some weird iframe structures so this is probably the cause. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by viswa.karala@chromium.org
, Jun 15 2018