After years of using firebug, I just recently discovered the monitor()
and debug() console api functions. Very cool. I'm not sure how they
escaped me for so long.
To the point, these functions appear to assume that the line in the
source file after the function definition is executable code. For
example, given
1 function foo()
2 {
3 console.log("foo");
4 }
5 function bar() {
6
7 console.log("bar");
8 }
9 function baz() {
10 console.log("baz");
11 }
12 function boink() { console.log("boink"); }
debug(foo) puts a breakpoint on line 2, which doesn't break
debug(bar) puts a breakpoint on line 6, which doesn't break
debug(baz) puts a breakpoint on line 10, which does break.
debug(boink) puts a breakpoint on line 13, which doesn't break
The same behavior holds true for monitor().
This limits the functionality of the api. I'd consider this a bug. How
about you?
Ed
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en.
