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 4 users

Issue metadata

Status: Fixed
Closed: Mar 2012
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Sign in to add a comment

Create a registry value that Chrome Frame will read and append to its command line.

Project Member Reported by, Mar 5 2012 Back to list

Issue description

This will allow for testing of experimental Chrome flags while running under Chrome Frame.

The value could be under either HKCU or HKLM, the security implications are roughly the same.

Comment 1 by, Mar 5 2012

Status: Assigned
Summary: Create a registry value that Chrome Frame will read and append to its command line. (was: NULL)
Either CF or CF's launcher process should read the registry values.
We should also put this in our group policy template.

Comment 2 by, Mar 5 2012

Any progress? I keep seeing google-chrome-frame threads where we're advising users to make builds. The sooner we get out of that business the better.

Comment 4 by, Mar 22 2012

Status: Started

Comment 5 by, Mar 23 2012

Here's how to test the new feature (this assumes Chrome Frame is installed and working):


Using the administrative templates provided for Chrome/Chromium:
  Open up chrome.adm in the Group Policy editor.
  Navigate to: 
    Computer Configuration
      Administrative Templates
        Classic Administrative Templates
          Default HTML renderer for [Chromium|Chrome] Frame
  Enable the 'Additional command line parameters for [Chromium|Chrome] Frame' policy and set your additional parameters.  For example "--enable-media-stream".

You can also do this by using regedit:

Open regedit and navigate to (this assumes you're running on a 64bit system, otherwise remove Wow6432Node):
Create a REG_SZ value and name it "AdditionalLaunchParameters".
Set its value to the extra parameters you want to use as above.


To verify that this is working, open up a page in IE that uses Chrome Frame.  E.g.
The page should be rendered in Chrome Frame.
Right click on the page and select "About [Chromium|Chrome] Frame".
In the about page, you will see the command line that was used to launch chrome.
Verify that your extra parameters are there.
Project Member

Comment 6 by, Mar 28 2012

The following revision refers to this bug:

r129384 | | Tue Mar 27 23:58:33 PDT 2012

Changed paths:

Adding policy support to Chrome Frame's launcher so that additional parameters can be passed to Chrome via Group Policy.

BUG= 116783 
TEST=See information in comment #5 of the issue.

Review URL:

Comment 7 by, Mar 28 2012

Status: Fixed

Comment 8 by, Sep 23 2012

I can't this to work on my machine.

I tried doing method 2 by adding the RG_SZ value named "AdditionalLaunchParameters" and assigned it the value "--enable-media-stream".  I am not running a 64 bit machine so I added the key to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Chromium.

Here is the command line from Chrome Frame:
"C:\Documents and Settings\Win XP\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --automation-channel=ChromeTestingInterface:4948.1 --chrome-frame --no-first-run --disable-background-mode --disable-popup-blocking --disable-print-preview --chrome-frame-shutdown-delay=30 --user-data-dir="C:\Documents and Settings\Win XP\Local Settings\Application Data\Google\Chrome Frame\User Data\IEXPLORE" --chrome-version=21.0.1180.89 --lang=en-US --flag-switches-begin --flag-switches-end

Windows XP, SP3 (32 bit), Chrome Frame v. 21.0.1180.89 and IE8.

Comment 9 by, Sep 24 2012

Please put the value in the key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome and try again.
Project Member

Comment 10 by, Mar 10 2013

Labels: -Area-Internals -Feature-ChromeFrame Cr-Internals Cr-ChromeFrame

Sign in to add a comment