New issue
Advanced search Search tips

Issue 446841 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2015
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature



Sign in to add a comment

Disable session restore functionality using command line flag

Reported by tejain...@gmail.com, Jan 7 2015

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36

Steps to reproduce the problem:
1. Open chrome 
2. Crash it. (Ex: pkill -9 chrome)
3. Reopen chrome
4. The yellow session restore infobar is shown

What is the expected behavior?
I am running chrome browser as kiosk. I dont want my user to see the yellow session restore infobar (neither the white session restore bubble). It would be great if there is a commandline flag that would ignore the session crash and just show the home page as if nothing happened.

What went wrong?
Chromium doesn't have a command line or configuration flag to disable session restore functionality.

Did this work before? No 

Chrome version: 39.0.2171.95  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 16.0 r0

 

Comment 1 by marja@chromium.org, Jan 7 2015

Btw, would --incognito be good for your use case? It always runs in incognito, and pages visited in incognito are never restored by session restore. As a bonus, your users' cookies and other data will be deleted when Chrome is closed.

Comment 2 by marja@chromium.org, Jan 7 2015

Cc: sky@chromium.org marja@chromium.org
That is what I am using right now: ingonito + kiosk mode. But the problem is i would like to keep the cookies and other data between shutdowns and crashes.
Status: Untriaged
Seems to be a feature request.

Please change the status, if somebody don't agree.
Labels: M-41
Labels: -Type-Bug Type-Feature

Comment 7 by pennymac@google.com, Jan 15 2015

Labels: -M-41 M-42 MovedFrom-41
Moving all non essential bugs to the next Milestone.

Comment 8 by sky@chromium.org, Jan 15 2015

Status: WontFix
We actively try to keep the set of flags chrome exposes to a minimum; only those that are used widely enough.

Sign in to add a comment