Remove the #ifndef RELEASE_BUILD guards around skipping the default-browser dialog on first-run

NEW
Unassigned

Status

()

3 years ago
3 years ago

People

(Reporter: jaws, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox43 affected, firefox44 affected, firefox45 affected)

Details

Bug 1191250 is now on beta and the deferring of the dialog is not working because when we landed it we included compiler guards to only build this change on non-release builds.

Are we OK with removing this guard now? Or should we keep it for another release?
Flags: needinfo?(philipp)
Flags: needinfo?(dolske)
Did anyone have a look at the data from the releases that this has been enabled on yet?
Is there any change vs. previous versions in the following metrics?
- % of users having Fx as their default
- usage hours
- ADI
- MAU

Also, I'm blanking on whether we had that enabled only for Windows 10 or for all platforms.

Generally, I would err on the side of removing the guard, because the experience is better, unless the numbers look terrible.
Flags: needinfo?(philipp)
I've not looked at any data, but I think we do need some indication it's not a regression before removing the prefix, to avoid a repeat of bug 1086958 / drop in user retention.

Also, I think we should probably so something about the UI for this in about:preferences... It's a little weird to have a prominent "Always check if Firefox is your default browser" setting, when for some people it's only active for 3 launches of their browser (we skip asking the first launch, try 3 times, and then skip asking again). Not sure what the best thing to do is -- we could just uncheck the pref, but we also probably want to differentiate between "user explicitly does not want Firefox to prompt again" and "user just didn't bother doing it when we asked".
Flags: needinfo?(dolske)
You need to log in before you can comment on or make changes to this bug.