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

Issue metadata

Status: WontFix
Closed: Feb 2
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression

Sign in to add a comment

[Chrome Home] Last "non-Chrome-NTP" webpage appears when opening Chrome

Reported by, Nov 9 Back to list

Issue description

Steps to reproduce the problem:
Preparation: Make sure Chrome has 0 tabs before opening.

1. Open Chrome.
2. Go to
3. Tap [Return] button.
4. Tap [Return] button (exiting Chrome).
5. Open Chrome.

What is the expected behavior?
After step 1, I should see Chrome NTP/Chrome Home.
After step 3, I should see Chrome NTP/Chrome Home.
After step 5, I should see Chrome NTP/Chrome Home.

(Result of Chrome Stable 62.0.3202.84)

What went wrong?
After step 3, I see with Chrome Home panel covering half the screen.
After step 5, I see

Did this work before? Yes 

Chrome version: 64.0.3261.0  Channel: dev
OS Version: 
Flash Version: 

Before Chrome Home, user can always tap [Return] button to return to previous page until it is Chrome NTP, and one more tap on [Return], user exits from Chrome. When user opens Chrome again, Chrome NTP appears, not last "non-Chrome-NTP" webpage.

In Chrome Home, last "non-Chrome-NTP" webpage always comes up when opening Chrome. This is very annoying.
Labels: Needs-triage-Mobile
Labels: Triaged-Mobile Needs-Feedback
Tested the issue in Android and could not reproduce the issue. 

teps Followed:
1. Launched Chrome Browser.
2. Navigated to
3. Observed Chrome NTP/Chrome Home after step 3 and step 5 

Chrome versions tested:

Android 7.0.0

Android Devices
7.0.0 SM-J710F Build/NRD90M

@loorongjie: Could you please help us with the OS & details of your device and attach a screencast as well.


@sandeepkumars, you misread my report, Chrome 62.0.3202.84 is working as expected, Chrome Dev 64.0.3261.0 is not working as expected.
Project Member

Comment 4 by, Nov 10

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

For more details visit - Your friendly Sheriffbot
Screencast for Chrome Dev 64
13.0 MB View Download
Labels: -Pri-2 ReleaseBlock-Stable M-64 Pri-1
Status: Untriaged
Able to reproduce the issue as per the steps mentioned in comment #2.

Chrome versions tested:

Android 7.0.0

Android Devices
7.0.0 SM-J710F Build/NRD90M

Below is the bisect info
Chrome Good Build -- 63.0.3237.11
Chrome Bad Build  -- 63.0.3238.0

Unable to provide the per-revision bisect as all good builds are getting invoked.

Requesting someone from dev team, please take a look at this issue and help us in assigning the issue to appropriate owner.

Adding Release Block Stable as this is a recent regression broken in M63.

Please navigate to below link for log's and video--

Note: This issue is not observed in Desktop.

Status: Assigned
May be this patch is the suspect, seeing some change in -

Assigning to Bernhard for confirming.
+Kingston, Matt

So, there isn't actually a New Tab Page per se anymore in Chrome Home. What you get when opening a new tab e.g. from the overflow menu is the bottom sheet shown over the tab switcher (I think fully expanded). When you navigate back we also show the bottom sheet, but in the half-opened state, which might be what you observed, so I think this is working as intended, but I'll pass to Kingston for triaging the feedback.
I have been experimenting with Chrome Home and following several public tracking bugs, so I know this is indeed "working as intended" based on the design. My report is to show that this design decision breaks a common workflow.

If a user go to website A > website B > website C > [Return] to website B > [Return] to website A (*) > [Return] and see overflow menu > [Return] to close Chrome > [Open Chrome] and see website A > website D > [Return] to A (*) > [Return] and see overflow menu > [Return] to close Chrome > [Open Chrome] and see A.

Website A persists when user opens Chrome. Workaround is after (*), explicitly close website A tab in tab manager instead of tapping [Return]. However, that is more taps than it used to be before Chrome Home and I always forgot to do this instead of keep tapping [Return] (old habits die hard).
Thanks for the feedback, that is very helpful!
Got it thanks -that's good to know. We're working on better back button behavior so we can take this into account as we proceed with it.
Labels: -ReleaseBlock-Stable -M-64
We are looking into potential solutions here though removing RBS since it's not a blocking bug.
Status: WontFix
We are ending the current Chrome Home experiment and closing the corresponding Chrome Home bugs. Thanks for the feedback and support!

Sign in to add a comment