What's new in ChromeDevTools 0.3.8
Nov 29, 2012
- Break on Exception:
- The debugger feature that instructs JavaScript VM to pause on exception throwing event has got a new form. Previously, it was controlled from the context menu on LaunchElement. Since this release, a more traditional Eclipse approach is implemented.
- To enable breaking on exception, the user should add a JS Exception breakpoint: Run|Add V8/Chrome JavaScript Exception Breakpoint menu item. This breakpoint has regular enable/disable semantics, additionally overridden by the Skip All Breakpoints control and, what's most useful, its state is persisted by the workspace. This means that once you have enabled break on exception, this will hold for the following debug sessions.
- Even though the UI allows you to create multiple breakpoints of this kind, you should hardly need more than one.
- Slight Changes to Launch Configuration:
- You might notice that the Breakpoint sync on launch control has disappeared from the launch configuration dialog. This is due to such synchronization only making sense for V8 Standalone configurations (where this control is left untouched).
- WIP Backends:
- WIP backends haven't been changed in this release.