Closed
Bug 1768608
Opened 2 years ago
Closed 2 years ago
[Rollout] New Firefox profiles are wrongly enrolled in the "TCP rollout, Phase III (Switch on by default for 25% EXISTING Release profiles)" rollout
Categories
(Firefox :: Messaging System, defect)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox100 | --- | unaffected |
firefox101 | --- | affected |
firefox102 | --- | unaffected |
People
(Reporter: mcoman, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
4.07 MB,
image/gif
|
Details |
[Affected versions]:
- Firefox Beta 101.0b4 - Build ID: 20220508185621
[Affected Platforms]:
- Windows 10 x64
- macOS 11.6.2
- Linux Mint 20.2 x64
[Prerequisites]:
- Have the update channel set to "release".
- Have the "user.js" file saved to your PC.
[Steps to reproduce]:
- Create a new Firefox profile but do not open it.
- Navigate to the previously created profile folder and paste the "user.js" from the prerequisites.
- Open the browser using the previously created profile and the
--first-startup
flag. - Navigate to the "about:studies" page and observe the displayed studies.
[Expected result]:
- The "TCP rollout, Phase III (Switch on by default for 25% EXISTING Release profiles)" study is NOT displayed.
[Actual result]:
- The "TCP rollout, Phase III (Switch on by default for 25% EXISTING Release profiles)" study is displayed on the "about:studies" page.
[Additional Notes]:
- This issue could be easily fixed by changing the rollout's targeting expression.
- Attached a screen recording of the issue.
Comment 1•2 years ago
|
||
Enrolling new users with Phase 3 is acceptable as Phase 2 will still be active attempting to enroll 100% new users, so if new users happen to get included in Phase 3 as well, that's fine.
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•