It's pretty confusing and not at all intuitive that "debugger;" only fires once you've opened the debugger once (thankfully you don't have to be *in* the debugger). I suggest having it fire when any of the devtools are active. E.g. I dropped a "debugger;" line into my code and then manually triggered it from the Web Console, but nothing happened. I think it should still activate the debugger.

The problem with this is that it would require enabling debug mode on the page, which will cause some slowdown, even in the case where one wants to inspect the page styles. Or even worse, when one tries to profile execution, essentially affecting the measurements. Jim, isn't this accurate? Rob, Dave, what do you think about this?

Yeah, this is another restriction caused by bug 716647: we can't take stack frames that were running at full optimization and then debug them. The stack must contain no frames scoped to a global when we add that global as a debuggee. I've added that bug as a blocker for this one. Can you guys think of more cases where this "no live frames on stack" restriction has caused a problem? Let's get bugs filed, all listed as blocked by 716647, so I can make the case to the JS team.

Bug 956087 is opened for the same thing as this, but has more discussion and context. James, what do you think about duping this one?

(In reply to Brian Grinstead [:bgrins] from comment #3) > Bug 956087 is opened for the same thing as this, but has more discussion and > context. James, what do you think about duping this one? Fine with me!