navigator.msLaunchUri(uri, successCallback, noHandlerCallback);

Fixed, flighted Issue #6761763

Details

Created
Mar 3, 2016
Privacy
This issue is public.
Fixed in build #
15026
Reports
Reported by 10 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

navigator.msLaunchUri('any.unknown.protocol:123456’,
function()
{
alert(‘success’);
},
function()
{
alert(‘failed’);
}
);

Expected Results:

navigator.msLaunchUri(uri, successCallback, noHandlerCallback);

If used with an unknow protocal, noHandlerCallback will be called instead of pop up app store.

Actual Results:

Dev Channel specific:

No

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Mara P.”

    Changed Assigned To to “Venkat K.”

    Changed Assigned To from “Venkat K.” to “Rob T.”

  • Also, as reported in Issue #7181860, sometimes, msLaunchUri simply does nothing (no popup shown, no handler called back). This as been seen on some computers, notably right after registering the protocol. Even on these computers, the problem I’m talking about now is intermittent. The fast you cannot rely on the callbacks being called makes the API too unreliable to be used in production on Edge at present time.

  • Actual Result

    — HandlerCallback /noHandlerCallback are triggered only about half of the time. When they are not triggered, nothing else appends.

    — The protocol handler is never executed.

    Edge Version

    25.10586.0.0

    Attachement

    test_case.zip

  • Microsoft Edge Team

    Changed Assigned To from “Rob T.” to “Kiril S.”

    Changed Assigned To to “wwatri”

    Changed Status to “Confirmed”

    Changed Assigned To from “wwatri” to “Lewis W.”

  • test case.zip and this issue always success in Edge. not called “noHandlerCallback”

  • Microsoft Edge Team

    Changed Assigned To from “Lewis W.” to “IE S.”

    Changed Status from “Confirmed” to “Fixed, flighted”

    Changed Assigned To from “IE S.” to “Steven K.”

  • Can anyone please tell whether this issue got fixed? If yes, then when will this fix be available for the users.

  • Microsoft Edge Team

    Changed Assigned To from “Steven K.” to “Lewis W.”

    Changed Status from “Fixed, flighted”

    Changed Assigned To from “Lewis W.” to “IE S.”

    Changed Status to “Fixed, flighted”

You need to sign in to your Microsoft account to add a comment.

Sign in