Issue metadata
Sign in to add a comment
|
WebAPK display-mode should go back to the previous standalone view from minimal-ui after coming back from different domain
Reported by
abhishek...@gmail.com,
Dec 3
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. On Chrome for Android, go to a website like flipkart.com and install the WebAPK that has display standalone view 1. Try to go to an experience that open different domain (to trigger minimal-ui view), such as the checkout flow (here, select netbanking payment option that would take you to a different domain, example State Bank of India) 2. Try to login in with some credentials (you can attempt with any incorrect random credential and do a login for a form post to happen) 3. Press back to cancel the flow and try to land back on origin WebAPK domain (eg. flipkart.com). You can select back when you get the confirm form submission page. 4. Notice that the view should have gone back to standalone (no browser chrome - as was before starting this example payment flow) but it's stuck in minimal-ui A video showing this problem and the steps to reproduce it is captured here: https://youtu.be/kxuGJsJGcEc What is the expected behavior? The view should go back to standalone display mode. What went wrong? * While it should have been display:standalone, the UI chrome got stuck in minimal-ui chrome which was also non-responsive (the "x" button is unclickable) * Using the display-mode media query (https://developers.google.com/web/fundamentals/app-install-banners/#detect-mode), the browser reports it as 'standalone' but visually it's still minimal-ui (this is bad because this way some logic on the website like a "progress bar" can break, now showing two progress bars) Did this work before? N/A Chrome version: 70.0.3538.110 Channel: stable OS Version: Android 8.1.0 Flash Version:
,
Dec 3
Note: All personal information (username, password, contact info) in the video are fake
,
Dec 4
,
Dec 5
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Navigated to flipkart.com, added to homescreen 2. Opened it from homescreen, logged in , added item to cart, proceeded with netbanking 3. Clicked back and observed flipkart webapk in cct mode, on clicking on "x" icon nothing happens Chrome versions tested: 70.0.3538.110 OS: Android 9.0.0 Android Devices: Pixel 2 Using the per-revision bisect providing the bisect results, Good Build - 70.0.3524.0 Bad Build - 70.0.3525.0 Manual CL: https://chromium.googlesource.com/chromium/src/+log/70.0.3524.0..70.0.3525.0?pretty=fuller&n=10000 On performing per-revision bisect we got the result as "You are looking for a change made after 583638(GOOD), but before 583756(BAD)." We have almost 100 changes in between good and bad and bad 583756 doesn't point to appropriate change. Hence adding appropriate label and requesting yfriedman@ or pkotwicz@ for further help in triaging. Adding RB-Stable for M-70. Please remove if this is not the case. Thanks!
,
Dec 5
Not blocking the 71 stable roll out for this.
,
Dec 5
Thanks for the report. As Ben said, I don't think this should be RBS (no functional regression, not clear this is common, 71 is already rolling out), but I'll mark it for the next release.
,
Dec 5
,
Dec 5
,
Dec 5
chelamcherla@: can you check tomorrow if this reproduces in the canary build from tonight? I'm curious whether the cl which landed for that issue resolves this
,
Dec 5
Bug 861618 still has an issue for which I have a fix. I'll try tomorrow to see if I can repro this issue if and if the same fix helps here.
,
Dec 27
I've confirmed the issue and that it's fixed in Canary. Please let me know if you're still seeing it. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by abhishek...@gmail.com
, Dec 3