Issue metadata
Sign in to add a comment
|
script:// scheme protocol is working on Windows & requesting external application
Reported by
zhe2...@gmail.com,
Oct 11
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Visit the next url on latest Chrome for Windows (I checked on Windows 7): script://test 2. Popup wil appear. It isn't reproducible on the Linux/Mac, this behavior is specific for Windows-only. What is the expected behavior? No action, or opening the Google search What went wrong? Popup appeared, asking to open Mokiner in a Windows Script Component Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I'm not sure, does it have any security impact, but this behavior is unusual, so I decided to let you know, just in case. I tried to execute some code within script: protocol, but without success.
,
Oct 12
Thanks for filing the issue! Able to reproduce the issue on reported chrome version 69.0.3497.100 using Windows 10 and the same issue isn't seen on 60.0.3112.0. Hence considering it as Regression and marking it as Untriaged, adding Needs-Bisect label. Will update the bisect info soon.
,
Oct 15
++ Issue isn't seen on latest canary 72.0.3580.0 using Windows 10. Bisect Information: ------------------- Last Bad Build: 71.0.3573.0 First Good Build: 71.0.3574.0 While performing per revision bisect it is showing RuntimeError: We don't have enough builds to bisect. revlist: [] and tried doing Chromium bisect, neither this helped. Hence providing the change log from Omahaproxy https://chromium.googlesource.com/chromium/src/+log/71.0.3573.0..71.0.3574.0?pretty=fuller&n=10000 Suspecting: https://chromium.googlesource.com/chromium/src/+/d19a75fc26fd0ab1ce79ef3d1c1c9b3cc1fbd098 Review URL: https://chromium-review.googlesource.com/c/1256208 @Mustafa Emre Acer: Please help in assigning it to the right owner, if this isn't related to your change. Please feel free to adjust the Milestone.
,
Oct 15
These were never intended to be supported. Can you please check whether you have a "URL Protocol" key under HKEY_CLASSES_ROOT\script in your registry? If no, then this is working as intended. Proper URL schemes must have an empty "URL Protocol" key, you can manually create one as a workaround to keep this working.
,
Oct 25
Closing per comment #4. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Oct 12