2001648 - Ship Interventions v147.6.0 out-of-band

Status: RESOLVED FIXED

(Web Compatibility :: Interventions, task)

Description

[Dennis Schubert [:denschub]]

Yet another Train Hop Friday™! This time, the release driver is bug 1950282, which is somewhat time critical because there's a F1 race this weekend. Intervention is already built, and shipping in Nightly, in the mentioned bug. Likewise, it has uplift requests.

Comment 1

[Dennis Schubert [:denschub]]

I did test that the F1TV frontpage loads on Nightly. We have internal capacity to do more thorough testing with an actual account, but I'll get this started on ship-it so we can do the internal testing on the staging channel.

Comment 2

[Dennis Schubert [:denschub]]

Build was successful, here is the link to the dep-signed .xpi. Because our timing can't possibly be any worse on a Friday after 4pm in CET, I'll run some testing myself before asking RelEng.

Comment 3

[Ksenia Berezina [:ksenia]]

I have tested the dep-signed xpi in an unbradned release build on macOS and Windows and confirm the intervention works as expected on the front page of https://f1tv.formula1.com/. Added my sign off on ShipIt.

Comment 4

[Dennis Schubert [:denschub]]

I also ran some testing in the same unbranded macOS and Windows builds, as well as a test in an Ubuntu VM because I did notice we're shipping an extra content script to Linux and I didn't want to leave that untested. Second sign-off on Ship-It was myself.

I also did a quick testing of the now-release-signed .xpi we got out of the shipping phase. Install and loading the F1 TV frontpage in a regular release build works for me on macOS, Windows, and Linux.

Ben, can you take the webcompat-147.6.0-build1 release from Ship-It and get that into the release-sysaddon channel - for Desktop on all platforms, targeting Release 145.* and Beta 146.*, please? We don't need a rule for Nightly 147, since the new intervention is already shipping in today's Nightly.

When it's on the staging channel, I'll provide release testing instructions here so that we can run our update testing again, and Yarik can test this as well and see if his account works.

Comment 5

[[e-mail] (:bhearsum)]

(In reply to Dennis Schubert [:denschub] from comment #4)

I also ran some testing in the same unbranded macOS and Windows builds, as well as a test in an Ubuntu VM because I did notice we're shipping an extra content script to Linux and I didn't want to leave that untested. Second sign-off on Ship-It was myself.

I also did a quick testing of the now-release-signed .xpi we got out of the shipping phase. Install and loading the F1 TV frontpage in a regular release build works for me on macOS, Windows, and Linux.

Ben, can you take the webcompat-147.6.0-build1 release from Ship-It and get that into the release-sysaddon channel - for Desktop on all platforms, targeting Release 145.* and Beta 146.*, please? We don't need a rule for Nightly 147, since the new intervention is already shipping in today's Nightly.

When it's on the staging channel, I'll provide release testing instructions here so that we can run our update testing again, and Yarik can test this as well and see if his account works.

webcompat 147.6.0 is live on release-sysaddon and beta-sysaddon

Comment 6

[Dennis Schubert [:denschub]]

Testing steps for the current release build. For testing in beta, replace release-sysaddon with beta-sysaddon, everything else remains.

1. Open a fresh profile, do not use your main profile for this.
2. Go to https://f1tv.formula1.com and verify that you see the "unsupported browser" banner.
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
6. In that new console, run ChromeUtils.importESModule("resource://gre/modules/AddonManager.sys.mjs", { global: "shared" }).AddonManagerPrivate.backgroundUpdateCheck();
7. 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.
8. Head to about:support, search for "Web Compatibility Interventions", and check that the version number shows 147.6.20251121.151608
9. Verify that the "unsupported browser" banner on https://f1tv.formula1.com is no longer there. Please also log into your account and check that video playback etc works as expected.
10. Restart Firefox, keeping the same profile. Verify that the version number in about:support is still 147.6.20251121.151608, and that f1tv still works.

Comment 7

[Yarik Kurmyza [:yarik] (he/him) (UTC+1)]

Tested on Mac - works perfectly

Comment 8

[Ksenia Berezina [:ksenia]]

Also confirming that it works as expected and "unsupported browser" banner is gone following above steps on macOS and Windows for release build.

Comment 9

[Dennis Schubert [:denschub]]

I also ran tests in real release builds on Windows, macOS, and Ubuntu. Since 146b6 is shipping now, we luckily don't have to worry about shipping this OOB update to Beta, those users can just update their builds.

Comment 10

[Dennis Schubert [:denschub]]

Our tests are all very green - I've pinged RelMan and RelEng to make the update go live.

Comment 11

[[e-mail] (:bhearsum)]

Updates are live on release now.

Comment 12

[Dennis Schubert [:denschub]]

Prepared a telemetry query to keep an eye on the numbers (Mozilla-staff-only link). I'll keep this bug open until Monday or so just to confirm, but this should be effectively resolved.