1097530 - [e10s] Mega.nz Add-on's 'mega:' address doesn't work

Status: VERIFIED FIXED

(Firefox :: Extension Compatibility, defect)

Description

[Demetrius S.]

Attachment: Screenshot 2014-11-12 02.09.53.png

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20141111030203

Steps to reproduce:

Installed the mega add-on from the mega website and attempted to navigate back to mega.co.nz


Actual results:

Gave a prompt that the address wasn't understood.


Expected results:

should have navigated to a mega 'chrome'

Comment 1

[Chris Peterson [:cpeterson]]

This bug is likely related to protocol handler bug 940206.

Comment 2

[Giorgio Maone [:ma1]]

(In reply to Chris Peterson [:cpeterson] from comment #1)
> This bug is likely related to protocol handler bug 940206.

No, unfortunately it seems not to be the case.

This add-on registers a XPCOM component of its own as a nsIProtoclHandler implementation in bootstrap.js, i.e. in the parent process only.

To be fixed, it needs to register this component in the child process too (either moving all the XPCOM stuff in a process script, or duplicating the registration in its already existent frame script e10s), or maybe wait and see what happens in bug 1175056.

Comment 3

[Giorgio Maone [:ma1]]

CCing Guy Kloss because he seems to be the technical lead at Mega.

Since they already have a frame script ("e10s.js"), the easiest way to attempt a fix is refactoring the their mega: nsIProtocolHandler XPCOM implementation & registration code into a module, and importing it from both bootstrap.js and e10s.js.

Comment 4

[gk]

Our browser extension developer reported that the problem is fixed for the next version. As I was told the fix did not need any such refactoring, but I wouldn't know of the exact circumstances myself.

Comment 5

[Giorgio Maone [:ma1]]

(In reply to gk from comment #4)
> Our browser extension developer reported that the problem is fixed for the
> next version. 

This seems to be fixed in 3.1.12, indeed. Thank you!

Since you already maintain a Chrome version, though, please start considering a migration to the WebExtensions API:

https://wiki.mozilla.org/WebExtensions
https://wiki.mozilla.org/WebExtensions/FAQ