2002369 - Ship Interventions v147.8.0 out-of-band

Status: RESOLVED FIXED

(Web Compatibility :: Interventions, task)

Description

[Thomas Wisniewski [:twisniewski]]

We were just notified in bug 1996823 that fido.ca also has the same bug that rogers.com does, causing users to not be able to see their billing info. Fido's billing is just as important as Rogers, so we will ship another out-of-band release for it. The intervention has already been updated and landed on nightly in the mentioned bug. Likewise, it has uplift requests.

Comment 1

[Thomas Wisniewski [:twisniewski]]

Build was successful, here is the link to the dep-signed .xpi. I don't have a Fido account with which to test the actual bug, but I'll some basic testing to confirm that the intervention should work.

Comment 2

[Thomas Wisniewski [:twisniewski]]

I've tested the XPI on MacOS, Windows, and Linux unbranded builds, and it is working as far as I can confirm, not having a Fido account to do a full test:

• about:compat shows rogers.com and fido.ca as it ought to
• visiting the script URL https://www.fido.ca/bbapp/bbapi.js with the intervention active shows the string: let url = new URL(window.location.href); url.hash = link; window.location.href = url.href;
• disabling the intervention in about:compat and the reloading the script URL instead shows the un-altered string: window.location.href = link;.

Comment 3

[Ksenia Berezina [:ksenia]]

I've tested the dev signed xpi in unbranded builds on MacOS and Windows and confirm that it's working as expected following the steps from comment 2.

Comment 4

[Thomas Wisniewski [:twisniewski]]

Testing steps for the current release build:

1. Open a fresh profile, do not use your main profile for this.
2. Go to https://www.fido.ca/bbapp/bbapi.js and confirm that this line of code is present window.location.href = link;.
3. Open about:config, edit extensions.systemAddon.update.url, and set it to https://aus5.mozilla.org/update/3/SystemAddons/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/release-sysaddon/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
4. Open the Firefox DevTools. In the DevTools, open the Settings via the Three-Dot-Menu -> Settings. In there, enable the checkbox Enable browser chrome and add-on debugging toolboxes.
5. Open the Firefox Browser Console:

• on Linux and Windows, press Ctrl+Shift+J to open it
• on macOS, it's Cmd+Shift+J

8. In that new console, run ChromeUtils.importESModule("resource://gre/modules/AddonManager.sys.mjs", { global: "shared" }).AddonManagerPrivate.backgroundUpdateCheck();
9. You won't see any progress, the update happens in the background. Wait 30 seconds, just to make sure Firefox has enough time to download and apply all updates.
10. Head to about:support, search for "Web Compatibility Interventions", and check that the version number shows 147.8.20251126.183330
11. Go back to https://www.fido.ca/bbapp/bbapi.js and confirm that this line of code is present et url = new URL(window.location.href); url.hash = link; window.location.href = url.href; (instead of what it was in step 2).
12. Restart Firefox, keeping the same profile. Verify that the version number in about:support is still 147.6.20251121.151608, and that step 11 still holds true.

Comment 5

[Sky Schubert [:skyschub]]

JFTR, I gave this a few proper tests, too, and it seems to work for me.

Comment 6

[Ksenia Berezina [:ksenia]]

It works for me as well, tested on macOS and Windows.

Comment 7

[Thomas Wisniewski [:twisniewski]]

Our tests didn't uncover anything worrying, so I've pinged RelMan and RelEng to make the update go live, and it should now be live on release.

Comment 8

[Thomas Wisniewski [:twisniewski]]

Here's a (Mozilla-staff-only) telemetry query to keep an eye on the numbers. I'll keep this bug open for a day or two just in case.