Re: Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-13 Thread J. Ryan Stinnett
On Mon, Mar 13, 2017 at 2:04 PM, Jared Wein wrote: > Yes, we support watches in the new debugger UI now. The new debugger UI is > used by default in the Browser Content Toolbox, and it is pretty nice and > shiny. New debugger UI is on for Browser Content Toolbox, but at the moment, it's still o

Re: Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-13 Thread Jared Wein
Yes, we support watches in the new debugger UI now. The new debugger UI is used by default in the Browser Content Toolbox, and it is pretty nice and shiny. Cheers, Jared On Mon, Mar 13, 2017 at 12:50 PM, Gijs Kruitbosch wrote: > On 13/03/2017 16:48, J. Ryan Stinnett wrote: > > > On Thu, Mar 9,

Re: Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-13 Thread Gijs Kruitbosch
On 13/03/2017 16:48, J. Ryan Stinnett wrote: On Thu, Mar 9, 2017 at 2:18 AM, Panos Astithas > wrote: You almost completely resolved the 4-year-old bug 814298, yay! I now wonder if this makes it easier to improve mochitest debugging per bug 929535. Thank

Re: Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-13 Thread J. Ryan Stinnett
On Thu, Mar 9, 2017 at 2:18 AM, Panos Astithas wrote: > You almost completely resolved the 4-year-old bug 814298, yay! I now > wonder if this makes it easier to improve mochitest debugging per bug > 929535. Thanks for the pointers to these bugs. Bug 814298 stills needs breakpoint persistence t

Re: Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-09 Thread Panos Astithas
You almost completely resolved the 4-year-old bug 814298, yay! I now wonder if this makes it easier to improve mochitest debugging per bug 929535. On Wed, Mar 8, 2017 at 9:22 PM, Kris Maglione wrote: > On Wed, Mar 08, 2017 at 01:09:10PM -0600, J. Ryan Stinnett wrote: > >> With bug 1275942 in Fir

Re: Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-08 Thread Kris Maglione
On Wed, Mar 08, 2017 at 01:09:10PM -0600, J. Ryan Stinnett wrote: With bug 1275942 in Firefox 55, a new Firefox CLI option was added: `--wait-for-jsdebugger`. ... Let me know if it's useful and / or you see room for improvement. To put it one way: if we are ever in the same room, I owe you a

Re: Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-08 Thread Jared Wein
This is very useful! Thank you for adding this! On Wed, Mar 8, 2017 at 2:11 PM, Dave Townsend wrote: > This is awesome, thanks for implementing this! > > On Wed, Mar 8, 2017 at 11:09 AM, J. Ryan Stinnett > wrote: > >> With bug 1275942 in Firefox 55, a new Firefox CLI option was added: >> `--wai

Re: Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-08 Thread Dave Townsend
This is awesome, thanks for implementing this! On Wed, Mar 8, 2017 at 11:09 AM, J. Ryan Stinnett wrote: > With bug 1275942 in Firefox 55, a new Firefox CLI option was added: > `--wait-for-jsdebugger`. > > Example usage: > > 1. Add "debugger;" to top of browser/base/content/browser.js > 2. $ ./ma

Startup JS debugging (sometimes) possible via Browser Toolbox

2017-03-08 Thread J. Ryan Stinnett
With bug 1275942 in Firefox 55, a new Firefox CLI option was added: `--wait-for-jsdebugger`. Example usage: 1. Add "debugger;" to top of browser/base/content/browser.js 2. $ ./mach run --jsdebugger --wait-for-jsdebugger 3. Browser Toolbox opens, pausing Firefox startup at the added line This tri