New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 884912 link

Starred by 1 user
Status: WontFix
Owner:
█ nancyaggarwal@google.com
Last visit > 30 days ago
Closed: Sep 18
Cc:
█ mkwst@chromium.org
dtapu...@chromium.org
aog-amp-actions@google.com
█ ulas@google.com
EstimatedDays: ----
NextAction: ----
OS: Android , Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Same origin cookies treated as 3P cookies

Project Member Reported by nancyaggarwal@google.com, Sep 17 
Chrome Version: 69.0.3497.100
OS: Mobile Chrome on Android

What steps will reproduce the problem?
(1) Enroll into this optin: https://www.google.com/experimental?e=STA from your corp account and in Google Network.
(2) Disable "Allow third-party cookies" (Settings -> Site Settings -> Cookies -> Uncheck "Allow third-party cookies").
(3) Search for "showtimes near me"
(4) Click on any showtime.
(5) Select "Fandango" from provider selection list.
(6) Pick a seat and click Next.
(7) Select type of ticket and click Next.
(8) Under Payment Method, there is a box which says "Uh oh. There was a problem". 

What is the expected result?
It should have shown a GPay widget. If you tick the "Allow third-party cookies", then it will work fine.

What happens instead?
Does not show GPay widget.

The top level origin is actions.google.com, and GPay is also on the same domain, but its cookies are treated as 3P cookies.

Comment 1 by dtapu...@chromium.org, Sep 18 

I tried to reproduce this I don't see the GPay Widget; I just get a choice to provide my credit card to the fandago website. Couple of questions.

1) I'm enrolling my browser (not my corp account in the trial.. is that ok).
2) Do I need to be signed in to fandago, I'm just continuing as a guest.
3) I might be having problems due to my location in Canada, I'm searching for movies near Buffalo.

Comment 2 by nancyaggarwal@google.com, Sep 18

Status: WontFix (was: Untriaged)
1) We need account enrollment.
2) Does not matter.
3) Its enabled only for en-US.

I guess from discussions on email, it looks like this is WAI. We will go ahead and find a workaround to support our use case. Closing it now.
►

Sign in to add a comment