chrome:// URLs cannot be opened using command line arguments
Reported by
thehunmo...@gmail.com,
Jul 29 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.13 Safari/537.36 Steps to reproduce the problem: 1. Open a Terminal window in OS X 2. Run the following command: open -a "Google Chrome" --args chrome://settings What is the expected behavior? A new instance of Chrome is opened, with the chrome://settings page loaded What went wrong? The chrome://settings page does not load Did this work before? N/A Chrome version: 61.0.3163.13 Channel: dev OS Version: OS X 10.12.5 Flash Version: The following command works fine for opening normal URLs: open -a "Google Chrome" --args http://example.com It is possible to set chrome:// URLs as startup pages in the UI, and it seems they should also be supported via CLI.
,
Aug 1 2017
As reported this issue is only with Chrome specific url's, Since this works fine on Windows and Mac with regular url's : Windows : C:\Program Files (x86)\Google\Chrome\Application/chrome.exe android.com Mac : /Applications/Google \Chrome.app/Contents/MacOS/Google\ Chrome android.com
,
Aug 2 2017
,
Aug 4 2017
,
Aug 4 2017
Agreed with comment 1; this seems intentional. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by woxxom@gmail.com
, Jul 29 2017