gecko-dev/devtools/server/startup
Nicolas Chevobbe 8be561cece Bug 1577798 - Don't create a new Debugger instance in WebConsoleActor. r=ochameau,jlast.
Previously, when creating a new WebConsoleActor, we were
also creating a new Debugger instance.
The problem was that we would never call `enable` on it,
which is what allows to create debuggee for all existing
globals, and for the ones that will be created after.
This means that we had multiple workaround to get a
global debuggee, and in the case of function, would add
a global as a debuggee only to get its script location.

This patch remove the creation of the new Debugger,
and retrieve the parent actor Debugger instance instead.

This shuffles things around a bit, are the Debugger instance
was created by the ThreadActor, but is now by the target
actor (BrowsingContext, ContentProcess, ...).

We can then remove the now unused `getGlobalDebugObject`
hooks we were using in the Function previewer, as we
get a proper Debugger object, with the script location.

Differential Revision: https://phabricator.services.mozilla.com/D44480

--HG--
extra : moz-landing-system : lando
2019-09-16 12:12:22 +00:00
..
content-process.js Bug 1577092 - Remove connectTo* helpers in debugger-server and use connectors directly r=nchevobbe 2019-08-28 13:07:56 +00:00
content-process.jsm Bug 1577092 - Remove connectTo* helpers in debugger-server and use connectors directly r=nchevobbe 2019-08-28 13:07:56 +00:00
frame.js Bug 1577092 - Remove connectTo* helpers in debugger-server and use connectors directly r=nchevobbe 2019-08-28 13:07:56 +00:00
moz.build Bug 1446222 - Move DevTools worker startup to new dir. r=jdescottes 2018-03-19 22:14:08 -05:00
worker.js Bug 1577798 - Don't create a new Debugger instance in WebConsoleActor. r=ochameau,jlast. 2019-09-16 12:12:22 +00:00