| DefaultWindowsLaunchOnLogin.sys.mjs |
`browser-idle-startup` category entry point.
This deliberately runs off the startup-critical path. Waiting for Nimbus's
first Remote Settings fetch (see `waitForNimbusReady`) forces Remote
Settings initialization, which does significant disk I/O; doing that in a
pre-UI category regressed Talos startup file-I/O metrics (bug 2050775).
The Windows startup apps registry key only matters before the user reboots
Windows, so this has ample slack and is dispatched once the browser is
idle instead. There is some risk that users could see the option disabled
in preferences before we get to enable it, but this is unlikely to be a
significant problem and we've accepted that risk.
The category manager invokes this with a `jsGlobal` first argument, which
we ignore; the real work and its inputs live in `enableOnFirstRunIfNeeded`
so they can be driven directly from tests.
|
4317 |
- |
| moz.build |
|
392 |
- |
| tests |
|
|
- |