2 ms·
Conditional breakpoints have been around for years, which solve all of those via arbitrary javascript. You just make the condition falsey if you don't want it
by Groxx 9y ago
Conditional breakpoints have been around for years, which solve all of those via arbitrary javascript. You just make the condition falsey if you don't want it to break (or `doAnything() && false`). Skip-counters are just a global counter and `x++ > N`. "Probe Expression" does look pretty neat though, that'd be a bit of a pain to do by hand (probably just viewing logs, which does provide rich objects in recent-ish years).
Granted, the UI isn't as clear about the capabilities, but I generally prefer "run JS, return true" over "choose one of N kinds of things to do", even if one of the N is "run JS, return true". Minus skip counters, those are a bit annoying by hand (needing globally unique var names and all).
I'm not sure when Firefox's built-in debugger got it, but I see search results implying they've been part of FireBug since 2007 at the very least. And I don't remember Chrome's debugger ever not having it (once they got their current-gen-like one, iirc it launched with extremely limited devtools?), though I could easily be forgetting the early days.