Issue 377404 in chromium: Custom protocol handler not launching external applications anymore

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Bug-Regression OS-Windows

New issue 377404 by simon.vi...@gmail.com: Custom protocol handler not
launching external applications anymore
http://code.google.com/p/chromium/issues/detail?id=377404

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

Steps to reproduce the problem:
1. Have a custom protocol handler registered in the windows registry, as
described here:
http://msdn.microsoft.com/en-us/library/ie/aa767914(v=vs.85).aspx

For testing purposes I added the following handler to the registry which
simply runs notepad:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\notepadtest]
"URL Protocol"="\"\""
@="URL:notepadtest Protocol"

[HKEY_CLASSES_ROOT\notepadtest\shell]

[HKEY_CLASSES_ROOT\notepadtest\shell\open]

[HKEY_CLASSES_ROOT\notepadtest\shell\open\command]
@="\"C:\\Windows\\notepad.exe\" %1"

2. Try the above custom protocol by entering the following command in the
JavaScript console: "window.location = 'notepadtest:something.txt'"

What is the expected behavior?
A dialog should appear asking me if I want to launch the external
application.

What went wrong?
Nothing happens.

Did this work before? Yes Prior to version 35

Chrome version: 35.0.1916.114 Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 13.0 r0

In all other browsers this still works. Is this a bug or a "security
feature" since Chrome 35?

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #1 on issue 377404 by fr...@grabcad.com: Custom protocol handler

not launching external applications anymore
http://code.google.com/p/chromium/issues/detail?id=377404

Starting Chrome with --enable-logging --v=1 shows the following log
entries in "chrome_debug.log" after entering "window.location
= 'notepadtest://something.txt'" in the JS console:

[4568:8668:0528/205433:VERBOSE1:resource_loader.cc(447)]
CancelRequestInternal: notepadtest://something.txt
[4568:8668:0528/205433:VERBOSE1:resource_loader.cc(621)] ResponseCompleted:
notepadtest://something.txt
[4568:4760:0528/205433:VERBOSE1:navigator_impl.cc(192)] Failed Provisional
Load: notepadtest://something.txt, error_code: -3, error_description:
Unknown error., showing_repost_interstitial: 0, frame_id: 1

This used to work in version 34 and earlier.

On Mac OS X 10.8 Chrome 35.0.1916.114 works as expected.

[chro...@googlecode.com]

Comment #2 on issue 377404 by dennisw...@gmail.com: Custom protocol handler

not launching external applications anymore
http://code.google.com/p/chromium/issues/detail?id=377404

Ditto to the experience described, except it fails on OSX 10.9.3 Chrome
35.0.1916.114 in my testing also.

[chro...@googlecode.com]

Comment #3 on issue 377404 by dennisw...@gmail.com: Custom protocol handler

not launching external applications anymore
http://code.google.com/p/chromium/issues/detail?id=377404

Ah! But an update JUST came through...and it seems to work again in Chrome
35.0.1916.153.

[chro...@googlecode.com]

Updates:
Cc: ashej...@chromium.org
Labels: Needs-Feedback

Comment #4 on issue 377404 by ashej...@chromium.org: Custom protocol

handler not launching external applications anymore
http://code.google.com/p/chromium/issues/detail?id=377404

@ simon.vizzini83: Would you mind checking the above issue on latest
35.0.1916.153 as per comment#3.

Thank you!

[chro...@googlecode.com]

Comment #5 on issue 377404 by simon.vi...@gmail.com: Custom protocol

handler not launching external applications anymore
http://code.google.com/p/chromium/issues/detail?id=377404

@ ashej...: Sorry for the late reply.
I can confirm that it works again in Chrome 35.0.1916.153

Thanks alot guys for fixing it :)

[chro...@googlecode.com]

Updates:
Status: WontFix
Labels: -Needs-Feedback

Comment #6 on issue 377404 by ashej...@chromium.org: Custom protocol

handler not launching external applications anymore
http://code.google.com/p/chromium/issues/detail?id=377404

That's Great! Based on you confirmation in comment#5, I am closing the bug.
Feel free to report a new issue, if encountered with any other issue again
with newer version of chrome.
Thank you!

[chro...@googlecode.com]

Comment #9 on issue 377404 by brian.mc...@gmail.com: Custom protocol

handler not launching external applications anymore

https://code.google.com/p/chromium/issues/detail?id=377404

FWIW, the machine where I can reproduce the problem is a Windows 2012 server

[chro...@googlecode.com]

Comment #10 on issue 377404 by csalem0...@gmail.com: Custom protocol

handler not launching external applications anymore
https://code.google.com/p/chromium/issues/detail?id=377404

I'm experiencing this problem with Chrome 43.0.2357.130 on some machines.
The steps above reproduce it for me. I attached the chrome debug log, the
custom protocol we're using is pcr:


Attachments:
debug.rtf 609 KB