ChromeHTML URL Protocol Handler does not work as expected (v2)
Reported by
d.vanha...@gmail.com,
Mar 8 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36 Example URL: ChromeHTML://www.example.com Steps to reproduce the problem: See issue 413236 1. Create a html page containing <a href="ChromeHTML://www.example.com">example</a> 2. Open the testpage in Internet Explorer and click on the example link. 3. A pop-up appears. Allow the website to open a program on your computer. 4. If Chrome was running, an new, window appears whith the home screen, otherwise a chrome.exe process starts and stops without displaying anything. What is the expected behavior? Chrome should start and open the URL What went wrong? Via Microsoft Sysinternals Process Monitor, I can see this got started : "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -- "chromehtml://www.example.com/" This is as expected when you read this thread: https://productforums.google.com/forum/#!topic/chrome/FrYaE4GBjD4 Doing the same command via the prompt has the same effect. Chrome only starts when chromehtml (Indeed in lowercase, probably caused by IE.) is replaced by HTTP. But this is not a solution because we want to switch to Chrome when users are using another browser. Did this work before? N/A Chrome version: 49.0.2623.75 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 20.0 r0 IE Version 11.0.10586.0
,
Mar 8 2016
Indeed. I was checking its progress when it got closed, so I opened a new issue. The other one was windows 7, I have windows 10.
,
Jul 26 2016
It happens on Windows 7 too. This is causing issues for some apps in our estate It does seem, at least in part, attributable to what the Chrome installer pokes into the Classes hive: The default value for HKLM\SOFTWARE\Classes\ChromeHTML\shell\open\command depending on the bitness of OS currently reads: "C:\Program Files\Google\Chrome\Application\chrome.exe" -- "%1" or "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -- "%1" With this configuration a URL crafted "chromehtml://www.google.com/" will open a new Chrome window but not the address, and ONLY if a Chrome instance is already running. To be able to at least pass the address through, it needs loose the quotes around "1" because the following does work: "C:\Program Files\Google\Chrome\Application\chrome.exe" -- %1 or "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -- %1 On Windows 7 we still have the issue that we can't seem to get Chrome to spawn an instance of itself unless one is already running.
,
Jul 26 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by svaldez@chromium.org
, Mar 8 2016Components: -Internals>Network Internals>PlatformIntegration