Every two weeks, engineering teams working on Firefox Desktop get together and update each other on things that they’re working on. These meetings are public. Details on how to join, as well as meeting notes, are available here.

We feel that the bleeding edge development state captured in those meeting notes might be interesting to our Nightly blog audience. To that end, we’re taking a page out of the Rust and Servo playbook, and offering you handpicked updates about what’s going on at the forefront of Firefox development!

Expect these every two weeks or so.

Thanks for using Nightly, and keep on rocking the free web!

Highlights

Contributor(s) of the Week

The team has nominated Adam (adamgj.wong), who has helped clean-up some of our Telemetry APIs. Great work, Adam!

Project Updates

Add-ons

andym wants to remind everybody that the Add-ons team is still triaging and fixing SDK bugs (like this one, for example).

Electrolysis (e10s)

mconley reports that a11y and touchscreen support landed in 51, but might not go out in that release, as there are still a few bad bugs with it.

mconley also wants everybody to know that we’re currently on track to ship Firefox with two content processes by default in Firefox 52, so stay tuned for that.

Core Engineering

ksteuber rewrote the Snappy Symbolication Server (mainly used for the Gecko Profiler for Windows builds) and this will be deployed soon.

felipe is in the process of designing experiment mechanisms for testing different behaviours for Flash (allowing some, denying some, click-to-play some, based on heuristics)

Platform UI and other Platform Audibles

Quality of Experience

mikedeboer has re-enabled the new Find in Page mode on Nightly, and is working on fixing performance and behaviour bugs

dao continues on his quest to improve the default theme in high-contrast display settings

Sync / Firefox Accounts

Uncategorized

A discussion is underway in firefox-dev concerning the organization of tests, and how “Firefox UI” tests fit in. These will likely be put in “puppeteer” subdirectories.

Here are the raw meeting notes that were used to derive this list.

Want to help us build Firefox? Get started here!

Here’s a tool to find some mentored, good first bugs to hack on.