Google chrome script debugger code#

Events include timer events, like setTimer, clearTimer, and the timer tick event handler. An event listener breakpoint is useful when you are trying to find who is responding to a click event, for example. There are also event listener breakpoints.

Google chrome script debugger code#

You can also break into code starting an AJAX request (and break only on specific URLs). Like any debugger you can break on specific lines of code. After you change the code the changes are live in the browser and working. Like the console window, this is a useful feature to have when you are still trying to figure out how things work. The sixth button is the live edit button, where you can click the the source code and change the code on the fly. Unfortunately, local variables will still be minified and look like variables from a Fortran program circa 1972 (I,j,k). If you are trying to step through minified source code to find a bug in a production library, the pretty print feature will at least give you the proper line breaks and white space to read the code. The fifth button is the pretty print button. Break on unhandled exceptions is a fast way to find broken code. The debugger can break on all exceptions, break on unhandled exceptions only, or ignore exceptions. The fourth button toggles the break on exceptions behavior. The third button is the 'click an element on the page to inspect it' button. The console also displays errors, warnings, and log messages, and provides autocompletion (the right arrow key seems to be the safest way to complete, as the ENTER key sometimes doesn't work (I said it was quirky)). Tip: To enter code that spans multiple lines use Shift+Enter to end a line. You can execute script code in the current debugging context, meaning you can manipulate the DOM, try different CSS selectors with jQuery, or call into libraries loaded on a page to figure out how an API works. The second button opens the Console, which is a helpful JavaScript REPL. The leftmost button allows you to dock and undock the tools window from the browser window. Here is a quick brain dump on some areas of interest (these are all in the stable build 17.0.963.79).

The Chrome Developer Tools are a bit quirky, but for script debugging I currently like them the best.