1177098 - registerProtocolHandler raises an NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS exception: "aWindow.QueryInterface is not a function"

Status: RESOLVED DUPLICATE of bug 1175056

(Firefox :: Untriaged, defect)

Description

[Daniel Llewellyn]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150623004006

Steps to reproduce:

1. install owncloud instance
2. install the owncloud addon "mail"
3. navigate to the mail "app" in your owncloud instance
4. check the console for errors after noticing that the page doesn't fully load


Actual results:

Exception copied below:

16:58:46.607 NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: [JavaScript Error: "aWindow.QueryInterface is not a function" {file: "resource://gre/modules/PrivateBrowsingUtils.jsm" line: 49}]'[JavaScript Error: "aWindow.QueryInterface is not a function" {file: "resource://gre/modules/PrivateBrowsingUtils.jsm" line: 49}]' when calling method: [nsIWebContentHandlerRegistrar::registerProtocolHandler]1 mail.js:303:0

The following javascript code from the mail addon for OwnCloud appears to be the trigger:

var url = window.location.protocol + '//' + window.location.host + OC.generateUrl('apps/mail/compose?uri=%s');
window.navigator.registerProtocolHandler("mailto", url, "ownCloud Mail");

This leads to a complete failure of the web page.


Expected results:

I believe the code should prompt the user to accept that the mailto: handler on the operating system is adjusted to point to firefox loading the URL it generates (OC.generateUrl('apps/mail/compose?uri=%s')).

Comment 1

[Loic]

With e10s disabled, it should work.