From 21f04c4d9fe18a7e4508c11844811431fb920284 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bel=C3=A9n=20Albeza?= <balbeza@mozilla.com>
Date: Thu, 19 Apr 2018 17:56:02 +0200
Subject: [PATCH] Bug 1454895 - allow toolbox to call getProcess when debugging
 a local tab. r=jryans

MozReview-Commit-ID: 19bhk3Wn9qE

--HG--
extra : rebase_source : f0926cbe239059cfd45cd2527db94a7b2106e4a5
---
 devtools/client/framework/target.js | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/devtools/client/framework/target.js b/devtools/client/framework/target.js
index 56894f8014b9..f201be3c4fde 100644
--- a/devtools/client/framework/target.js
+++ b/devtools/client/framework/target.js
@@ -413,6 +413,8 @@ TabTarget.prototype = {
       // 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.