1011677 - Debugging chrome code running in a child process

Status: RESOLVED DUPLICATE of bug 1060093

(DevTools :: Debugger, defect)

Description

[Tom S [:evilpie]]

Allison had this idea in bug 1011663. I don't think we have any way of doing this yet, but it's probably just a matter of rewiring some actor that we already have for content code in the child.

Comment 1

[Panos Astithas (he/him) [:past] (please ni?)]

I think the backend code is in place for this: script.js which contains both ThreadActor and ChromeDebuggerActor is already loaded in child processes. What is missing is a UI mode toggle that would make the Browser Toolbox target the latter instead of the former.

Actually, I'm not quite sure how a sane UI for this would look, especially if we want it to work before Firefox is e10s-only. If we only consider the long term, I think it boils down to a UI element for focusing the browser toolbox to a particular global, which is something we've been wanting to do for quite a while (bug 806775, bug 928018).

Comment 2

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

A separate toolbox for chrome code in the content process was added in bug 1060093.