Custom Tabs Don't Load from GSA |
|||
Issue descriptionChrome Version: 64.0.3282.137 (Chrome Beta) OS: Android What steps will reproduce the problem? (1) Go to the -1 page on Android (GSA?) (2) Click on an article in the feed that should load up in a Chrome Beta CCT (3) The page will not load. What is the expected result? The page doesn't load. What happens instead? Go to the menu and choose "Open in Chrome Beta" and the page loads in Chrome just fine.
,
Feb 2 2018
Yeah the CCT loads and the progress bar stays stuck at about 10-15%. Not able to reproduce right now :(. I see it pretty reliably so I'll grab a screenshot this weekend if I see it again. Sorry about that!
,
Feb 6 2018
@yusufo -- wasn't there some issue where the prerendered page didn't load correctly? But maybe in that case, the page would be blank or the viewer frame would be there but no content. I guess if the progress bar is stuck at 10-15%, then it might simply be that the cache isn't loading? Seems like we might need net logs or "something" to be able to investigate this more.
,
Feb 6 2018
yes, this seems to be the b/70625701 crbug.com/801408 We have yet to identify a good way to reproduce this one, so any devices that can reliably get this behavior (doesn't have be even 50% :) ) would actually help a lot.
,
Feb 6 2018
one thing that is different here is the mention of the progress bar. Normally when we show the prerendered page at amp_url, we navigate it to amp_url#fragment_no and that should normally not cause any network requests. I wonder if the viewer is missing that request somehow. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bauerb@chromium.org
, Feb 2 2018