зеркало из https://github.com/mozilla/gecko-dev.git
e9634ef8c8
When opening the Browser Console, if the browser toolbox fission pref is enabled, we create a WebConsoleConnectionProxy for each process. This allow us to not start the ContentProcessMessages listener (that uses ContentProcessMessagesForward), but directly connect to the content process, to get fully inspectable console message, from the Browser Console. We keep the this.proxy reference in WebConsoleUI to represent the "main" target proxy, and we add an `additionalProxies` property that represent proxies for other targets we connect to (e.g. content process targets). We then have a function to list all the proxies we're handling, in order to be able to do tasks on all of them (e.g. clearing cache, network message, ...) We also take this as an opportunity to add a `evaluateJSAsync` at the WebConsoleUI level so callsites don't retrieve the proxy.webConsoleClient themselves. Differential Revision: https://phabricator.services.mozilla.com/D40786 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| client | ||
| docs | ||
| platform | ||
| server | ||
| shared | ||
| startup | ||
| .eslintrc.js | ||
| .eslintrc.mochitests.js | ||
| .eslintrc.xpcshell.js | ||
| CODE_OF_CONDUCT.md | ||
| moz.build | ||
| templates.mozbuild | ||