Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test and Adapting to Multiple Processes #26

Closed
lidel opened this issue Nov 25, 2015 · 3 comments
Closed

Test and Adapting to Multiple Processes #26

lidel opened this issue Nov 25, 2015 · 3 comments
Assignees
Labels
kind/discussion Topical discussion; usually not changes to codebase
Milestone

Comments

@lidel
Copy link
Member

lidel commented Nov 25, 2015

Dear add-on developer,

You might have heard the news[1] that future versions of Firefox will run the browser UI separately from web content. This is called Multi-process Firefox (also "Electrolysis" or "e10s")[2], and it is scheduled for release in the first quarter of 2016[3].

If your add-on code accesses web content directly, using an overlay extension[4], a bootstrapped extension[5], or low-level SDK APIs[6] like window/utils or tabs/utils, then you will probably be affected.

To minimize the impact on users of your add-ons, we are urging you to test your add-ons[7] for compatibility. You can find documentation on how to make them compatible here[8].

Starting Nov. 24, 2015, we are available to assist you every Tuesday in the #addons channel on irc.mozilla.org[9]. Click here[10] to see the schedule. Whether you need help testing or making your add-ons compatible, we're here to help!

Sincerely,
The Add-ons Team

[1] https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/
[2] https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox
[3] https://wiki.mozilla.org/Electrolysis#Schedule
[4] https://developer.mozilla.org/en-US/Add-ons/Overlay_Extensions
[5] https://developer.mozilla.org/en-US/Add-ons/Bootstrapped_extensions
[6] https://developer.mozilla.org/en-US/Add-ons/SDK/Low-Level_APIs
[7] https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox#Testing
[8] https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox#Updating_your_code
[9] irc://irc.mozilla.org/addons
[10] https://atsay.github.io/e10s_office_hours/

@lidel lidel added the kind/discussion Topical discussion; usually not changes to codebase label Nov 25, 2015
@lidel lidel self-assigned this Nov 25, 2015
@lidel lidel closed this as completed in e7cd8b9 Nov 27, 2015
This was referenced Nov 27, 2015
@the8472
Copy link
Contributor

the8472 commented Dec 14, 2015

I think adding the flag is not sufficient. the protocol handler needs to be registered in content processes too for example.

@lidel
Copy link
Member Author

lidel commented Dec 14, 2015

To be honest I just 'assumed' it works natively: got no warnings about slow e10 shims etc.

I tried to confirm it but I was unable to find any good documentation regarding protocol handlers in e10s – do you have any resources in mind?

@the8472
Copy link
Contributor

the8472 commented Dec 14, 2015

No concrete documentation, but i did some work on greasemonkey and there a protocol handler had to be registered in the child process too to make it work.

I'll do some testing on my end first, maybe a PR will fall out of it too ;)

@lidel lidel added this to the v1.4.0 milestone Jan 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/discussion Topical discussion; usually not changes to codebase
Projects
None yet
Development

No branches or pull requests

2 participants