James from the Search team has been working on persisting the search term in the address bar after you do a search in it. It is now enabled on Nightly (see bug 1802564). Try it out, file bugs if you see them and let us know if you have any feedback.
Evan, one of the students working with us from CalState LA, landed a patch that adds a new Opera GX migrator
It’s currently disabled by default, but can be enabled by setting `browser.migrate.opera-gx.enabled` to true in about:config
For WebExtension authors: thanks to Alex Ochameau’s work in Bug 1410932, starting from Firefox 110 the errors raised from extension content script contexts will be logged in the related tab's web console
The screenshots component now respects the setting “Always ask you where to save files” when downloading screenshots. Set `screenshots.browser.component.enabled` to true to use this feature.
Gregory Pappas [:gregp]
Janvi Bajoria [:janvi01]
Jonas Jenwald [:Snuffleupagus]
🌟 Divyanshu Agrawal added a fix to not save values in fields with `autocomplete="one-time-code"`
🌟 Alan Shirk added Window Device Pixel Ratios to Graphics section of about:support
eliang made it possible to import data from OperaGX
steven w added a pref that opens the existing migration.xhtml document in a tab dialog box modal
🌟 Tyler Brinkman updated browser_tabCloseSpace to use overflowTabs() from BrowserTestUtils
Improvements to “all sites” optional permissions support in the about:addons permissions view - Bug 1778461
Use https by default in MV3 extension requests (enforced through the default MV3 extension CSP) - Security and privacy related restrictions Bug 1797086
Fixed a race between the extension manifest parsing and the extension startupCache population on extension startup - Bug 1791370
Thanks to Gregory Pappas for contributing:
implementation of the additional Omnibox onDeleteSuggestions API event Bug 1478095 - Implement `onDeleteSuggestion`
Exposing securityKeyLength in WebRequest SecurityInfo details Bug 1778473 - webRequest API: Add key length property to SecurityInfo object
As part of the ongoing work on the declarativeNetRequest API:
Restricted tabIds and excludedTabIds conditions to session rules - Bug 1804464
NOTE: declarativeNetRequest API is currently only enabled when the “extensions.dnr.enabled” pref is set to true, and only exposed to MV3 extensions.
Zac Svoboda improved the color of errors in the JSON viewer (bug)
We added scrollend event in the Debugger Event Breakpoints panel (bug)
Julian fixed a bug in webDriver where WebDriver:FindElements would not retrieve elements if the Firefox window was behind another app’s window (bug)
Henrik added support for serialization of Node objects (bug)
mochitest-media for now, browser-chrome in the near future, and hopefully xpcshell
Please consider migrating your components if you haven't already. Don't forget actors as well.
Total: 43.6% (up from 41.3%)
#esmification on Matrix
The students are now on exam / winter break and will hit the ground running again in late January.
Landed some changes in the category colors (more contrast, brown is now really brown, added a new magenta color).
Changed the treeherder performance regression template to output the before and after profile links for each regression (PR #7588)
[James] fixed context menu search terms to be displayed in the address bar for certain engines. Bug 1801602
[Drew] has refactored quick suggest telemetry tests. Bug 1804807
[Drew] did a bunch of refactors to support row buttons in all row types. Bug 1803873
[Dale] updated a few strings for the quick action buttons. Bug 1783153
[Dale] turned off quickactions on zero prefix by default. Bug 1803566
[Stephanie] fixed a bug so we can record search telemetry from different search engines who have the same underlying ad provider. Bug 1804739
[Mandy] fixed a bug where search engine order was modified. Bug 1800662
[Standard8] has refactored multiple files in search:
Our Storybook is online
Currently a manual deployment process, will look into automating it soon
Emilio updated stylesheet loading to be sync for our privileged shadow DOM, avoiding flashes of unstyled content (FOUC) Bug 1799200
mkaply, jhirsch, Neil, and Johnathan Sudiaman are this month’s triagers!
mstriemer, hjones, niklas and sclements will triage starting 2023
[Mossop]: No meeting 27th December
The Fx Desktop meeting seems to be sharing demos and updates across the broader engineering team. There've been really cool updates and demos in the past. There is a newsletter that gets sent out and the updates are posted in the Mozilla wiki. But I am worried and concerned that these updates are not getting to our users. There's been a recurring theme that our features are not discoverable. Example, searching tabs, bookmarks, and history using shortcuts on the address bar.
I'm wondering if there's a way to bring these updates we discuss in our Fx desktop meeting and make it more discoverable for our users? Sort of like a newsletter and tips for specifically our users, that they can always go back to and find it again. Maybe something like, an about:tips or about:new-features pages.
mconley: this hits the nightly blog after comms review, that's the most accessible spot currently (posting to fx-dev less so)
bit of a missing step here: 8 week gap between nightly and release. easy for nightly users to forget about stuff by the time there's a release-oriented comms cycle
jaws: where do we think our users are? how could we reach them? it depends
mconley: and do they want to be reached? There’s a fine balance, I think, between informing users and annoying users.
jaws: post more to a firefox nightly youtube channel? (except marketing-sensitive stuff)
mstriemer: Chrome updated for me recently and it has a really nice promo page on update with new features + promoting existing ones
mandy: screen share showing this page in chrome (with historical updates and latest updates)
mconley: I recall a What’s New feature in Firefox… a gift-box button. This was intentionally removed during Proton (2020).
amy: I used to work on the whats new page and they might be excited for some input / updates. Happy to help bridge connections there.
mconley: This does also feel like something related to Release Management… like, each release has an assigned Release Manager that is tracking each release. Feels like an overlap between Release Management and Marketing.
jaws: Engineering has a role here as well. We need to give Release Management and Marketing material to work with.
Amy Churchwell to find out who is responsible for updating the What’s New page, and what process they use to get their information.
DevTools team started to put updates in Release Notes (e.g. https://www.mozilla.org/en-US/firefox/107.0/releasenotes/ )
[jaws] relnote-firefox tracking flag! Use this (set to `?` and fill in the form) to alert our Release Managers / Marketing team about things that are relevant to a release.