Allow experimenting with 1-click default vs settings-dialog-ful flow
Categories
(Firefox :: Messaging System, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox91 | --- | fixed |
People
(Reporter: Mardak, Assigned: Mardak)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
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.
|
Assignee | |
Comment 1•4 years ago
|
||
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.
|
||
Updated•4 years ago
|
|
|
Assignee | |
Comment 2•3 years ago
|
||
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)
|
|
Assignee | |
Comment 3•3 years ago
|
||
Switch pref check to NimbusFeature.getVariable with updated manifest for fallback pref.
|
||
Comment 5•3 years ago
|
||
| bugherder | ||
Description
•