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 displaying the stack trace than the console.log did.
On Dec 1, 2:46 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
> Ok now I see what you mean. The representation we use for the object
> changed. What don't you like about the new representation?
>
> jjb
>
> On Dec 1, 12:33 pm, Steve Smith <slsmit...@gmail.com> wrote:
>
> > 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 set up of course. :) )
>
> > On Dec 1, 2:23 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
>
> > > 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 caught
> > > > in.
>
> > > If you post a test case then we can know what you are talking about.
>
> > > jjb
>
> > > > N
>
> > > > On Wed, Dec 1, 2010 at 12:09 PM, John J Barton
> > > > <johnjbar...@johnjbarton.com>wrote:
>
> > > > > 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
> > > > > > 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 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 the line of the error in the script. Is
> > > > > > > > there
> > > > > > > > any way to turn that behavior off so that our error handling
> > > > > > > > code
> > > > > will
> > > > > > > > run?
>
> > > > > > > I don't think Firebug knows how to do what you describe. Some
> > > > > > > things
> > > > > > > you can try:
> > > > > > > 1) Firebug > Firebug Icon Menu > Options > Reset all. Does it
> > > > > > > help?
> > > > > > > 2) Install Firebug in a new Firefox profile, Does it help?
> > > > > > > 3) Report a bug,http://code.google.com/p/fbug/issues/list
>
> > > > > > > jjb
>
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > > > Groups
> > > > > "Firebug" group.
> > > > > To post to this group, send email to fire...@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > > > > firebug+unsubscr...@googlegroups.com<firebug%2bunsubscr...@googlegroups.com>
> > > > > .
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/firebug?hl=en.
>
> > > > --
> > > > Nadav Givoni
> > > > nadavgiv...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to fire...@googlegroups.com.
To unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en.
