WebAPK banners do not dismiss after navigation |
|||
Issue descriptionChrome Dev 57.0.2984.3 on Android What steps will reproduce the problem? (1) Go to a PWA and press Add to Home screen (2) Press open from Play install screen (i.e. don't dismiss the WebAPK banner) (3) Open some other app that intents into Chrome and let it intent in What is the expected result? Chrome navigates to that page but the WebAPK banner isn't still visible What happens instead? Chrome navigates to the new page but the WebAPK banner from the previous PWA remains visible Assigning to Dom for triage to appropriate person to fix for 57.
,
Jan 25 2017
Weird, I attached one before but it didn't seem to upload. By "open from Play install screen" I mean the full screen page that says "This app requires no special permissions. [Done] [Open]" (or similar). This issue doesn't depend on that though so forget that I mentioned it. More precise repro steps: (1) Go to a PWA and press Add to Home screen (2) Press Install on Play confirmation dialog (won't be present in Stable version) (3) Press Done on Play confirmation dialog. You should now be back in the PWA, with the banner visible saying [Open]. Step (1) will got straight to this step in Stable. (4) Open any other app that intents into Chrome and let it intent in Chrome should now have opened the new page the intent requested, but the WebAPK banner from the previous PWA remains visible (see screenshot)
,
Jan 28 2017
,
Jan 30 2017
(Added to WebAPK component. I also suspect this is the same issue as #682718 if offline pages are opened via an intent.)
,
Feb 8 2017
I can't reproduce this on Chrome Canary 57.0.2986.0. I install a PWA as a WebAPK, and return to the page where the banner shows "Open". I then minimise Chrome, use GSA to search for something, and click a link (having set GSA to open in the external browser, and set my default browser to Chrome Canary). A new tab opens in Canary to the link I clicked, with no banner. Switching tabs back to the PWA reveals the banner again (as it should: banners are tab specific). Have I missed a step / should use some other repro steps? How did you intent back into Chrome?
,
Feb 15 2017
I also can't reproduce today. I note that I was reproducing consistently when we still had the full screen install modal rendered by the Play Store so perhaps it's only when using the untrusted sources bit and APKs not signed by Play that triggers the buggy codepath. Either way, marking as WontFix unless someone runs into this again and can repro. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dominickn@chromium.org
, Jan 25 2017