New issue
Advanced search Search tips

Issue 829197 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Last session gets cleared when Chrome is launched directly in incognito mode

Reported by innatere...@gmail.com, Apr 5 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3386.1 Safari/537.36

Steps to reproduce the problem:
1. Set Chrome to "Restore my tabs on startup".
2. Open a few tabs in a normal window, then quit Chrome.
3. Start Chrome in an incognito window, either via the context menu of pinned Chrome icon on Windows taskbar or the command line switch --incognito.
4. Open a normal window.

What is the expected behavior?
The normal windows loaded with the tabs of previous session.
Incognito windows should not affect the session record of normal windows in any way.

What went wrong?
The normal window opens only a NTP, and the Recently closed tabs menu is empty.

Did this work before? No 

Chrome version: 67.0.3386.1  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

I searched and found some past issues about this, but they are either strangely WontFixed ( issue 276254 ) or claimed it had fixed the issue when it had not ( issue 31540 ), or at least not for this particular set of repro steps.
 
Comment #14 of  issue 31540  had reported a set of almost identical repro steps as well but got ignored.
Labels: Needs-Triage-M67
Labels: Triaged-ET M-67 Target-67 FoundIn-67 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version 67.0.3386.1 and on the latest chrome version 67.0.3388.0 using Windows-10, Mac 10.12.6 and Ubuntu 14.04. As the issue is seen from M60(60.0.3112.0) considering it as non-regression and marking it as Untriaged.

Thanks!
Labels: Hotlist-DesktopUIChecked Hotlist-DesktopUIValid
***Mass UI Triage***

We are able to reproduce this bug on latest canary #72.0.3622.0 and its a nonregression issue. Hence adding respective labels for further triage.Thanks!

Sign in to add a comment