Skip to content

Should we reflect the actual channel in about:debugging?

One of the things we inherited from previous/Tor Browser implementations of the branding commit is that we used to replace the various inspector logo.

However, we now do a much simpler thing on Tor Browser, and we could adapt it also to Mullvad Browser, that is:

The diff
diff --git a/devtools/client/aboutdebugging/src/actions/runtimes.js b/devtools/client/aboutdebugging/src/actions/runtimes.js
index 346758c17910..c270d88c510d 100644
--- a/devtools/client/aboutdebugging/src/actions/runtimes.js
+++ b/devtools/client/aboutdebugging/src/actions/runtimes.js
@@ -60,25 +60,7 @@ const CONNECTION_TIMING_OUT_DELAY = 3000;
 const CONNECTION_CANCEL_DELAY = 13000;
 
 async function getRuntimeIcon(runtime, channel) {
-  if (runtime.isFenix) {
-    switch (channel) {
-      case "release":
-      case "beta":
-        return "chrome://devtools/skin/images/aboutdebugging-fenix.svg";
-      case "aurora":
-      default:
-        return "chrome://devtools/skin/images/aboutdebugging-fenix-nightly.svg";
-    }
-  }
-
-  // Use the release build skin for devtools within Tor Browser alpha releases.
-  if (channel === "alpha") {
-    return "chrome://devtools/skin/images/aboutdebugging-firefox-release.svg";
-  }
-
-  return channel === "release" || channel === "beta" || channel === "aurora"
-    ? `chrome://devtools/skin/images/aboutdebugging-firefox-${channel}.svg`
-    : "chrome://devtools/skin/images/aboutdebugging-firefox-nightly.svg";
+  return "chrome://branding/content/about-logo.svg";
 }
 
 function onRemoteDevToolsClientClosed() {
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information