msLaunchUri does not work reliably

Not reproducible Issue #7181860

Details

Author
Guillaume R.
Created
Apr 12, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
13.10586
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

On some computers only, the msLaunchUri API does not work (nothing happens after calling the method, no success or error callback).

  1. Register a custom URI scheme in the system
  2. Use the msLaunchUri on Edge to launch it, adding a trace to the success and error callbacks
    Expected: a prompt (Yes|No) is displayed to the user, asking whether he meant to switch app. Or the error callback to be called on failure.

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Christian F.”

    Changed Status

  • Hello,

    This item appears to be a duplicate of an existing item of feedback and will be closed out to reflect this. Please follow the existing item here for updates on this issue:

    https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/6761763/

    All the best,
    The MS Edge Team

  • Changed Status

  • As James M. from the MS Edge Team said in #6761763, the problem with the success callback needs to be treated in a separate bug, which is this one => reopening.

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Assigned To from “James M.” to “Steven K.”

    Changed Assigned To to “Balaji B.”

    Changed Assigned To to “wwatri”

  • Adding the same comments here from the duplicated bug 6761763.

    These are the four cases being tracked.  The expected results for cases #1 and #2 are assuming using your test code or a similar alerting test case (see the attached repros and README).

    1. protocol handler available AND only one AND a callback is provided
         > “supported” pop-up

    2. no protocol handler available AND a callback is provided
         > “unsupported” pop-up

    3. no protocol handler available AND a callback is not provided
         > should be a dialog to select an application to handle the request

    4. multiple protocol handlers available AND a default is not selected.
         > should be a dialog to pick a default application

    Cases #1 and #2, which I believe was the main point of your bug submission, correct me if I am wrong, are fixed and are available in latest insider fast build, “the Creator’s Update.”

    The Edge Team

  • Microsoft Edge Team

    Changed Assigned To from “wwatri” to “Jameson L.”

    Changed Status to “Confirmed”

    Changed Status from “Confirmed” to “Not reproducible”

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

Sign in