1175056 - Owncloud mail issue with e10S

Status: RESOLVED DUPLICATE of bug 940206

(Firefox :: Untriaged, defect)

Description

[Baudouin Feildel]

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

Steps to reproduce:

Use the Owncloud Mail app in Firefox developer edition with e10s activated.


Actual results:

Javascript error that block the page while loading. This doesn't happen in non e10s window.

Here is the javascript error:

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]

This error is triggered by that line: https://github.com/owncloud/mail/blob/v0.1.3/js/mail.js#L303


Expected results:

The page should load normally.

Comment 1

[Tracy Walker [:tracy]]

Can you try with a new profile or with all of your add-ons disabled?

Comment 2

[Baudouin Feildel]

With a new profile the same error occurs.
The new profile have no add-ons so I suppose that with all add-ons disabled the same will occur.

Comment 3

[Loic]

Do I need to create a Owncloud account to test the mail app?

Comment 4

[Baudouin Feildel]

I can open an account for you on my instance, contact me directly by email.

Comment 5

[Loic]

IMHO, it would be nice to have a guest account, so Mozilla devs/triagers could test, especially when it will be fixed (if there is a bug).

Comment 6

[Baudouin Feildel]

I understand your point. I am not the mail app developer. I will contact him to see if it is possible to provide such an account. Meanwhile peoples who wants to test the mail app can contact me directly by email.

Comment 7

[Baudouin Feildel]

FYI: here is the related bug for Owncloud Mail app : https://github.com/owncloud/mail/pull/818

Comment 12

[Ian Nartowicz]

Is this not exactly the same as bug 117098, now fixed?  It is the same error message.  Perhaps someone can test with a recent nightly.

Comment 13

[Ryan Kelly [:rfkelly]]

AFAICT this is not related to Sync, moving it out of that component.

Comment 14

[Michelle Funches - QA]

@Reporter: Please confirm if this is still an issue? Can you also report your current Firefox version? 
[Firefox 42.0]

If applicable - Have you checked current Firefox DevEdition or the current Nightly build?