We are usingnavigator.msLaunchUri method as protocol handler in our application. As per the MSDN documentif the user's system does not have a program registered to handle a specific protocol, the Internet Explorer will invoke thenoHandlerCallback. It is the fallback mechanism which the developer can define to handle when such scenarios happen. But in case of EDGE thenoHandlerCallback is not executed. It is automatically redirecting to the default fallback mechanism of opening the Windows Store dialog to open the program. Can someone confirm if such issue is happening in EDGE? If yes, can we expect a fix sometime soon?
Thanks.