Closed Bug 1694259 Opened 9 months ago Closed 5 months ago

Allow experimenting with 1-click default vs settings-dialog-ful flow

Categories

(Firefox :: Messaging System, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
91 Branch
Iteration:
91.2 - Jun 14 - Jun 27
Tracking Status
firefox91 --- fixed

People

(Reporter: Mardak, Assigned: Mardak)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Assuming we get some 1-click default browser ability perhaps with bug 1686286, it could be useful to have different actions that trigger the current settings dialog flow vs the 1-click flow to run an experiment measuring the differences.

Bug 1686343 landed with a waitForDefault action property as well as a combo PIN_AND_DEFAULT action that might need to change in some way if we have 1-click default functionality.

There might be some different interactions depending on the OS/version where at least recent windows 10 has the settings window/dialog while mac has a confirm/keep dialog.

Assignee: nobody → edilee
Severity: -- → S3
Priority: -- → P2
Depends on: 1703578

Similar to the approach in bug 1716884, we can expose a new NimbusFeatures.shellService.disable1ClickDefault to globally turn off the new behavior (and not just for about:welcome)

Status: NEW → ASSIGNED
Iteration: --- → 91.2 - Jun 14 - Jun 27
Priority: P2 → P1
See Also: → 1716884
Summary: Support welcome action for 1-click default vs settings-dialog-ful flow → Allow experimenting with 1-click default vs settings-dialog-ful flow

Switch pref check to NimbusFeature.getVariable with updated manifest for fallback pref.

Pushed by elee@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a375dcbc0e3f
Allow experimenting with 1-click default vs settings-dialog-ful flow r=andreio
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.