Closed Bug 582397 Opened 14 years ago Closed 1 year ago

Extension cannot register protocol handler

Categories

(Firefox :: General, defect)

4.0 Branch
x86
Linux
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0b2) Gecko/20100720 Firefox/4.0b2
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b2) Gecko/20100720 Firefox/4.0b2

I am currently developing an extension to handle the market:// protocol.
Currently it works in the most recent Firefox stable on all platforms, however it does not work in FF 4 B2
The extension is based on the exsisting FF 3.* extension "MLDonkey Protocol Handler"

Reproducible: Always

Steps to Reproduce:
1. Install extension that handles a protocol in FF 3.*
2. Attempt to open a URI for the protocol being handled.
3.
Actual Results:  
Firefox returns a prompt "Firefox doesn't know how to open this address, because the protocol (market) isn't associated with any program."

Expected Results:  
The link is passed to the relevant protocol handler.
Are you sure that the external application exists, is executable and you set the correct path to it ?
The extension does not pass the URI to an external application, rather it is processed by an internal function within the extension.

It does work correctly under FF 3.*
Version: unspecified → 4.0 Branch
QA Whiteboard: qa-not-actionable

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --

Old-school XUL add-ons are unfortunately no longer around, but we do have WebExtension APIs for registering protocol handlers: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/protocol_handlers

I would be very surprised, Paddy, if you're still blocked on this somehow, but just in case, the above documentation may be helpful. We're going to close this one out as INCOMPLETE in the interim.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.