MozillaWiki

Firefox/AddOns/Status/current: Difference between revisions

Page Discussion

Firefox/AddOns/Status/current (view source)

Revision as of 18:42, 15 February 2017

2,565 bytes added ,  15 February 2017
m
→‎Schedule: update
m (→‎Schedule: update)
Line 176: Line 176:


== Schedule ==
== Schedule ==
The following schedule covers rollout of the single content process feature to release builds.
{| class="wikitable"
|-
! Date !! Nightly !! Aurora !! Beta !! Release !! Target % !! Submission Criteria
|-
|2017-01-24 || Fx 54: Sandboxing and multi content processes [A] || 53 default|| Fx 52: All but MPC=False|| Fx 51: everything from Fx50 and ~750 add-ons not marked MPC=True [B]. || 7 ||
|-
|2017-03-07 || Fx 55 ||Fx 54: Sandboxing and multi content processes [A]||Fx 53: All but MPC=False [B]|| Fx 52: same as 51|| 14||
|-
|2017-04-18 || Fx 56 || 55 default ||Fx 54: Sandboxing and multi content processes [A]. Disable direct CPOW access. [4]||Fx 53: All but MPC=False get e10s [1]||34 || Submissions: Stop accepting new Legacy [2] add-ons (still accepting Legacy updates). New Webextensions only.
|-
|2017-06-12 ||Fx 57: Stop running Legacy add-ons (no MPC=False add-ons and remove e10s compatibility shims). [C]|| 56 default || 55 default ||Fx 54: Sandboxing and multi content processes [A]. || * ||
|-
|2017-08-07 || Fx 58 ||Fx 57: Webextension only. Stop running Legacy add-ons (no MPC=False add-ons and remove e10s compatibility shims). [C]||Fx 56: Beta supporting only webextensions.|| 55 || * ||
|-
|2017-10-02|| Fx 59 || 58 default ||Fx 57: Webextensions Only. Stop running Legacy add-ons (no MPC=False add-ons and remove e10s compatibility shims). [C]|| 56 || * ||
|-
|2017-11-15|| Fx 60 || 59 default || 58 default ||Fx 57: Webextensions only.  Stop running Legacy add-ons (no MPC=False add-ons and remove e10s compatibility shims). [C]||38 || Submissions: stop accepting Legacy add-ons updates. Only webextensions and updatese to webextensions
|}


[A] will put link to blog that explains this - in progress https://docs.google.com/document/d/1_EynR-5y9xqg3oAuERCVkJJApnbQ5iHwPJkVuHt6U2E/edit#
[B] add-on/e10s status wiki goes into details of the release plans and is updated based on Beta results https://wiki.mozilla.org/Firefox/AddOns/Status/current#Add-ons.2Fe10s_Program_Status_Report and https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule
[C] need to link out to blog on details of this - starting ASAP in nightly... so find breaks now
[1]  if add-ons are reported not working (functionality or impactig firefox) there are _ options....  We can ....
[2] define legacy
[4] Direct CPOW access was not expected and not initially blocked with MPC=True.  There were ~60 add-ons that did this.  It was fixed so no new ones could and temporary "allow" list for add-ons that did.  That will be removed in Beta 54, but then ride to Release 55.
=== Sandboxing ===
=== Sandboxing ===
Content security sandboxing in Firefox is a security measure that restricts operating system access malicious content can gain through security vulnerabilities. Add-ons which interact with the file system through [https://developer.mozilla.org/en-US/Add-ons/SDK/Guides/Content_Scripts content scripts] will be impacted by [https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Limitations_of_frame_scripts this feature]. Currently file system write restrictions are rolling out on various platforms in Firefox 50 and Firefox 52. File system read restrictions will start rolling out in Firefox 54. Add-on authors should familiarize themselves with [https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Limitations_of_frame_scripts areas of the file system that will be blocked by these features] as they roll out, and adjust their Add-on code to avoid any potential issues.
Content security sandboxing in Firefox is a security measure that restricts operating system access malicious content can gain through security vulnerabilities. Add-ons which interact with the file system through [https://developer.mozilla.org/en-US/Add-ons/SDK/Guides/Content_Scripts content scripts] will be impacted by [https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Limitations_of_frame_scripts this feature]. Currently file system write restrictions are rolling out on various platforms in Firefox 50 and Firefox 52. File system read restrictions will start rolling out in Firefox 54. Add-on authors should familiarize themselves with [https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Limitations_of_frame_scripts areas of the file system that will be blocked by these features] as they roll out, and adjust their Add-on code to avoid any potential issues.
Line 195: Line 221:
<p></p>
<p></p>
There is a preference you can check to see if multiple content processes are enabled.  In about:config, a dom.ipc.processCount of 1 means that multiple content processes are not enabled.  Any number higher than 1 and the browser is using multiple processes.  To troubleshoot if your add-on is experiencing issues from multiple content processes, you can reset the number to 1 to see if the issue goes away.
There is a preference you can check to see if multiple content processes are enabled.  In about:config, a dom.ipc.processCount of 1 means that multiple content processes are not enabled.  Any number higher than 1 and the browser is using multiple processes.  To troubleshoot if your add-on is experiencing issues from multiple content processes, you can reset the number to 1 to see if the issue goes away.




Sescalante
Confirmed users
1,094

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1163049"