The newly revamped Firefox View is shown in a Firefox window. The "Recent browsing" section is selected, showing 1 tab under "Open tabs", 5 tabs under "Recently closed tabs", and a call to sign in to a Firefox Account in order to get tabs from other devices.
Categories: News

All Lights Green for 119 – These Weeks in Firefox: Issue 145


Friends of the Firefox team

Resolved bugs (excluding employees)

Volunteers that fixed more than one bug

  • Masatoshi Kimura [:emk]
  • Sebastian Zartner [:sebo]
  • Zac Svoboda :zacnomore

New contributors (🌟 = first patch)


Project Updates

Add-ons / Web Extensions

WebExtensions Framework
  • In Bug 1851373, we fixed a regression (Bug 1830767) related to event pages being terminated while still running. This is a short-term workaround that we also uplifted to both Beta and Release. The longer term fix is now tracked by Bug 1844041.
WebExtension APIs
  • Fixed a bug that was making the scripting API method getRegisteredContentScripts to be returning scripts registered using the contentScripts API by the same extension – Bug 1851173.
    • NOTE: only manifest_version 2 extensions may have been able to hit this bug, and only if they are using both APIs (e.g. as part of transitioning to scripting API from contentScripts API but keeping the use of the contentScripts API for cases where the scripting API couldn’t be still used for). We don’t expect this bug to have been hit that often.
  • As part of migrating WebCompat built-in to the scripting API, we ran into Bug 1853409 because the scripting API matchAboutBlank is unconditionally set internally and we do not expose it in the API (See Bug 1853013 comment 6). As a short term workaround, we agreed with the WebCompat team to special-case the WebCompat extension ID in Bug 1853412 until the underlying Bug 1853409 has been fixed.

Developer Tools

  • Contributors
    • Sebastian Zartner (:sebo) added inactive CSS warnings for ignored properties on
      • ::placeholder pseudo-elements (bug)
      • ::first-letter pseudo-elements (bug)
      • ::cue pseudo-elements (bug)
    • Zac Svoboda (:zacnomore) made a lot of contributions in the last 2 weeks
      • Switch to Data view when JSON is broken (bug)
      • Fixed color contrast for Layout flexbox highlight toggle (bug)
      • Tweaked spacing on compatibility panel elements (bug)
      • Fixed a typo in a property name (bug)
    • LyScott123 made wrapped primitive value visible in console/debugger (bug)
      • The DevTools Console is shown with the following code executed: `Object(123)`. Below that, the primitive value of 123 is represented in a tree that lists the primitive value as well as the underlying object prototype.

        Who could object to this?

    • krishna.ravi732 fixed a bug in top-level await console evaluation and for loops (bug)
  • Arai added column source notes to binary operator and function call arguments so the debugger can underline the right expression for Uncaught TypeError (bug)
  • Alex improved the debugger performance (e.g. opening a big file is 20% faster) keeping data in a worker and then querying the worker, instead of transfering the data from the worker to the main thread (bug, bug)
  • Bomsy fixed an issue that would lead to debugger crashes (bug)
  • Nicolas made the Computed panel show custom properties value (bug)
    • The DevTools style rules pane is shown, with the "computed" panel next to it. The style rules pane shows a single rule for a CSS variable that is a calculation using a number of other variables whose values aren't shown. In the computed pane, that same calculation is shown, but with the variables replaced with their underlying values.

      Simplification for the win!

  • Nicolas made the Rule view refresh when a stylesheet is added to the page (bug)
WebDriver BiDi
  • Sasha implemented the script.realmDestroyed event which lets clients know when the realm is not available anymore for script evaluation (bug)
  • Sasha implemented the browsingContext.userPromptClosed event (bug)
  • Henrik implemented the browsingContext.reload, which provides a simple API to reload a given browsing context (bug)
  • Julian updated our vendored version of puppeteer to v21.2.0, with almost 100 new tests passing with the BiDi implementation (close to the 50% mark, see ) (bug)

ESMification status

  • ESMified status:
    • browser: 86%
    • toolkit: 99%
    • Total:  95.55%
  • #esmification on Matrix

Lint, Docs and Workflow

  • The ESLint rule react-hooks/exhaustive-deps will now raise errors rather than warnings. The previous warnings for this rule have been fixed.
  • Additionally, all the rules enabled in devtools/client/debugger will now all raise errors rather than warnings.
  • With some other improvements, we’re now down to about 13 ESLint warnings left in mozilla-central.
  • This all helps to ensure that we’re fixing issues where we intend for them to be fixed. It also means that using warnings as part of a roll-out mechanism will help highlight that the warnings are something that we need to fix.

Migration Improvements

  • Improvements importing when Firefox is installed as a Snap
  • We’re doing a small experiment to see if adding some adorable illustrations to the device migration wizard improves the number of people going through it.
    • The second step of the device migration wizard on SUMO. It instructs the user on how to configure Firefox so that it's syncing data via a Firefox Account. In the bottom right-hand corner of the wizard is an adorable cartoon fox peeking out from behind a set of boxes.
    • The third step of the device migration wizard on SUMO. It instructs the user on how to download Firefox on their new computer by following a special URL. In the bottom right-hand corner of the wizard is an adorable cartoon fox jumping out of a set of boxes.

      Fox in a box!

New Tab Page

Search and Navigation

Storybook/Reusable Components

One comment on “All Lights Green for 119 – These Weeks in Firefox: Issue 145”

Post a comment

  1. Ken Dawes wrote on

    In Firefox 119 the “Firefox Suggest” no longer shows the urls, only the site description.

    To me this is extremely short-sighted as the information shown could be spoofed on a malicious site.

    I understand the desire to dumb-down the interface in order not confuse naieve web users, but this is a security risk.

    For myself personally, as a web developer, it is very inconvenient as the same description might be used on different web pages under test… Makes things confusing!

    At the least it should be a selectable option in the FF settings.

    Is there a way to go back to seeing the urls via an about:config setting?

    Thank you.


Leave a Reply

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