From 40a355a42d4a9444dc753c04c6608dade2f06a23 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Fri, 19 Apr 2024 03:13:27 +0200 Subject: Adding upstream version 125.0.1. Signed-off-by: Daniel Baumann --- toolkit/mozapps/update/docs/BackgroundUpdates.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'toolkit/mozapps/update/docs') diff --git a/toolkit/mozapps/update/docs/BackgroundUpdates.rst b/toolkit/mozapps/update/docs/BackgroundUpdates.rst index 7f97f58c74..d8a154cb39 100644 --- a/toolkit/mozapps/update/docs/BackgroundUpdates.rst +++ b/toolkit/mozapps/update/docs/BackgroundUpdates.rst @@ -65,7 +65,7 @@ observe and control these settings. But there are some other pieces of state which absolutely must come from a profile, such as the telemetry client ID and logging level settings (see -`BackgroundTasksUtils.jsm `__). +`BackgroundTasksUtils.sys.mjs `__). This means that, in addition to our per-installation prefs, we also need to be able to identify and load a profile. To do that, we leverage `the profile @@ -137,7 +137,7 @@ API `__. For platform-specific scheduling details, see the -`TaskScheduler.jsm `__ +`TaskScheduler.sys.mjs `__ module. These background tasks are scheduled per OS user and run with that user’s @@ -177,7 +177,7 @@ visible to users: see `bug 1775132 After setting up this profile and reading all the configuration we need into it, the regular -`UpdateService.jsm `__ +`UpdateService.sys.mjs `__ check process is initiated. To the greatest extent possible, this process is identical to what happens during any regular browsing session. -- cgit v1.2.3