I just installed Firebug 1.6 and it seems to be overriding our try/
catch error handling code. This is basically code that catches the
error and does a console.log of the error object. But now instead the
console in Firebug is stopping at the error and displaying the error
message that links to
On Dec 1, 6:45 am, Steve Smith slsmit...@gmail.com wrote:
I just installed Firebug 1.6 and it seems to be overriding our try/
catch error handling code. This is basically code that catches the
error and does a console.log of the error object. But now instead the
console in Firebug is
OK so I jumped to some conclusions that were wrong. It's not that
Firebug is overriding our try/catch. It's just that the console.log
display of the error object has changed. When we switch to using
console.exception to display the error object, we get the stack trace,
which is what I really
The arguments passed into using 1.6 into the catch statement are
definitely different then the arguments passed into the 1.5 version of
Firebug.
Nak1
On Dec 1, 9:43 am, John J Barton johnjbar...@johnjbarton.com wrote:
On Dec 1, 6:45 am, Steve Smith slsmit...@gmail.com wrote:
I just installed
Firebug does not pass arguments into the catch statement, I guess you
have some other problem.
jjb
On Dec 1, 10:02 am, Nak1 nadavgiv...@gmail.com wrote:
The arguments passed into using 1.6 into the catch statement are
definitely different then the arguments passed into the 1.5 version of
Then it's overriding the method somehow, because I've reverted back to
FireBug 1.5.4 and the argument passed into the catch is the standard Error
object, in 1.6 it's passing in the object in which the error was caught in.
N
On Wed, Dec 1, 2010 at 12:09 PM, John J Barton
So when you put arguments into the watch panel, it has changed
somehow?
On Dec 1, 10:02 am, Nak1 nadavgiv...@gmail.com wrote:
The arguments passed into using 1.6 into the catch statement are
definitely different then the arguments passed into the 1.5 version of
Firebug.
Nak1
On Dec 1, 9:43
On Dec 1, 10:15 am, Nadav Givoni nadavgiv...@gmail.com wrote:
Then it's overriding the method somehow, because I've reverted back to
Which method?
FireBug 1.5.4 and the argument passed into the catch is the standard Error
object, in 1.6 it's passing in the object in which the error was
You can run this:
try {
var tst = new testObj();
}catch(e){
console.log(e)
}
in Firebug 1.5.4 and 1.6 and compare the outputs. Or
try {
var tst = new testObj();
}catch(e){
debugger;
}
and compare the e object in each version.
(Provided you don't have testObj
I don't know that I don't like it; I guess I find it a little odd that
the console.log does not output the error object as an object like it
used to. But I'm happy to use console.exception to view the error;
it's giving me all the info I need. And in fact console.exception does
a better job of
10 matches
Mail list logo
