Re: Easier debugging/inspecting of remote tab state with the Browser Content Toolbox

Wow, this is great! I just ran into this problem a week ago and it was quite annoying to work around. Thanks for fixing it. :-) bholley On Tue, Oct 3, 2017 at 4:15 PM, Matthew N. wrote: > With bug 1401343 > fixed, `TabChildGlobal`s for the

Re: Easier debugging/inspecting of remote tab state with the Browser Content Toolbox

On 2017-10-03 5:44 PM, Boris Zbarsky wrote: On 10/3/17 7:15 PM, Matthew N. wrote: For those of you who don't know, when the "devtools.chrome.enabled" pref is true the Web Developer > Browser Content Toolbox opens a toolbox targeting the content process that the selected tab is loaded in. Mat

Re: Easier debugging/inspecting of remote tab state with the Browser Content Toolbox

On 10/3/17 7:15 PM, Matthew N. wrote: For those of you who don't know, when the "devtools.chrome.enabled" pref is true the Web Developer > Browser Content Toolbox opens a toolbox targeting the content process that the selected tab is loaded in. Matt, Do you know whether this starts a new Firef

Easier debugging/inspecting of remote tab state with the Browser Content Toolbox

With bug 1401343 fixed, `TabChildGlobal`s for the attached content process are exposed via a `tabs` getter in the Browser Content Toolbox's console tab. This makes it much easier to inspect a remote tab's state or to access privileged APIs rela