1745930 - The "VPN Moments Page 13" is wrongly triggered even if the "Firefox Multi-Account Containers" extension is installed

Status: VERIFIED FIXED

(Firefox :: Messaging System, defect)

Description

[Marius Coman [:mcoman], Ecosystem QA, PTO until 20th of October, for any testing requests ping :poiegas]

Attachment: rec of the issue.gif

[Affected versions]:

• Firefox Release 95.0 - Build ID: 20211129150630

[Affected Platforms]:

• Windows 10 x64
• macOS 11.6.1

[Prerequisites]:

• Have the latest Firefox Release 95.0 en-US locale installed.
• Have a Firefox profile with the latest version of the "Firefox Multi-Account Containers" (8.0.3) installed.
• Have the "browser.search.region" pref set to "US" in the "about:config" page.
• Have the latest version of the "Remote Settings Devtools" add-on installed from here.

[Steps to reproduce]:

1. Open the browser with the profile from the prerequisites.
2. Click the "Remote Settings Devtools" toolbar button from the right part of the "Address Bar".
3. Change the environment to "Stage" and restart the browser.
4. Restart the browser again and observe the behavior.

[Expected result]:

• The "VPN Moments Page 12" is triggered.

[Actual result]:

• The "VPN Moments Page 13" is triggered instead.

[Notes]:

• Also, I've checked the targeting of the "VPN Moments Page 12" in the "AS Router Admin" page and it appears that is valid but the "VPN Moments Page 13" is triggered first.
• Attached a screen recording of the issue.

Comment 1

[Emily McMinn :emcminn]

Thanks Marius! I can fix this by adding some exclusionary targeting to moments page 13.

Comment 2

[Emily McMinn :emcminn]

Closing this as resolved since the page launched successfully yesterday.

Comment 3

[Robert Martin [:romartin], Ecosystem QA]

I have verified that this issue is no longer reproducible by following the steps provided in the description using Firefox 95.0.2 en-US (Build ID: 20211218203254) on Windows 10 x64, macOS 11.6, and Ubuntu Linux 20.04 x64.

However, I've uncovered a scenario that still reproduces the issue and I've logged it here.

@Emily, can you please weigh in on this?

Comment 4

[Emily McMinn :emcminn]

This may be due to when during startup the moments page targeting is checked; the check is likely happening before the user installs the addon. This particular message should no longer be live (ended on the 31st) so it shouldn't be an immediate concern, however it'll likely affect any future messages that rely on a particular addon. We're going to repurpose the bug to look at this in a more general sense.