Google Fi signup workflow broken with Strict Site Isolation enabled
Reported by
basc...@gmail.com,
Jan 18 2018
|
||||||
Issue descriptionChrome Version : 63.0.3239.132 OS Version: OS X 10.13.2 URLs (if applicable) : https://fi.google.com/signup Other browsers tested: N/A What steps will reproduce the problem? Go through the Google Fi signup workflow, selecting a plan, device, etc until you are almost to the screen where you accept the ToS and enter payment info What is the expected result? ToS appears, and then the next page appears prompting for payment information. This works correctly after disabling Strict Site Isolation and restarting Chrome. What happens instead of that? ToS not displayed, advances to a partially rendered next screen, lots of ERR_BLOCKED_BY_CLIENT in the console. Please provide any additional information below. Attach a screenshot if possible. No screenshot, sorry ;( UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
,
Jan 18 2018
I couldn't repro this with --site-per-process on Mac 63.0.3239.132 or Linux 63.0.3239.132. Maybe someone else on the site isolation team can try to repro and help narrow this down? bascule@: It'd be very helpful if you can provide a screenshot of the failure with DevTools open.
,
Jan 18 2018
I also can't repro this with --site-per-process on Windows 63.0.3239.132. Let us know if this is repeatable for you or if anyone else is able to repro it.
,
Jan 18 2018
I can attempt a repro. It may also be due to UBlock Origin, which I had the site whitelisted under at the time, and with which that succeeded after disabling Strict Site Isolation, but it'd probably be the #1 thing on my list which is a potential culprit. When I get a chance I'll try to do a repro in an incognito window.
,
Jan 18 2018
I'd also recommend trying this with --site-per-process in a clean profile, as well as when running with --disable-extensions to see if an extension might somehow be interfering with the flow.
,
Jan 18 2018
Thanks. UBlock Origin might indeed be involved. It's possible that extension's behavior might have changed with --site-per-process, which would be useful to know as well.
,
Jan 18 2018
Yes, if you can confirm that this problem goes away when you run with --site-per-process, but disable UBlock Origin in chrome://extensions, that would be very useful to know.
,
Jan 22 2018
@Reporter: Please try to test the issue as per inputs given in Comment#5, 6 & 7 and let us know the behaviour. Thanks!
,
Jan 22 2018
,
Jan 22 2018
Not sure I have time to try to reproduce this again (seems I'd have to create a new Google Account, as I already completed the signup flow with my current one) If you'd like to close this out with the suspicion that uBlock Origin is the cause that seems ok to me.
,
Jan 22 2018
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 23 2018
As per comment#7 and comment#10 requesting alex...@chromium.org for further action on this issue. Thanks!
,
Mar 12 2018
[Mac triage] Given the lack of activity, I'm closing this out. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Jan 18 2018