1915722 - Support holdback for one-click Set to Default users default experience

Status: RESOLVED FIXED

(Firefox :: Messaging System, enhancement, P1)

Description

[Punam Dahiya [:pdahiya]]

Scope of this bug is to implement one-click set to default wins rolled out via Nimbus , default experience in Firefox Desktop

To track cumulative impact of H2 2024 experiments, we need to ensure holdback branch of long-term-holdback-2024-h2-velocity-desktop not see one-click-set to default experience as discussed here

https://experimenter.services.mozilla.com/nimbus/long-term-holdback-2024-h2-velocity-desktop/summary

Comment 1

[Meg Viar [:mviar]]

Hi Venetia - what are your thoughts about doing this before the end of the H2 holdback? We could potentially uplift this into Fx131 Beta.

Comment 2

[Vtay]

YES - if we can, we should.

Nicholas was also planning to implement it on the background updater as well

Comment 3

[Punam Dahiya [:pdahiya]]

Thanks @vtay. NI @nrishel to help link the implementing bug . I believe fix will be flipping prefs that powers feature variables "setDefaultGuidanceNotifications", "setDefaultBrowserUserChoiceRegRename".

As per timeline and scope of the fix, we can repurpose this bug to support holdback study by launching a shellService feature rollout with no-one-click that enrolls only users from holdback branch of LTH.

Comment 4

[Nick Rishel [:nrishel]]

Sounds like a plan, and yes changing the pref is sufficient for setDefaultBrowserUserChoiceRegRename and setDefaultGuidanceNotifications (the latter is already pref-ed on by default). I'll work on a patch in Bug 1916780.

Should we uplift to beta once landed?

Comment 5

[Punam Dahiya [:pdahiya]]

(In reply to Nick Rishel [:nrishel] from comment #4)

Sounds like a plan, and yes changing the pref is sufficient for setDefaultBrowserUserChoiceRegRename and setDefaultGuidanceNotifications (the latter is already pref-ed on by default). I'll work on a patch in Bug 1916780.

Should we uplift to beta once landed?

Yes beta uplift request once Bug 1916780 fix lands in Nightly and QA verified. setDefaultGuidanceNotifications pref-end on by default, my understanding we don't want to show guidance notification once setDefaultBrowserUserChoiceRegRename (one-click) is turned on , unless back-end functionality handles showing guidance notification only for users on devices where one-click set default fails.

Comment 6

[Nick Rishel [:nrishel]]

Guidance notification is only show when 1-click fails, so we can leave it on.

Comment 7

[Meg Viar [:mviar]]

We'll want to put an experiment recipe together for QA testing in beta.

Comment 9

[Meg Viar [:mviar]]

Here's the initial recipe created by @pdahiya to ensure no one click set to default rollout for users in the long-term holdback branch.

Comment 10

[Meg Viar [:mviar]]

This was launched on September 30th.