chrome_frame/chrome_frame_automation.cc - Issue 21150006: Introduce --cancel-first-run and reduce the strength of --no-first-run.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: chrome_frame/chrome_frame_automation.cc

Issue 21150006: Introduce --cancel-first-run and reduce the strength of --no-first-run. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Replace hardcoded --no-first-run in scripts Created 7 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« chrome/browser/first_run/first_run.cc ('K') | « chrome/test/webdriver/webdriver_capabilities_parser_unittest.cc ('k') | chrome_frame/chrome_launcher_unittest.cc » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: chrome_frame/chrome_frame_automation.cc

diff --git a/chrome_frame/chrome_frame_automation.cc b/chrome_frame/chrome_frame_automation.cc

index bcf4f06f2c9c9a96451278d3baaa6fb033dcda73..04cc9b2e5ec1cc9817302f0e0f9aa41fa5b02919 100644

--- a/chrome_frame/chrome_frame_automation.cc

+++ b/chrome_frame/chrome_frame_automation.cc

@@ -267,7 +267,7 @@ void AutomationProxyCacheEntry::CreateProxy(ChromeFrameLaunchParams* params,

command_line->AppendSwitch(switches::kChromeFrame);

// Chrome Frame never wants Chrome to start up with a First Run UI.

- command_line->AppendSwitch(switches::kNoFirstRun);

+ command_line->AppendSwitch(switches::kSkipFirstRun);

grt (UTC plus 2) 2013/07/30 02:48:16 GCF uses a different user data dir than Chrome, so

gab 2013/07/30 14:10:17 Actually, for user-level the First Run beacon is d

grt (UTC plus 2) 2013/07/30 14:21:11 Ah. Right you are, sir. The beacon is put in the A

// Chrome Frame never wants to run background extensions since they

// interfere with in-use updates.