ismailhabib/custom-protocol-detection

Issues

• uri何如获取的

  #47 opened 2 years ago by Wdd1050210965
  1

• Firefox Version 64.0

  #37 opened 6 years ago by heural
  12

• ERROR ReferenceError: onBlur is not defined while tried to open custom protocol on edge and chrome on laest versions using custom-protocol-check npm package

  #49 opened 2 years ago by Kundansp
  0

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

  #48 opened 2 years ago by Wdd1050210965
  0

• The failure callback is called even when protocol is defined

  #44 opened 4 years ago by jaimestuardo
  1

• my Page in an iframe occur error DOMException: Blocked a frame with origin "null" from accessing a cross-origin frame

  #46 opened 3 years ago by Hjw52
  1

• my page running in an iframe , onBlur function not run, i have registered with top level window

  #17 opened 8 years ago by he0xff
  4

• After the 85 version of Google browser，window can‘t monitor blur of alert

  #45 opened 4 years ago by CarosZch
  5

• Uncaught SyntaxError: Lexical declaration cannot appear in a single-statement context

  #42 opened 4 years ago by emanuelespies
  1

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

  #3 opened 9 years ago by ArfyFR
  6

• Open the client's API for success or failure callback?

  #41 opened 4 years ago by liganggang
  0

• the bug in Firefox

  #40 opened 5 years ago by Cyhai18
  1

• Div in example

  #38 opened 5 years ago by zatarus
  0

• False positive protocol detection in Firefox after install-uninstall of custom protocol

  #21 opened 8 years ago by 40rn05lyv
  2

• In Chrome if user selects the "Remember my choice for all links of this type" check box the fail callback always gets called.

  #1 opened 10 years ago by spstratis
  6

• Need to control timeouts for some browsers

  #35 opened 6 years ago by nm777
  1

• "Remember my choice for all links of this type" selected

  #13 opened 8 years ago by ryanheath86
  4

• Protocol detection does not fail on Firefox Quantum

  #32 opened 7 years ago by pegiadise
  4

• Is it possible to wait until browser custom protocol confirmation to be accepted?

  #31 opened 7 years ago by kirill-konshin
  2

• Safari in Mac OS X and custom protocol

  #16 opened 7 years ago by abbesch
  1

• Does not work with Safari

  #30 opened 7 years ago by kirill-konshin
  3

• Edge and msLaunchUri

  #7 opened 9 years ago by yoisn
  2

• Chrome and custom protocol

  #8 opened 9 years ago by edwardstumpf
  6

• Protocol detection in Edge in Windows 10 doesn't work

  #22 opened 8 years ago by KushnirDV
  4

• Firefox 53 not working

  #28 opened 7 years ago by jgordor
  1

• Automated tests

  #27 opened 7 years ago by ismailhabib
  0

• firefox NS_ERROR_FAILURE

  #24 opened 8 years ago by mafar
  3

• Both success and failure callbacks are executed in IE

  #20 opened 8 years ago by 40rn05lyv
  0

• Protocol detection in IE11 in Windows 7 doesn't work

  #19 opened 8 years ago by 40rn05lyv
  1

• line 187 - url should be uri

  #15 opened 8 years ago by justinbangerter
  2

• Success callback

  #6 opened 8 years ago by sraimund
  7

• protocolcheck.js is marked as JS.Downloader by SEP

  #11 opened 8 years ago by guojilin0
  0

• Request for OSS license

  #9 opened 9 years ago by mattlebeau
  2

• Chrome/Edge

  #5 opened 9 years ago by maartenpeels
  1

• Nothing for Safari

  #2 opened 9 years ago by spignataro
  1