Closed Bug 1047432 Opened 6 years ago Closed 2 years ago

"Multifox" add-on does not work with e10s

Categories

(Firefox :: Extension Compatibility, defect)

x86
Windows 7
defect
Not set

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
e10s + ---

People

(Reporter: karthikeyansgexecutives, Unassigned)

References

()

Details

(Keywords: addon-compat)

1. Install the "Multifox" on Firefox Nightly with "browser.tabs.remote.autostart" value 'TRUE'
2. Sign into gmail account on Default windows of "Multifox"
3. Locate the "Multifox" add-on on Menu bar
4. Click on it to choose "new" option to open a new window
5. Type in the gmail.com in the address bar of newly opened Firefox nightly window

Desired result:

The browser windows takes you to login screen of gmail.com

Actual result:

The browser windows opens up the signed in gmail account from default window.
tracking-e10s: --- → ?
Mentor: cpeterson
Keywords: addon-compat
I can confirm the newly-opened (by multifox) window has the same Google credentials as I have in the window from which I spawned the second multifox window.
Status: UNCONFIRMED → NEW
Ever confirmed: true
The developer has been contacted through AMO.
I think I'll wait for the availability of a more comprehensive documentation.
(In reply to Jeferson Hultmann from comment #3)
> I think I'll wait for the availability of a more comprehensive documentation.

Is there anything in particular that you think is missing from the docs?
For example: https://developer.mozilla.org/en-US/docs/Observer_Notifications

Where observers for "http-on-modify-request" or "document-element-inserted" should be placed? Chrome or frame script?
(In reply to Jeferson Hultmann from comment #5)
> For example: https://developer.mozilla.org/en-US/docs/Observer_Notifications
> 
> Where observers for "http-on-modify-request" or "document-element-inserted"
> should be placed? Chrome or frame script?

Jeferson, the MDN documentation is still in flux. This MDN page has an e10s code example using "http-on-modify-request" (in chrome script) and mentions "document-element-inserted" (in frame script):

https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Pitfalls_for_add-on_developers

HTTP networking happens in the chrome process. Document changes happen in the content process.
If you have any other e10s questions, just drop by the #e10s IRC channel on irc.mozilla.org (https://wiki.mozilla.org/IRC).
Glad to see new documentation!

It seems I'll need to wait until bug 1108827 gets fixed, because currently there is no equivalent method for
httpChannel.notificationCallbacks.getInterface(Ci.nsILoadContext).associatedWindow

(Something like nsIHttpChannel.associatedInnerWindowID would be enough!)
Depends on: 1108827
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.