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

Issue 853464 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Usually the app closed after the last tab was closed, not anymore.

Reported by colin.fr...@gmail.com, Jun 16 2018

Issue description

Steps to reproduce the problem:
1. Open a tab
2. Close it 
3. Note the annoying black screen 

What is the expected behavior?
The app should close when that last tab is closed... And when leaving the app by pressing "back", it should re-open with a new fresh tab (now it re-opens with the black chrome background with the + button to open a new tab) 

What went wrong?
I don't know. 

Did this work before? N/A 

Chrome version: 67.0.3396.87  Channel: stable
OS Version: 8.0.0
Flash Version:
 
Screenshot_20180616-093251_Chrome.jpg
100 KB View Download
Labels: Needs-triage-Mobile
Cc: pnangunoori@chromium.org
Components: UI>Browser>NewTabPage
Labels: Triaged-Mobile Needs-Feedback
colin.frelechox@ -- Thanks for reporting this issue. This is the intended behavior of Chrome application upon closing all the tabs, the screen mentioned in Comment #1 will be observed. In the mentioned screen, user can open a new tab and access Chrome settings.

Thanks!
No no no no !

It never done that before, I had Motorola Defy, Samsung S2/Note2/Note4/S7/Note8 and it do that now !

It's annoying ! I uninstalled all the updates and it's back to normal (app close with the last tab closed) ! It's not a normal behavior.

Please. Put it back to normal, its a bug. 
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 18 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 Deleted

Status: WontFix (was: Unconfirmed)
Please refer the  Issue 783562  for your reference.

Closing this issue as it is the intended behavior.

Thanks!

Sign in to add a comment