New issue
Advanced search Search tips

Issue 629279 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Most command line flags do not work

Reported by gma...@gmail.com, Jul 18 2016

Issue description

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

Steps to reproduce the problem:
This has the same effect in both powershell, cmd, and when passed to `cmd /C "..."`

1. change directory to `C:\Program Files (x86)\Google\Chrome\Application`
2. Run chrome.exe --version
3. Run chrome.exe --window-size=300,300 (Quoted to `"300,300"` in powershell)
4. Run chrome.exe --auto-open-devtools-for-tabs

What is the expected behavior?
1. Expected version to print
2. Expected new window to open with a size of 300x300
3. Expected new window to open and as new tabs open for devtools to auto-open

What went wrong?
A new window opens in all three situations but without any other of the expected effects.

Interestingly, `chrome.exe --incognito` works as expected.

Did this work before? N/A 

Chrome version: 51.0.2704.106  Channel: stable
OS Version: 8.1
Flash Version: Shockwave Flash 22.0 r0
 
I experience the same behavior on Windows 10 using Chrome 51.0.2704.106 m (64-bit)
I tested this with Win10x64 Pro and Chrome Version 51.0.2704.106 m.  --version did not work (window opened, but no version info).  Both size and devtools worked as expected for me.
Components: UI>Browser
Labels: M-54
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on windows 7 using chrome version 51.0.2704.106 and canary 54.0.2800.0 with the below steps

1. Run chrome.exe --version
2. Run chrome.exe --window-size=300,300
3. Run chrome.exe --auto-open-devtools-for-tabs
4.for all 3 steps observed only chrome window opened

This issue is observed from M30 old builds.Hence marking it as Untriaged to get more inputs from dev team.

Thanks,
I have the same issue on Ubuntu 16.04 64-bit.
Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment