860502 - Bring desktop Firefox' app.update.timerFirstInterval closer to the Fennec and Metro value

Status: NEW

(Firefox :: General, defect)

Description

[Jared Wein [:jaws] (please needinfo? me)]

Metro checks for an update 20 seconds after launch, Firefox for Android checks for update 30 seconds after launch. Firefox on desktop currently waits 10 minutes after startup to check for an update.

Users who launch and exit the browser in a short time interval will never start the update process.

We should lower app.update.timerFirstInterval to somewhere between 20s and 60s. http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/update/nsUpdateTimerManager.js is where the changes should be made.

After landing this, we may want to file a follow-up bug to build a hotfix that will set this pref on older versions of Firefox as well.

Comment 1

[Robert Strong (they/them - no direct email)]

(In reply to Jared Wein [:jaws] from comment #0)
>...
> We should lower app.update.timerFirstInterval to somewhere between 20s and
> 60s.
> http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/update/
> nsUpdateTimerManager.js is where the changes should be made.
The changes should be made to the Firefox preferences and not to nsUpdateTimerManager.js.
http://mxr.mozilla.org/mozilla-central/source/browser/app/profile/firefox.js

Comment 2

[Jared Wein [:jaws] (please needinfo? me)]

Bah, sorry, thanks for the correction.

Comment 3

[Robert Strong (they/them - no direct email)]

btw: you can also control the delay between notifying each consumer with the app.update.timerMinimumDelay preference with a minimum value of 60 (e.g. 60 seconds). It is currently 120 seconds.

Comment 4

[Robert Strong (they/them - no direct email)]

I have heard about data that shows that a large number of sessions are extremely short. Does that data also include if these same systems also have session length over time? It would be helpful with knowing the number of systems that would benefit from this change.