Add-ons

Developers who haven’t set this flag don’t have to worry about multiprocess compatibility and can focus on porting to WebExtensions and making the Firefox 57 deadline

Activity Stream

timspurway reports that the team has re-evaluated their schedule for landing in Nightly – new estimate puts Activity Stream in Fx57

Electrolysis (e10s)

There will be an e10s-multi experiment once Firefox 54 reaches Beta that will test 4 different cohorts: 1 content process, 2 content processes, 4, and 8. 25% of users in each. The goal is for e10s-multi to ride the Firefox 55 train.

Project Mortar (PDFium)

The team is currently dealing with process separation work, and waiting on this bug to land which will allow us to create a special type of JS-implemented plugin

The team is also tackling the printing engine as well, as we want to make sure we print PDFs as accurately as possible

Blocked on spinning up QA help for manual testing, but we will first add more automation test and compare the result of pdf.js to understand how much improvement we gain. (Thanks to bsmedberg’s suggestion!)

Talking to release team on release to-dos, and how best to keep the system add-on up to date

Why would Pocket need to be moved to an add-on? It’s been bought out by Mozilla so it makes sense to incorporate into Firefox. Pocket is still technically an extension so if you’re looking to disable it, you can set extensions.pocket.enabled to false in about:config