custom-protocol-detection
custom-protocol-detection copied to clipboard
Detect whether a custom protocol is available in browser (FF, Chrome, IE8, IE9, IE10, IE11, and Edge)
uri何如获取的
uri传什么?
For the Firefox-Version 64.0 the check stopped working. The Function openUriUsingFirefox should throw an Exception in Lines 85/86 if the protocol is not available, but in this version of firefox...
 Please help
uri随便传值,iframe.contentWindow.location.href = uri ,传入的值能打开软件就打开软件,打不开软件什么都不做,也不触发失败的回调
If protocol is defined and it is associated with an executable, browser shows an alert in order to accept or deny the execution. I think that alert causes the timeout...
chrome 95 and Official example Has anyone encountered this situation? Can this library be used on iframe pages?  
function openUriWithTimeoutHack(uri, failCb, successCb) { var timeout = setTimeout(function () { failCb(); handler.remove(); }, 1000); //handle page running in an iframe (blur must be registered with top level window) var...
Closes #35 Accepts a new `timeouts` object that contains several properties that can be used to adjust behavior for slower protocol handlers.
Handle properly the behavior if FF v76+