Closed Bug 1514793 Opened 6 years ago Closed 6 years ago

Custom Protocol problem after version 64 update

Categories

(Firefox :: Untriaged, defect)

64 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1514834

People

(Reporter: rdelay, Unassigned)

Details

Attachments

(1 file)

Attached image firefox error.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 Steps to reproduce: We have a custom protocol and a launch page that tries to launch it and if it cant it will try to download and install the app to register the protocol. Once Firefox updated to 64 this stopped working. From what I can tell the catch never gets triggerd in the function below: function openUriUsingFirefox(uri, failCb, newInstall) { var iframe = document.querySelector("#hiddenIframe"); if (!iframe) { iframe = _createHiddenIframe(document.body, "about:blank"); } try { iframe.contentWindow.location.href = uri; } catch (e) { if (e.name == "NS_ERROR_UNKNOWN_PROTOCOL") { failCb(); } } } we have made no code changes and Version 63 worked just fine. Actual results: The page stops processing because the try never fails. Expected results: The try should fail and then call the failCB() function in the catch. See the attached screen show from the catch() while running version 63
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: