75
edits
Changes
post London update
== Add-ons ==
* Web extension testing seems to be broken with the multiple content processes
* SDK based add-ons probably come with a big memory overhead per process.
* Running Out of process WE add-ons in separate processes?is not part of the project* Do e10sified legacy Some add-ons work?might break because of false assumptions (JSM has to be loaded* Do shimmed legacy add-ons work?per process now for example)
== Testing ==