[Experiment] The URL of the "VPN Moments" page from the "Treatment A" branch is wrongly set to "https://www.mozilla.org/en-GB/firefox/welcome/17a/ " instead of "https://www.mozilla.org/en/firefox/welcome/17a/ "
Categories
(Firefox :: Messaging System, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox121 | --- | verified |
People
(Reporter: mcoman, Assigned: hanna_a)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
4.27 MB,
image/gif
|
Details |
[Affected versions]:
- Firefox Release 121.0 - Build ID: 20231211174248
[Affected Platforms]:
- Windows 11 x64
- macOS 14.1
- Ubuntu 22.04 x64
[Prerequisites]:
- Have a Firefox profile with the following prefs in the "about:config" page:
nimbus.debug
pref set totrue
[Steps to reproduce]:
- Open the browser using the profile from the prerequisites.
- Navigate to "about:studies?optin_slug=moments-page-january-en&optin_branch=treatment-a&optin_collection=nimbus-preview" and restart the browser.
- Restart the browser again and observe the URL of the "VPN Moments" page.
[Expected result]:
- The "https://www.mozilla.org/en/firefox/welcome/17a/" is displayed.
[Actual result]:
- The "https://www.mozilla.org/en-GB/firefox/welcome/17a/" URL is displayed instead.
[Additional Notes]:
- Attached a screen recording of the issue.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Hi Marius! Thanks for filing this! I've updated the Treatment A branch in the recipe to use the correct link.
https://experimenter.services.mozilla.com/nimbus/moments-page-january-en/summary
Reporter | ||
Comment 2•2 years ago
|
||
Hi, Hanna! I have verified this issue and I can confirm that the URL of the "VPN Moments" page from the "Treatment A" branch is set to "https://www.mozilla.org/en/firefox/welcome/17a/". Verified using the latest Firefox Release 121.0 (Build ID: 20231211174248) installed on Windows 10 x64, macOS 14.1, and Ubuntu 22.04 x64.
Considering this I am marking this issue as Resolved - Fixed.
Reporter | ||
Comment 3•2 years ago
|
||
Based on my previous comment I am marking this issue as Verified - Fixed.
Description
•