Merging upstream version 125.0.1.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 26 insertions, 0 deletions

diff --git a/devtools/server/actors/watcher/target-helpers/content-process-jsprocessactor-startup.js b/devtools/server/actors/watcher/target-helpers/content-process-jsprocessactor-startup.js
new file mode 100644
index 0000000000..1765bcc66c
--- /dev/null
+++ b/devtools/server/actors/watcher/target-helpers/content-process-jsprocessactor-startup.js
@@ -0,0 +1,26 @@
+/* This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
+
+"use strict";
+
+const { setTimeout } = ChromeUtils.importESModule(
+  "resource://gre/modules/Timer.sys.mjs"
+);
+
+/*
+   We can't spawn the JSProcessActor right away and have to spin the event loop.
+   Otherwise it isn't registered yet and isn't listening to observer service.
+   Could it be the reason why JSProcessActor aren't spawn via process actor option's child.observers notifications ??
+*/
+setTimeout(function () {
+  /*
+    This notification is registered in DevToolsServiceWorker JS process actor's options's `observers` attribute
+    and will force the JS Process actor to be instantiated in all processes.
+  */
+  Services.obs.notifyObservers(null, "init-devtools-content-process-actor");
+  /*
+    Instead of using observer service, we could also manually call some method of the actor:
+    ChromeUtils.domProcessChild.getActor("DevToolsProcess").observe(null, "foo");
+  */
+}, 0);