New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 625972 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Closing a custom tab goes to chrome not the app

Reported by luanbarb...@gmail.com, Jul 6 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome Browser
2. Open a application that has a webview with links
3. Click on click that the app will open using Chrome Custom Tabs
4. Hit back button or the close button on the Custom Tab

What is the expected behavior?
The Custom Tab should be closed, going back to the App that called it.

What went wrong?
The Custom Tab closes the tab, but the browser appears instead of the Application that called the Custom Tab.

Did this work before? N/A 

Chrome version: 51.0.2704.106  Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 22.0 r0

Another behaviour that I saw is when the Chrome Browser is not opened and I hit the back button the Custom Tab "closes" and the App that called it appears. However, the custom tab will remain open in the background (can be seen in the recents stack)
 
device-2016-07-06-152218.png
407 KB View Download
device-2016-07-06-152230.png
123 KB View Download
Labels: -OS-Mac OS-Android
The problem was because my Activity had launchMode set to singleInstance, for any other value (standard or singleTask) the problem will not appear.

Not sure if this is a bug or work as intended (anyway, this detail could be a good addition to the Chrome Custom Tabs guide)
Components: UI>Browser>Mobile>CustomTabs

Comment 4 by lizeb@chromium.org, Jul 28 2016

Cc: ian...@chromium.org yus...@chromium.org lizeb@chromium.org
Status: Available (was: Unconfirmed)
Project Member

Comment 6 by sheriffbot@chromium.org, Sep 18 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
Sounds like you might have been using NEW_TASK with the CCT intent and that wasn't fully supported at launch (when you mention it being visible in recents instead of the app).  I believe this has been addressed though.

Sign in to add a comment