Closed
Bug 1322122
Opened 8 years ago
Closed 7 years ago
Add-ons that register a handler for a URI scheme do not work since FF50 (e10s on)
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: kovatsch, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160725105554
Steps to reproduce:
The FF add-on Copper uses contract @mozilla.org/network/protocol;1?name=coap in chrome.manifest to declare a protocol handler component (similar to other protocol handler add-ons such as FireFTP, which are also broken now). This worked until FF 50.
Actual results:
Since version 50, Firefox redirects the registered scheme "coap" to the search (Google by default). No error messages are displayed.
Expected results:
The defined add-on XUL page should have been loaded.
| Reporter | ||
Comment 1•8 years ago
|
||
Steps to reproduce: (Would be good if the report form would say the same)
1) Install https://addons.mozilla.org/de/firefox/addon/copper-270430/ or https://addons.mozilla.org/de/firefox/addon/fireftp/
2) Enter coap://californium.eclipse.org/ or ftp://ftp.gnu.org/
3) Add-ons are not loaded
4) Try with FF < 50 and see add-ons loaded
Due to e10s turn on. See also bug 1320470.
Blocks: e10s-addons
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Component: Untriaged → Extension Compatibility
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → All
See Also: → 1320470
Summary: Add-ons that register a handler for a URI scheme do not work since FF50 → Add-ons that register a handler for a URI scheme do not work since FF50 (e10s on)
| Reporter | ||
Comment 3•8 years ago
|
||
Thanks a lot, helps for now!
Will there be any documentation how to register protocol handlers with e10s? (add-on handler, not the Web-based kind)
Comment 4•7 years ago
|
||
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•