A graph showing the Speedometer benchmark comparing Firefox, Chromium and Chrome. The graph is inverted, with higher scores appearing lower in the graph. Higher scores are better, therefore appearing lower in the graph is better. The top of the graph shows Chromium at around the 120 mark, with a slight change for the worse towards the end of June at around 110. The middle of the graph shows Firefox, rapidly closing in on Chrome, moving from ~150 to ~170, with it fully converging with the Chrome score around July 6th 2023. The bottom fo the graph shows Chrome fairly steady between ~165 and ~170.
Categories: News

Full Speed Into The Future – These Weeks in Firefox: Issue 142

Highlights

 

Friends of the Firefox team

Resolved bugs (excluding employees)

Volunteers that fixed more than one bug

  • Devesh Bisen
  • Ganna
  • Gregory Pappas [:gregp]
  • Itiel
  • Jonas Jenwald [:Snuffleupagus]
  • Sebastian Zartner [:sebo]

New contributors (🌟 = first patch)

Project Updates

Add-ons / Web Extensions

Addon Manager & about:addons
  • Some more changes have been landed as part of the “Chrome extensions import” project, in time to be included in Firefox 116 along with the rest of the changes introduced to the AddonManager internals in support of this feature:
    • A message bar in going to be shown in about:addons while the imported addon have been staged but still pending full installation – Bug 1838466
    • Staged imported extensions will be fully installed after a browser restart when the user didn’t allow the staged extensions to be fully installed before shutting down Firefox – Bug 1840352
  • Thanks to annhermy (Ganna) for contributing a fix for Bug 1754401 (related to the “Report Abuse” dialog intermittently missing padding at the bottom of the dialog)
  • Thanks to Richard Marti for fixing an about:addons regression in Thunderbird (Bug 1840086), and Niklas for following up to apply the proper longer term fix (Bug 1838041)
    • NOTE: the regression was due to the FiveStarRating reusable webcomponent – defined at toolkit-level – which was referencing a fluent file only available in desktop builds.

Developer Tools

DevTools
  • Alex is still deep into cleaning up the Debugger codebase in order to make it faster and support unload breakpoint (bug, bug, bug, bug, bug, bug, bug, bug, bug)
  • Hubert made the Netmonitor indicate if a request was resolved with DNS over HTTPS (DoH) (bug)
    • The "Headers" pane in the Network Monitor of the Firefox Desktop developer tools. It's showing a list of properties of a network request, including that the DNS Resolution occurred over DNS over HTTPS.
  • Nicolas landed a few patches to make sure the inspector works as expected with CSS nesting  (bug, bug, bug, bug, bug, bug, bug)
  • Nicolas enabled the compatibility tooltip everywhere (was Nightly only for a couple of release) (bug)
  • Julian modified HAR export so URL are set as title in the page entries (instead of the page title) (bug)
WebDriver BiDi
  • Henrik fixed a bug which prevented to correctly serialize shadow roots in some scenarios (bug)
  • Sasha implemented the browser.close command (bug)

ESMification status

  • Approx 1 year since we started.
  • ESMified status:
    • browser: 85%
    • toolkit: 99%
    • Total:  94.64% (up from 94.42%)
  • #esmification on Matrix

Information Management

  • Changes to how Recently Closed Tabs work have started to land. This is a series of changes to how these menus work to better align with people’s intuitive understanding of what “recently closed” should mean as observed in our user testing.
    • The web-extension `session` API is unchanged. This already consolidated the closed tabs from all open windows into one list. And the notion of a “current” window is tricky in this context, so restoring a tab via the API will continue to re-open it into the window it was closed from.

Migration Improvements

  • The new migration wizard was enabled by default in Firefox 115 (except for startup / onboarding migration). We’re still running an experiment on embedding the wizard during onboarding to test how successful users are in using it.
  • The extensions migration capability has uplifted to Beta (Firefox 116). It’s currently disabled behind browser.migrate.chrome.extensions.enabled while we experiment with it.
    • Since the last meeting, we also beefed up our automated testing for extensions migration.
  • CSV passwords (and by extension, Safari password) import can now be controlled via Nimbus. We’re going to be experimenting with this on the release channel at some point. Thanks to the Credential Management team for collaborating with us on this one!
  • We took the opportunity to do some refactoring and cleanup now that the new wizard has mostly stabilised.
  • We added a telemetry probe to measure how long it takes to reach the first page of both the legacy and new migration wizard.
  • We made the new migration wizard more resilient and timely when one of the other browser profiles contains a corrupted or malformed database.
  • For device migration, UX is working on finalizing updated copy for the current SUMO page to guide people through moving their data to a new device.

Picture-in-Picture

Search and Navigation

During our most recent sprint, the search and URL bar team worked on a bug bashing effort we called “Dragon Slayer”. Many of the following bugs were fixed as part of this effort. If you and your team are interested in learning more about our dragon slayer sprint, please reach out to Chris Bellini.

 

  • Dão fixed a bug where the URL bar had been losing its formatting when a user dragged an empty new tab to a separate window
  • Stephanie fixed a performance bug where pasting a long string into the URL bar was causing jank
  • Dale fixed a Quick Actions bug related to the wraparound behavior of Quick Actions buttons in the URL bar results pane when a window is narrow
  • Marco fixed a bug so that we now allow more time for the URL bar heuristic results to be returned. This fixed a heuristic provider timeout issue, which was sometimes causing unexpected searches
  • Now that Rich Suggestions has landed in Nightly, Dale fixed some bugs related to the feature: 1835695, 1840486
  • Jonathan Kingston, a software engineer at Duck Duck Go, contributed a patch to update DDG favicons to match the company’s new branding
  • Drew has landed a significant number of patches related to Pocket suggestions appearing in the URL bar: 1837097, 1841295, 1841354, 1841408, 1841409, 1841442, 1841446, 1841447
  • Daisuke also landed a Pocket Suggestions patch, one that hides the “show less frequently” option for high-confidence matches
  • Dão landed a patch that fixes an intermittent test verify failure in one of the URL bar mochitests
  • James landed a patch that enables the SERP telemetry improvements in Nightly
  • James also landed a patch that furthers the removal of the Top Sites feature
  • Mandy landed a patch that removes all code related to an autofilling search engines feature
  • Dão fixed a bug where the Go button would sometimes disappear when switching tabs. (The Go button is an arrow that appears on the right hand side of the URL bar as you’re entering text.)

Storybook/Reusable Components

No comments yet

Post a comment

Leave a Reply

Your email address will not be published. Required fields are marked *