From MozillaWiki
Jump to: navigation, search

Actions from last meeting

  • Select a new meeting leader for 28 February’s meeting. Today’s meeting leader is: jared (jaws)
    • Next meeting leader will be Kit

General Topics / Roundtable (tips/tricks/FYI, productivity improvements, industry news)

Friends of the Firefox team

Project Updates Add-ons

  • [mconley] I noticed that the Sidebar API (compatible with Opera’s API) has been implemented 💰

Activity Stream

Content Handling Enhancement

  • Landed string redesign inside Downloads Panel (bug 1282662)
  • Next is the download progress indication redesign (bug 1270006, bug 1270012)
  • Both scheduled for Firefox 54, while the visual redesign landed in Firefox 52

Electrolysis (e10s)

  • e10s-multi is tentatively targeted to ride the trains in Firefox 55
    • Hoping to use a scheme where we measure the user’s available memory in order to determine maximum content process count
    • Here’s the bug to track requirements to enable e10s-multi on Dev Edition by default
  • According to our Telemetry, ~62% of our release population has e10s enabled by default now 😎

Firefox Core Engineering

Form Autofill

Go Faster

  • 1-day uptake of system add-ons is ~85% in beta (thanks to restartless), and ~72% in release (Wiki)

Platform UI and other Platform Audibles


Project Mortar (PDFium)

  • Just had a workweek, working on ways to separate PDFium to make it more standalone and import-able to Firefox

Quality of Experience

  • Preferences reorg and search project is fully underway. jaws and mconley lead a “hack-weekend” this past weekend with the MSU students working on the reorg and search projects
  • Onboarding work continues
    • Prepared to run a survey on Beta to users with automigration, to better understand why users elect to undo the import and how they feel about it
    • Verdi did some user testing with the about-to-launch Funnelcake test, and found that 3 of 7 participants experienced long Firefox hangs on startup (multiple minutes, while importing data). Currently diagnosing and working on a fix as our top priority.
      • Woo, science! 🔬


  • Fixed a glaring problem with one-off buttons in scaled (zoomed) display configurations that made the search settings button appear in a separate line.
  • We now correctly report when a search engine could not be installed due to an invalid format.
  • Some Places work mostly in preparation of support for hi-res favicons.
  • The study results from the unified-search experiment came in: one-off buttons in the awesomebar were an undeniable success, removing the search bar not so much. A followup study is being planned.

Sync / Firefox Accounts

Storage Management

  • Fischer has been working on implementing Persistent Storage section of preferences. Right now this section is hidden by default and if shown it will only show sites that have requested Persistent Storage. Eventually it will show other site data and we will remove the redundant areas of the Preferences.

Test Pilot* Two experiments, No More 404s and Tracking Protection, are graduating this week from the Test Pilot program.

This week I learned

  • [mconley / jaws]: If you do window.getComputedStyle on a node that is not appended, you can still cause a style / layout flush for the global that the node belongs to.
  • [mconley] A reminder that setting an unload or beforeunload event handler within “content” bypasses bfcache.
    • [MattN] You can often use a pagehide listener instead
  • [MattN] Be careful with `this` in content scripts since it refers to the tab global, not the scripts’ top-level scope. e.g. `XPCOMUtils.defineLazyModuleGetter(this, "SomeName", …)` leaks `SomeName` outside the content script onto the tab global. See, bug 1338907 and bug 673569.
    • [jaws] Can we have an eslint rule for this? We would need a way to mark scripts as content scripts