[Google Plus] Chrome launches but link does not open in any Tab
Reported by
smoha...@etouch.net,
Mar 10 2016
|
|||||
Issue descriptionApplication Version: Chrome Dev 51.0.2673.0 Android Build Number: 6.0.1/MMB29R Device: Nexus 9 Precondition: 1. Google plus homescreen shortcut should be present [Launches as app] Steps to reproduce: 1. Launch chrome> Force stop it 2. Launch 'Google plus' homescreen shortcut> Open any link [Chrome will launch and link will get open in one tab] 3. Close the opened tab and switch back to 'Google Plus' homescreen shortcut from Recents 4. Open the same link from 'Google Plus' homescreen shortcut and Observe Observed behavior: Chrome launches but link does not open in any Tab Expected behavior: Chrome should launch and link should open in one Tab Frequency: <5/5> Note: Once the observed behavior is seen, link does not open at all even if tried multiple times. Additional comments: 1. This issue is a non-regression issue. Issue is present in M48,M49,M50,M51 2. This issue is reproducible on Samsung Galaxy S4(5.0.1/LRX22C), Moto g2(5.0.2/LXB22), Spice Mi-498(6.0.0/MRA58M), Karbonn Sparkle V(5.1.1/LMY47V), Nexus 7(5.1.1/LMY48T), Nexus 9(6.0.1/MMB29S), Micromax Canvas A1(6.0.1/MMB29Q)
,
Mar 11 2016
,
Mar 11 2016
I can't repro this locally. Are there any specific flags you have set on your devices?
,
Mar 11 2016
I'm now seeing this when I use the ChromeModernDev.apk instead of the ChromeDev.apk. Don't know how to triage this, but I don't think this is WebappActivity specific.
,
Mar 11 2016
Well, I'm not having an issue with the renderer failing in ChromeDev.apk, but it still fails to open new tabs.
,
Mar 24 2016
Haven't had time to investigate, but it'd be good to fix.
,
Apr 23 2016
On my Nexus 7, I'm not seeing a ChromeTabbedActivity#processUrlViewIntent() call being made when no new tab is created, which makes me suspect that we're dropping the Intent on the floor. I believe this is because the first click on the link makes Clank start up is cached and fails to finish going through the onNewIntent pathway because the Intent is exactly the same when the link is clicked again from the webapp. This is a separate problem from the Tab being created and failing to load anything at all.
,
Apr 25 2016
Er, we're not even getting an onNewIntent() here. I'm guessing it's an Android thing that prevents us from getting the Intent back, which makes it impossible to create a new tab in this scenario.
,
May 16 2016
If this is actually a 51 stable blocker it needs to be fixed and merged back by this time next week. What's the deal here, no love for 3 weeks?
,
May 16 2016
We're kind of stuck here because it looks like Android isn't delivering the Intent as intended; it's similar to the other RBS bug on my plate that's ExternalDependency. I'd punt this past RBS but keep the priority high.
,
May 16 2016
,
May 23 2016
Duping this against the other bug, since we can't do anything about either case and it has more context. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dknandiraju@chromium.org
, Mar 10 2016