Bug 1454895 - allow toolbox to call getProcess when debugging a local tab. r=jryans draft
authorBelén Albeza <balbeza@mozilla.com>
Thu, 19 Apr 2018 17:56:02 +0200
changeset 785085 f0926cbe2390
parent 785067 0c4b59df5b3e
child 787701 61ba32205824
child 787702 f934e9999b9a
child 787724 a2bbd4b5ff56
child 787851 6e21da1f80c5
child 787852 ee6a7153b376
child 788310 e2295c3bc0d6
push id107130
push userbalbeza@mozilla.com
push dateThu, 19 Apr 2018 16:27:29 +0000
reviewersjryans
bugs1454895
milestone61.0a1
Bug 1454895 - allow toolbox to call getProcess when debugging a local tab. r=jryans MozReview-Commit-ID: 19bhk3Wn9qE
devtools/client/framework/target.js
--- a/devtools/client/framework/target.js
+++ b/devtools/client/framework/target.js
@@ -408,16 +408,18 @@ TabTarget.prototype = {
 
       // When connecting to a local tab, we only need the root actor.
       // Then we are going to call DebuggerServer.connectToFrame and talk
       // directly with actors living in the child process.
       // We also need browser actors for actor registry which enabled addons
       // to register custom actors.
       // TODO: the comment and implementation are out of sync here. See Bug 1420134.
       DebuggerServer.registerAllActors();
+      // Enable being able to get child process actors
+      DebuggerServer.allowChromeProcess = true;
 
       this._client = new DebuggerClient(DebuggerServer.connectPipe());
       // A local TabTarget will never perform chrome debugging.
       this._chrome = false;
     } else if (this._form.isWebExtension &&
           this.client.mainRoot.traits.webExtensionAddonConnect) {
       // The addonActor form is related to a WebExtensionParentActor instance,
       // which isn't a tab actor on its own, it is an actor living in the parent process