Deploy February 24, 2026 (#5856)

Changes:

[Markus Stange] Move transparent fill check to a less expensive place.
(#5826)
[fatadel] refine docs for ctrl key (#5831)
[Nazım Can Altınova] Update the team members inside CONTRIBUTING.md
(#5829)
[fatadel] Provide correct instructions on the home page for Firefox for
Android (Fenix) (#5816)
[Markus Stange] Make markers darker (#5839)
[Markus Stange] Directly use photon-colors (#5821)
[Markus Stange] Migrate to esbuild (#5589)
[Markus Stange] Use data URLs for SVG files. (#5845)
[Markus Stange] Tweak dark mode colors some more. (#5846)
[Nazım Can Altınova] Make the source table non-optional in the gecko
profile format (#5842)
[fatadel] fix foreground color of the button on error page (#5849)
[Nazım Can Altınova] 🔃 Sync: l10n -> main (February 24, 2026) (#5855)

And special thanks to our localizers:

de: Michael Köhler
el: Jim Spentzos
en-GB: Ian Neal
es-CL: ravmn
fr: Théo Chevalier
fy-NL: Fjoerfoks
ia: Melo46
it: Francesco Lodolo [:flod]
nl: Mark Heijl
ru: Valery Ledovskoy
sv-SE: Andreas Pettersson
zh-TW: Pin-guang Chen

Author: canova

.gitignore

@@ -4,6 +4,7 @@ node_modules/
 .DS_Store
 dist/
 public_html/
+build-meta/
 flow-coverage
 coverage
 .eslintcache

CONTRIBUTING.md

@@ -6,21 +6,21 @@ First off, thanks for taking the time to contribute to Mozilla and the Firefox P
 
 This project is made up of a cross section of different parts of Mozilla, including people from Firefox DevTools and from Firefox's platform team who are working on the C++ and Rust internals of Firefox. Some core Mozillians on the team are:
 
-| -                                                                                          | Name               | Github Handle                                                  | Position                               |
-| ------------------------------------------------------------------------------------------ | ------------------ | -------------------------------------------------------------- | -------------------------------------- |
-| ![][julienw]                                                                               | Julien Wajsberg    | [@julienw](https://github.com/julienw)                         | Firefox Frontend Engineer              |
-| ![][canova]                                                                                | Nazim Can Altinova | [@canova](https://github.com/canova)                           | Firefox Platform and Frontend Engineer |
-| <img src="https://avatars.githubusercontent.com/mstange?size=56" width="56" height="56" /> | Markus Stange      | [@mstange](https://github.com/mstange)                         | Firefox Platform Engineer              |
-| ![][AdamBrouwersHarries]                                                                   | Adam Harries       | [@AdamBrouwersHarries](https://github.com/AdamBrouwersHarries) | Firefox Platform Engineer              |
-| ![][davehunt]                                                                              | Dave Hunt          | [@davehunt](https://github.com/davehunt)                       | Firefox Profiler Team Manager          |
+| -                                                                                          | Name               | Github Handle                                    | Position                               |
+| ------------------------------------------------------------------------------------------ | ------------------ | ------------------------------------------------ | -------------------------------------- |
+| ![][fatadel]                                                                               | Adel Fatkhutdinov  | [@fatadel](https://github.com/fatadel)           | Firefox Frontend Engineer              |
+| ![][carverdamien]                                                                          | Damien Carver      | [@carverdamien](https://github.com/carverdamien) | Firefox Platform Engineer              |
+| ![][canova]                                                                                | Nazim Can Altinova | [@canova](https://github.com/canova)             | Firefox Platform and Frontend Engineer |
+| <img src="https://avatars.githubusercontent.com/mstange?size=56" width="56" height="56" /> | Markus Stange      | [@mstange](https://github.com/mstange)           | Firefox Platform Engineer              |
+| ![][davehunt]                                                                              | Dave Hunt          | [@davehunt](https://github.com/davehunt)         | Firefox Profiler Team Manager          |
 
 <!-- mstange's image is differently inserted because its size isn't properly controlled by the size parameter, strangely -->
 
 [mstange]: https://avatars.githubusercontent.com/mstange?size=56
-[julienw]: https://avatars.githubusercontent.com/julienw?size=56
+[fatadel]: https://avatars.githubusercontent.com/fatadel?size=56
+[carverdamien]: https://avatars.githubusercontent.com/carverdamien?size=56
 [canova]: https://avatars.githubusercontent.com/canova?size=56
 [davehunt]: https://avatars.githubusercontent.com/davehunt?size=56
-[AdamBrouwersHarries]: https://avatars.githubusercontent.com/AdamBrouwersHarries?size=56
 
 We're friendly and we're on the [Mozilla Matrix instance](https://chat.mozilla.org/) in the [_Firefox Profiler_ channel (_#profiler:mozilla.org_)](https://chat.mozilla.org/#/room/#profiler:mozilla.org). Come chat with us if you have any questions about the project.
 
@@ -37,30 +37,21 @@ To get started clone the repo and get the web application started.
 1.  Run `git clone [email protected]:firefox-devtools/profiler.git`
 2.  Run `cd profiler`
 3.  Run `yarn install`, this will install all of the dependencies.
-4.  Run `yarn start`, this will start up the webpack server.
+4.  Run `yarn start`, this will start up the development server.
 5.  Point your browser to [http://localhost:4242](http://localhost:4242).
 6.  If port `4242` is taken, then you can run the web app on a different port: `FX_PROFILER_PORT=1234 yarn start`
 
-Other [webpack](https://webpack.js.org/configuration/) and [webpack server](https://webpack.js.org/configuration/dev-server/) options can be set in a `webpack.local-config.js` file at the repo root. For example, if you want to disable caching and the server to automatically open the home page, put in there the following code:
-
-```js
-module.exports = function (config, serverConfig) {
-  config.cache = false;
-  serverConfig.open = true;
-};
-```
-
 This project uses [TypeScript](https://www.typescriptlang.org/).
 
 ## Using GitHub Codespaces
 
 Alternatively, you can also develop the Firefox Profiler online in a pre-configured development environment using [GitHub Codespaces](https://github.com/features/codespaces).
 
-GitHub Codespaces will automatically install all dependencies, start the webpack server for you, and forward port 4242 so you can access the web app. Please look at our [GitHub Codespaces documentation](./docs-developer/codespaces.md) for more information.
+GitHub Codespaces will automatically install all dependencies, start the development server for you, and forward port 4242 so you can access the web app. Please look at our [GitHub Codespaces documentation](./docs-developer/codespaces.md) for more information.
 
 ## Loading in profiles for development
 
-The web app doesn't include any performance profiles by default, so you'll need to load some in. Make sure the local Webpack web server is running, and then try one of the following:
+The web app doesn't include any performance profiles by default, so you'll need to load some in. Make sure the local development server is running, and then try one of the following:
 
 #### 1. Record a profile:
 

__mocks__/gecko-profiler-demangle.ts

@@ -1,14 +1,14 @@
 // This module replaces the wasm-pack generated module 'gecko-profiler-demangle'
 // in our tests.
 // The reason for this replacement is the fact that wasm-pack (or rather,
-// wasm-bindgen), when targeting the browser + webpack, generates an ES6 module
+// wasm-bindgen), when targeting the browser + bundlers, generates an ES6 module
 // that node cannot deal with. Most importantly, it uses the syntax
 // "import * as wasm from './gecko_profiler_demangle_bg';" in order to load
-// the wasm module, which is currently only supported by webpack.
+// the wasm module, which is currently only supported by bundlers.
 // The long-term path to make this work correctly is to wait for node to
 // support ES6 modules (and WASM as ES6 modules) natively [1]. It's possible
 // that in the medium term, wasm-bindgen will get support for outputting JS
-// files which work in both webpack and in node natively [2].
+// files which work in both bundlers and in node natively [2].
 // [1] https://medium.com/@giltayar/native-es-modules-in-nodejs-status-and-future-directions-part-i-ee5ea3001f71
 // [2] https://github.com/rustwasm/wasm-bindgen/issues/233
 

docs-developer/CHANGELOG-formats.md

@@ -128,13 +128,17 @@ We've also cleaned up the ResourceTable format:
 
 ### Older Versions
 
-Older versions are not documented in this changelog but can be found in [processed-profile-versioning.jt](../src/profile-logic/processed-profile-versioning.ts).
+Older versions are not documented in this changelog but can be found in [processed-profile-versioning.ts](../src/profile-logic/processed-profile-versioning.ts).
 
 ## Gecko profile format
 
+### Version 33
+
+The `sources` field in the Gecko profile format is now non-optional. An upgrader was added that creates an empty `SourceTable` for profiles that don't have one.
+
 ### Version 32
 
-`frameTable` `location` string field was changed to include an optional `sourceIndex` at the end of the string inside brackets for JS sources. For example, new JS frames look like this: `functionName (http://script.url/:1234:1234)[1234]` with the last number being its `sourceIndex`. This index references entries in the shared `SourceTable` in `profile.sources` (added in in the same version) which centralizes all source file information.
+`frameTable` `location` string field was changed to include an optional `sourceIndex` at the end of the string inside brackets for JS sources. For example, new JS frames look like this: `functionName (http://script.url/:1234:1234)[1234]` with the last number being its `sourceIndex`. This index references entries in the shared `SourceTable` in `profile.sources` (added in the same version) which centralizes all source file information.
 
 ### Version 31
 
@@ -163,4 +167,4 @@ The `searchable` property is implemented in the marker schema. Previously all th
 
 ### Older Versions
 
-Older versions are not documented in this changelog but can be found in [gecko-profile-versioning.jt](../src/profile-logic/gecko-profile-versioning.ts).
+Older versions are not documented in this changelog but can be found in [gecko-profile-versioning.ts](../src/profile-logic/gecko-profile-versioning.ts).

docs-user/guide-ui-tour-panels.md

@@ -6,7 +6,9 @@ Get to know Firefox Profiler UI a bit better with a tour that highlights various
 
 ![A screenshot highlighting the panels on the lower half of the UI.](images/ui-tour-panels.png)
 
-The timeline lists multiple threads, while the panels provide an analysis of the currently selected thread in the timeline. The panel only uses one thread at a time by default. However it's possible to merge several threads together by using the `Ctrl` keyboard key when clicking a thread.
+The timeline lists multiple threads, while the panels provide an analysis of the currently selected thread in the timeline.
+The panel only uses one thread at a time by default.
+However, it's possible to merge several threads together by using the `⌘`/`Ctrl` keyboard key when clicking a thread.
 
 ## The Call Tree
 

locales/de/app.ftl

@@ -333,6 +333,13 @@ Home--record-instructions =
 Home--instructions-content =
     Das Aufzeichnen von Leistungsprofilen benötigt <a>{ -firefox-brand-name }</a>.
     Vorhandene Profile können jedoch in jedem modernen Browser angezeigt werden.
+Home--fenix-instructions-directly =
+    Ein Leistungsprofil von { -firefox-android-brand-name } kann direkt auf diesem Gerät erstellt werden.
+    Weitere Informationen finden Sie unter <a>Leistungsprofile von { -firefox-android-brand-name } direkt auf dem Gerät</a>.
+Home--fenix-instructions-remotely =
+    Sie können auch Leistungsprofile für { -firefox-android-brand-name } per Fernzugriff von
+    { -firefox-brand-name } für Desktop erstellen. Weitere Informationen finden Sie in der Dokumentation
+    <a>Leistungsprofile von { -firefox-android-brand-name } per Fernzugriff</a>.
 Home--record-instructions-start-stop = Profilerstellung stoppen und starten
 Home--record-instructions-capture-load = Profil aufzeichnen und laden
 Home--profiler-motto = Zeichnen Sie ein Leistungsprofil auf. Analysieren Sie es. Teilen Sie es. Machen Sie das Web schneller.