From MozillaWiki
Jump to: navigation, search

Today’s meeting leader is: mconley

General Topics / Roundtable

Friends of the Firefox team

For contributions from April 20 2021 to May 4 2021, inclusive.


  • None

Resolved bugs (excluding employees)

Fixed more than one bug

  • Falguni Islam
  • Itiel
  • kaira [:anshukaira]
  • Kajal Sah
  • Luz De La Rosa
  • Richa Sharma
  • Sebastian Zartner [:sebo]
  • Vaidehi

New contributors (🌟 = first patch)

Project Updates

Add-ons / Web Extensions

Addon Manager & about:addons

  • Starting from Firefox 90, when no extensions are installed our about:addons page will show to the users a nicer message to explicitly direct them to instead of an empty list of installed extensions (Bug 1561538) - Thanks to Samuel Grasse-Haroldsen for fixing this polishing issue.
  • As part of the ongoing work to get rid of OS.File usage, Barret unveiled and fixed some races in AddonManager and XPIDatabase jsm (Bug 1702116)
  • Fixed a macOS specific issue in the “Manager Extension Shortcuts” about:addons view, which was preventing this view from detecting some of the conflicting shortcuts (Bug 1565854)

WebExtensions Framework

WebExtension APIs

  • Nicolas Chevobbe applied the needed changes to ensure that the devtools.inspectedWindow.reload method is Fission compatible also when an extension does pass to it the userAgent option (Bug 1706098)

Developer Tools


  • Neil has been working on reviving the tab unloader for when users are hitting memory limits

    • It’s smarter this time though, and should hopefully make better choices on which tabs to unload.
    • Currently disabled by default, but Nightly users can test it by setting `browser.tabs.unloadOnLowMemory` to `true`

Form Autofill

Installer & Updater

Lint and Docs

  • No updates this week

macOS Spotlight

Messaging System

New Tab Page



Password Manager

PDFs & Printing

  • No update


Performance Tools

  • Stacks now include the category color of each stack frame (in tooltips, marker table, sidebar)


  • Fixed a bug where the dot markers appear in the wrong places.





  • 156x156pxWow, much changes! Big reveal!
  • Restyled notification bars to appear as part of the browser toolbox

    • Now adapt to the theme too (dark and light mode of notification bars)
  • Modal dialogs now use the Firefox design language, much prettier!
  • Context menus on Windows have updated styling and macOS uses native context menus

    • Both will now respect system dark mode settings! 🌞🌚
  • Tabs have a new look and feel

    • Easier to see what tab is selected 👀
    • Second line of text displayed to describe audio/picture-in-picture state
    • More text is displayed when audio is playing, now that the audio button replaces the favicon when the tab is hovered
  • Icons have been updated to have lighter strokes, and a new downloads animation too!
  • Menus have been reorganized, removing less used options and renaming items to make them easier to find

Search and Navigation

  • Lots of polish fixes to Proton address bar (and search bar)
  • The Search Mode chiclet can now be closed also when the address bar is unfocused - Bug 1701901
  • Address bar results action text (for example “Switch to tab”, or “Search with Engine”) won’t be pushed out of the visible area by long titles anymore - Bug 1707839
  • Double dots in domain-looking strings will now be corrected - Bug 1580881
  • Nightly en-US only (experimental): browser.urlbar.unitConversion.enabled and browser.urlbar.suggest.calculator


This week I learned

  • [gijs] CSS `ch` units depend on the device pixel rendering of the `0` character in the font, font-size and DPI scaling. So the CSS `px` outcome of something like `50ch` can easily vary by 30px between DPI scaling (with identical font size + font), if the font forces glyphs to be rendered in line with device pixels. Unless you’re dealing with monospace text, it’s probably better to use `em` for font-size-related sizing.
  • [gijs] CSS selectors: `:root:-moz-lwtheme` works but `:host:-moz-lwtheme` does not, you want `:host(:-moz-lwtheme)`.

  • [gijs] As of October 2020, you can split `skip-if` and `fail-if` annotations in test manifests (browser.ini, mochitest.ini, etc.) across lines! This is equivalent to separating with `||` but makes it easier to read multiple conditions. E.g.:

    skip-if = os == “win” || os == “linux

    Is equivalent to:

    skip-if =
    os == “win” # fails because X
    os == “linux” # fails because Y