Firefox/AddOns/Status/current: Difference between revisions

Line 197: Line 197:
|}
|}


[A] will put link to blog that explains this - in progress https://docs.google.com/document/d/1_EynR-5y9xqg3oAuERCVkJJApnbQ5iHwPJkVuHt6U2E/edit#
[A] [https://wiki.mozilla.org/Firefox/AddOns/Status/current#Sandboxing Sandboxing and Multicontent processes details]
[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
[B] [https://wiki.mozilla.org/Firefox/AddOns/Status/current#Add-ons.2Fe10s_Program_Status_Report add-on/e10s status wiki goes into details of the release plans and is updated based on Beta results]
[C] need to link out to blog on details of this - starting ASAP in nightly... so find breaks now
[C] blog coming on Road to 57
[1] if add-ons are reported not working (functionality or impactig firefox) there are _ options....  We can ....
[1] Link to blog coming on road to 57
[2] define legacy
[2] Legacy are any
[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.
[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 ===
Confirmed users
1,094

edits