Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / ismailhabib/custom-protocol-detection issues and pull requests

#48 - 为什么不管传入什么uri都不会触发失败回调

Issue - State: open - Opened by Wdd1050210965 almost 3 years ago

#47 - uri何如获取的

Issue - State: open - Opened by Wdd1050210965 almost 3 years ago - 1 comment

#45 - After the 85 version of Google browser，window can‘t monitor blur of alert

Issue - State: open - Opened by CarosZch over 4 years ago - 5 comments

#44 - The failure callback is called even when protocol is defined

Issue - State: open - Opened by jaimestuardo over 4 years ago - 1 comment

#43 - Fix the FF behavior. The iFrame should be recreated each time

Pull Request - State: open - Opened by heitara over 4 years ago

#41 - Open the client's API for success or failure callback?

Issue - State: open - Opened by liganggang over 4 years ago

#40 - the bug in Firefox

Issue - State: closed - Opened by Cyhai18 almost 5 years ago - 1 comment

#39 - Fix detection on Safari/iOS.

Pull Request - State: open - Opened by mmolinari over 5 years ago - 3 comments

#38 - Div in example

Issue - State: open - Opened by zatarus almost 6 years ago

#37 - Firefox Version 64.0

Issue - State: open - Opened by heural about 6 years ago - 12 comments

#36 - Add support for custom timeouts

Pull Request - State: open - Opened by nm777 about 6 years ago

#35 - Need to control timeouts for some browsers

Issue - State: open - Opened by nm777 about 6 years ago - 1 comment

#34 - Feature/tests

Pull Request - State: closed - Opened by dcchuck almost 7 years ago - 1 comment

#33 - Proper handling of Safari and iOS

Pull Request - State: closed - Opened by kirill-konshin almost 7 years ago - 2 comments

#32 - Protocol detection does not fail on Firefox Quantum

Issue - State: open - Opened by pegiadise over 7 years ago - 4 comments

#30 - Does not work with Safari

Issue - State: closed - Opened by kirill-konshin over 7 years ago - 3 comments

#29 - Fallback to useragent to detect brower

Pull Request - State: open - Opened by millette over 7 years ago

#28 - Firefox 53 not working

Issue - State: closed - Opened by jgordor over 7 years ago - 1 comment

#27 - Automated tests

Issue - State: open - Opened by ismailhabib over 7 years ago

#26 - Improved openUriInNewWindowHack

Pull Request - State: closed - Opened by edwardstumpf almost 8 years ago

#25 - Enhanced Firefox exception check

Pull Request - State: closed - Opened by edwardstumpf almost 8 years ago

#24 - firefox NS_ERROR_FAILURE

Issue - State: open - Opened by mafar almost 8 years ago - 3 comments

#23 - some user might be want to get failed callback on not supported browser

Pull Request - State: open - Opened by athese6 almost 8 years ago

#22 - Protocol detection in Edge in Windows 10 doesn't work

Issue - State: open - Opened by KushnirDV almost 8 years ago - 4 comments

#20 - Both success and failure callbacks are executed in IE

Issue - State: open - Opened by 40rn05lyv about 8 years ago

#19 - Protocol detection in IE11 in Windows 7 doesn't work

Issue - State: open - Opened by 40rn05lyv about 8 years ago - 1 comment

#18 - migrate module to npm package

Pull Request - State: closed - Opened by annavernidub about 8 years ago - 1 comment

#16 - Safari in Mac OS X and custom protocol

Issue - State: closed - Opened by abbesch over 8 years ago - 1 comment

#15 - line 187 - url should be uri

Issue - State: closed - Opened by justinbangerter over 8 years ago - 2 comments

#13 - "Remember my choice for all links of this type" selected

Issue - State: open - Opened by ryanheath86 over 8 years ago - 4 comments

#12 - Success Callback

Pull Request - State: closed - Opened by ryanheath86 over 8 years ago - 1 comment

#11 - protocolcheck.js is marked as JS.Downloader by SEP

Issue - State: open - Opened by guojilin0 almost 9 years ago

#10 - fixed running within an iframe under Chrome

Pull Request - State: closed - Opened by alexarnesen almost 9 years ago - 1 comment

#9 - Request for OSS license

Issue - State: closed - Opened by mattlebeau almost 9 years ago - 2 comments

#8 - Chrome and custom protocol

Issue - State: open - Opened by edwardstumpf almost 9 years ago - 6 comments

#7 - Edge and msLaunchUri

Issue - State: closed - Opened by yoisn almost 9 years ago - 2 comments

#6 - Success callback

Issue - State: closed - Opened by sraimund almost 9 years ago - 7 comments

#5 - Chrome/Edge

Issue - State: closed - Opened by maartenpeels almost 9 years ago - 1 comment

#4 - Win 10 support

Pull Request - State: closed - Opened by ismailhabib about 9 years ago

#3 - Just for you to know, since IE10 there is msLaunchURI which has a "noHandlerCallback"

Issue - State: closed - Opened by ArfyFR about 9 years ago - 6 comments

#2 - Nothing for Safari

Issue - State: closed - Opened by spignataro almost 10 years ago - 1 comment