### Beta/Release Uplift Approval Request * **User impact if declined**: Users upgrading from older versions can see the upgrade spotlight if not enrolled into the 100% rollout. * **Is this code covered by automated tests?**: Yes * **Has the fix been verified in Nightly?**: No * **Needs manual test from QE?**: Yes * **If yes, steps to reproduce**: 1. new profile in old firefox (this sets `browser.startup.homepage_override.mstone` to something like "100.0") 2. open profile in new firefox 3. don't see upgrade spotlight (about:telemetry events will include `upgrade_dialog trigger reason disabled`) See more details in https://mozilla-hub.atlassian.net/browse/QA-2073 * **List of other uplifts needed**: none * **Risk to taking this patch**: Low * **Why is the change risky/not risky? (and alternatives if risky)**: QA already verified the rollout that effectively remotely sets the pref to `false` that this patch sets as default. * **String changes made/needed**: none * **Is Android affected?**: No
Bug 1851878 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
### Beta/Release Uplift Approval Request * **User impact if declined**: Users upgrading from older versions can see the upgrade spotlight if not enrolled into the [100% rollout](https://firefox.settings.services.mozilla.com/v1/buckets/main/collections/nimbus-desktop-experiments/records/upgrade-spotlight-rollout). * **Is this code covered by automated tests?**: Yes * **Has the fix been verified in Nightly?**: No * **Needs manual test from QE?**: Yes * **If yes, steps to reproduce**: 1. new profile in old firefox (this sets `browser.startup.homepage_override.mstone` to something like "100.0") 2. open profile in new firefox 3. don't see upgrade spotlight (about:telemetry events will include `upgrade_dialog trigger reason disabled`) See more details in https://mozilla-hub.atlassian.net/browse/QA-2073 * **List of other uplifts needed**: none * **Risk to taking this patch**: Low * **Why is the change risky/not risky? (and alternatives if risky)**: QA already verified the rollout that effectively remotely sets the pref to `false` that this patch sets as default. * **String changes made/needed**: none * **Is Android affected?**: No