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

Issue 598168 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 20
Cc:
█ brajkumar@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Global command line flags

Reported by afagag...@gmail.com, Mar 26 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2687.0 Safari/537.36

Steps to reproduce the problem:
1. SETX /M CHROMIUM_FLAGS "--disable-images"
2. SETX /M CHROMIUM_USER_FLAGS "--disable-images"

What is the expected behavior?
Chrome should load the command line from environment variable.

What went wrong?
Apparently this works on Linux but not on Windows for some reason. 

Did this work before? N/A 

Chrome version: 51.0.2687.0  Channel: dev
OS Version: 6.3
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by brajkumar@chromium.org, Mar 31 2016

Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows 7 using chrome Dev M51-51.0.2687.0 & 51.0.2693.2 by following steps mentioned below.

1. Opened cmd prompt 
2. Typed C:\Users\brajkumar\AppData\Local\Google\Chrome\Application\chrome.exe SETX /M CHROMIUM_FLAGS "--disable-images"
3. Pressed enter
4. Observed that chrome opened by enabling the mentioned flag via command line

afagagtea@ - Could you please confirm is this is the issue you are talking about? If yes, please do recheck this issue by upgrading your chrome latest Dev M51-51.0.2693.2. If issue still persists please provide detailed steps of repro.

Thanks!
598168.JPG
103 KB View Download

Comment 2 by afagag...@gmail.com, Mar 31 2016 

1. Open cmd prompt 
2. SETX /M CHROMIUM_FLAGS "--disable-images"
3. Clos cmd prompt
4. Open cmd prompt (to refresh environment variables)
5. cd "C:\Program Files (x86)\Google\Chrome\Application\"
6. chrome.exe
7. Chrome does not register any global flag from environment variable

This was tested in a Windows 8.1 VM.
chrome.PNG
29.1 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 1 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by afagag...@gmail.com, Apr 5 2016 

Has this been resolved yet?

Comment 5 by brajkumar@chromium.org, May 13 2016

Labels: -Needs-Review
Owner: ----
Status: Untriaged (was: Unconfirmed)
Tested this issue on Windows 7 using chrome latest Dev M52-52.0.2729.3 by following steps mentioned in the comment #2. Observed chrome does not register global flag from environment variable. 

This is a non-regression issue seen from past M35-35.0.1849.0, Hence marking it as untriaged.

Thanks!

Comment 6 by dtapu...@chromium.org, Nov 20

Status: WontFix (was: Untriaged)
Chromium doesn't support global flags.

On Linux (I presume you mean a debian based release) they support the chromium flags in the shell wrapper. (see https://sources.debian.org/src/chromium-browser/70.0.3538.102-1/debian/scripts/chromium/?hl=88#L88)

You could certainly create your own shell wrapper for windows as well.
►

Sign in to add a comment