[stub installer] Allow the user to specify to launch/not launch Firefox post installation completion in the customized installation path

RESOLVED WONTFIX

Status

()

Firefox
Installer
--
enhancement
RESOLVED WONTFIX
6 years ago
5 years ago

People

(Reporter: jsmith, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [stub-])

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Heard this on a mozilla zine discussion - we should allow the user in a customized installation path to specify whether they would like Firefox to launch on the completion of the installation of Firefox. This user brought up concerns that they have no way to control it in the stub installer.
(Reporter)

Updated

6 years ago
Blocks: 322206
Whiteboard: [stub-]
This was a UX design decision so cc'ing some UX folk
(Reporter)

Updated

6 years ago
Severity: normal → enhancement
Comment on attachment 743990 [details]
screenshots of the current UI

Stephen, do you think this should be wontfix or can you think of a decent place to put another checkbox? Keep in mind that with some locales the text for setting as the default browser is more than one line. Thanks!
Attachment #743990 - Flags: ui-review?(shorlander)
Comment on attachment 743990 [details]
screenshots of the current UI

(In reply to Robert Strong [:rstrong] (do not email) from comment #3)
> Comment on attachment 743990 [details]
> screenshots of the current UI
> 
> Stephen, do you think this should be wontfix or can you think of a decent
> place to put another checkbox? Keep in mind that with some locales the text
> for setting as the default browser is more than one line. Thanks!

The design intent was to have a seamless experience from install to launch, it doesn't seem worth the overhead add an option to prevent launching Firefox even in the options panel.
Attachment #743990 - Flags: ui-review?(shorlander) → ui-review+
Resolving as wontfix
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.