Open
Bug 1763113
Opened 3 years ago
Users set preferences are converted to default preferences if the user is enrolled in a rollout that sets the same value
Categories
(Firefox :: Normandy Client, defect)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox99 | --- | affected |
People
(Reporter: mheres, Unassigned)
Details
Attachments
(1 file)
|
5.35 MB,
video/mp4
|
Details |
[Note]:
- This interferes with user choice in the case of a rollback. The user set value which was converted to default value is reset to the build default in a rollback.
[Affected Versions]:
- Firefox Release 99.0 (Build ID: 20220330194208)
[Affected Platforms]:
- Windows 10
- macOS 12.3
- Linux Mint 20.2
[Prerequisites]:
- Have Firefox open.
- Have a Stage Rollout set (this rollout modifies “javascript.options.wasm_caching” to “false”).
- Have a user.js file saved on your computer to enroll in the rollout.
[Steps to reproduce]:
- Go to “about:config” and modify “javascript.options.wasm_caching” to “false”.
- Restart the browser.
- Copy the user.js file to the profile folder and restart the browser.
- Restart the browser.
- Go to “about:config” and observe the “javascript.options.wasm_caching” preference.
[Expected result]:
- The preference remains as a user set value even after enrollment in the rollout (i.e. is represented with a bold font).
[Actual result]:
- The user set preference is converted to a default preference after enrollment in a rollout which sets the preference to the same value (i.e. is represented with an unbolded font).
[Additional Notes]:
- Attached is a recording of the issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•