Closed Bug 1833520 Opened 1 year ago Closed 1 year ago

Allow setting new migration prefs from about:welcome

Categories

(Firefox :: Messaging System, enhancement, P1)

enhancement

Tracking

()

VERIFIED FIXED
115 Branch
Iteration:
115.1 - May 8 - May 19
Tracking Status
firefox114 + verified
firefox115 --- verified

People

(Reporter: Mardak, Assigned: Mardak)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

[Tracking Requested - why for this release]: Experiment targeting Fx114 might need the ability to set certain prefs from about:welcome.

In order to support about:welcome experiments with treatment branches that use the new import experience without relying on Nimbus multifeature capability from bug 1726190 (to configure aboutwelcome screens and migrationWizard prefs still relying on server-side changes), we'll need to be able to configure the migration wizard to show the desired experience. E.g.,

             {
               id: "checkbox-2",
               defaultValue: true,
               label: {
                 string_id: "mr2022-onboarding-easy-setup-import-checkbox-label",
               },
               action: {
+                type: "MULTI_ACTION",
+                data: {
+                  actions: [
+                    {
+                      type: "SET_PREF",
+                      data: {
+                        pref: {
+                          name:
+                            "browser.migrate.content-modal.about-welcome-behavior",
+                          value: "standalone",
+                        },
+                      },
+                    },
+                    {
                       type: "SHOW_MIGRATION_WIZARD",
                       data: {},
+                    },
+                  ],
+                },
               },
             },
Summary: Allow setting new migration prefs → Allow setting new migration prefs from about:welcome

Might want to clear prefs in case users go back a screen and uncheck as supported in bug 1823777. Although we might not have a good way to clean up pref changes for those who do enroll into the branch and does the action to set prefs.

See Also: → 1823777

Include prefs needed to enable content modal as experimented in 113.

Pushed by elee@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cfed793865f8
Allow setting new migration prefs from about:welcome r=pdahiya

Comment on attachment 9334466 [details]
Bug 1833520 - Allow setting new migration prefs from about:welcome r?pdahiya,mconley

Beta/Release Uplift Approval Request

  • User impact if declined: Users might not see the expected experiment experience
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes comment 6
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce: See Test Plan https://phabricator.services.mozilla.com/D178256
  • List of other uplifts needed: none
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Doesn't change default behavior and might only be used in 114 experiment that would go through experiment QA before launching
  • String changes made/needed: none
  • Is Android affected?: No
Attachment #9334466 - Flags: approval-mozilla-beta?
Flags: qe-verify+
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
QA Whiteboard: [qa-triaged]

I‘ve verified this enhancement using the latest Firefox Nightly 115.0a1 (Build ID: 20230517153544) on Windows 10 x64, macOS 11.7.1, and Ubuntu 22.04 x64.

  • After following the testing steps from this Test Plan, I confirm the following:
    • The "content-modal" prefs are set (enabled=true, behavior=standalone, import-all=true) after clicking the primary button while the “Import from previous browser” checkbox is checked.
    • The standalone migrate experience is shown when clicking the primary button while the “Import from previous browser” checkbox is checked.
    • The "content-modal" prefs are set (enabled=true, behavior=default, import-all=false) after clicking the primary button while the “Import from previous browser” checkbox is unchecked.
    • In Nightly the default pref value for enabled is true, and in Beta/Release is false.
Status: RESOLVED → VERIFIED

Comment on attachment 9334466 [details]
Bug 1833520 - Allow setting new migration prefs from about:welcome r?pdahiya,mconley

Approved for 114.0b6.

Attachment #9334466 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

I‘ve verified this enhancement using Firefox Beta 114.0b6 (Build ID: 20230518180043) on Windows 10 x64, macOS 11.7.1, and Ubuntu 22.04 x64.

  • After following the testing steps from this Test Plan, I confirm the following:
    • The "content-modal" prefs are set (enabled=true, behavior=standalone, import-all=true) after clicking the primary button while the “Import from previous browser” checkbox is checked.
    • The standalone migrate experience is shown when clicking the primary button while the “Import from previous browser” checkbox is checked.
    • The "content-modal" prefs are set (enabled=false, behavior=default, import-all=false) after clicking the primary button while the “Import from previous browser” checkbox is unchecked.
    • In Nightly the default pref value for enabled is true, and in Beta/Release is false.
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: