commit 8f159297b4120b7494d1fec3c9375777940f4277
parent ce7f1a1ff5286e4a54b12529819c76c79e14b4f6
Author: Pier Angelo Vendrame <pierov@torproject.org>
Date: Tue, 24 Feb 2026 09:58:17 +0100
fixup! BB 4234: Use the Firefox Update Process for Base Browser.
BB 44668: Allow to replace detailsURL with unsupportedURL.
We perform unsupported detection locally, rather than with a
server-side logic, that is what Mozilla does.
So, we send unsupported users to the details of the actual update,
rather than sending them to a page with details of why they are
unsupported.
With this patch, we can distinguish those cases, and send user to a
more appropriate page when needed.
Diffstat:
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/toolkit/.eslintrc.mjs b/toolkit/.eslintrc.mjs
@@ -7,7 +7,7 @@ export default [
rules: {
// XXX Bug 1326071 - This should be reduced down - probably to 20 or to
// be removed & synced with the mozilla/recommended value.
- complexity: ["error", 47],
+ complexity: ["error", 49],
},
},
];
diff --git a/toolkit/mozapps/update/UpdateService.sys.mjs b/toolkit/mozapps/update/UpdateService.sys.mjs
@@ -2491,6 +2491,13 @@ class Update {
this.elevationFailure = false;
}
+ if (this.unsupported && update.hasAttribute("unsupportedURL")) {
+ // Override the detailsURL with the dedicated link for the EOL.
+ // Otherwise it will point to the release blog post for the wrong version.
+ // See tor-browser#44668.
+ this.detailsURL = update.getAttribute("unsupportedURL");
+ }
+
if (!this.detailsURL) {
try {
// Try using a default details URL supplied by the distribution