Open Firebug on Javascript Error

[Tom-343]

Firefox 3.5.3 - Firebug 1.4.3

If Firebug is attached to a page but minimized, is there an option to
automatically show the window if a javascript error occurs?  I've had
a look through the about:config options, can't see anything obvious.

I occasionallly have the situation (especially if I've accidentally
turned Firebug on by mistake) where the page doesn't seem be reacting
correctly, eventually to discover that the javascript debugger has
stopped on an error.

(Also, if the javascript line in question is long, it's impossible to
see the red error message underneath!)

Cheers,
Tom

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[John J Barton]

On Oct 22, 10:02 am, Tom <tomhartl...@...> wrote:

> Firefox 3.5.3 - Firebug 1.4.3
>
> If Firebug is attached to a page but minimized, is there an option to
> automatically show the window if a javascript error occurs?  I've had
> a look through the about:config options, can't see anything obvious.
>
> I occasionallly have the situation (especially if I've accidentally
> turned Firebug on by mistake) where the page doesn't seem be reacting
> correctly, eventually to discover that the javascript debugger has
> stopped on an error.
>
> (Also, if the javascript line in question is long, it's impossible to
> see the red error message underneath!)

I believe both of these problems are fixed in Firebug 1.5,
http://getfirebug.com/releases/firebug/1.5X, look for b1.

jjb
>
> Cheers,
> Tom

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[Tom-343]

On Oct 22, 6:13 pm, John J Barton <johnjbar...@...> wrote:

> On Oct 22, 10:02 am, Tom <tomhartl...@...> wrote:
>
> > Firefox 3.5.3 - Firebug 1.4.3
>
> > If Firebug is attached to a page but minimized, is there an option to
> > automatically show the window if a javascript error occurs?  I've had
> > a look through the about:config options, can't see anything obvious.
>
> > I occasionallly have the situation (especially if I've accidentally
> > turned Firebug on by mistake) where the page doesn't seem be reacting
> > correctly, eventually to discover that the javascript debugger has
> > stopped on an error.
>
> > (Also, if the javascript line in question is long, it's impossible to
> > see the red error message underneath!)
>
> I believe both of these problems are fixed in Firebug 1.5,http://getfirebug.com/releases/firebug/1.5X, look for b1.
>
> jjb

Hi John, thanks for the quick reply.

I've uninstalled 1.4.3 and installed 1.5Xb1.
"Break on all errors" has gone from the Scripts tab popup menu, and
javascript errors are showing the red "1 Error" in the console frame
in the status bar.
Does that mean "break on all errors" has gone altogether, as I can
find it in any of the options?

Cheers,
Tom

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[John J Barton]

On Oct 22, 10:48 am, Tom <tomhartl...@...> wrote:

> On Oct 22, 6:13 pm, John J Barton <johnjbar...@...> wrote:
>
>
>
> > On Oct 22, 10:02 am, Tom <tomhartl...@...> wrote:
>
> > > Firefox 3.5.3 - Firebug 1.4.3
>
> > > If Firebug is attached to a page but minimized, is there an option to
> > > automatically show the window if a javascript error occurs?  I've had
> > > a look through the about:config options, can't see anything obvious.
>
> > > I occasionallly have the situation (especially if I've accidentally
> > > turned Firebug on by mistake) where the page doesn't seem be reacting
> > > correctly, eventually to discover that the javascript debugger has
> > > stopped on an error.
>
> > > (Also, if the javascript line in question is long, it's impossible to
> > > see the red error message underneath!)
>
> > I believe both of these problems are fixed in Firebug 1.5,http://getfirebug.com/releases/firebug/1.5X, look for b1.
>
> > jjb
>
> Hi John, thanks for the quick reply.
>
> I've uninstalled 1.4.3 and installed 1.5Xb1.
> "Break on all errors" has gone from the Scripts tab popup menu, and
> javascript errors are showing the red "1 Error" in the console frame
> in the status bar.

You can click on the red 1 Error, the console opens, and if the error
is breakpointable, you can set a breakpoint on it in the console.

> Does that mean "break on all errors" has gone altogether, as I can
> find it in any of the options?

We are trying to get rid of these invisible options. To break on
errors that can appear in the Console, click the pause button, [ || ].
It will throb, then break when you hit an error.

We're not completely happy with the current solution. We don't like
the old solution. We are looking for suggestions. Contenders need to
be visible and very compact, competitive with our current solution in
these regards.

A separate issue is stickiness: currently the break on any error in
the console turns off when you hit.

Try the b1 solution and let us know what you think.

jjb
>
> Cheers,
> Tom

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[Tom-343]

> > Hi John, thanks for the quick reply.
>
> > I've uninstalled 1.4.3 and installed 1.5Xb1.
> > "Break on all errors" has gone from the Scripts tab popup menu, and
> > javascript errors are showing the red "1 Error" in the console frame
> > in the status bar.
>
> You can click on the red 1 Error, the console opens, and if the error
> is breakpointable, you can set a breakpoint on it in the console.
>
> > Does that mean "break on all errors" has gone altogether, as I can
> > find it in any of the options?
>
> We are trying to get rid of these invisible options. To break on
> errors that can appear in the Console, click the pause button, [ || ].
> It will throb, then break when you hit an error.
>
> We're not completely happy with the current solution. We don't like
> the old solution. We are looking for suggestions. Contenders need to
> be visible and very compact, competitive with our current solution in
> these regards.
>
> A separate issue is stickiness: currently the break on any error in
> the console turns off when you hit.
>
> Try the b1 solution and let us know what you think.
>
> jjb

Hi John,

Apologies for the delay in replying - had quite a lot on my plate
recently, and need a bit of time to think about what exactly I expect
from the system.

One of the major downsides of not having an always-on "break on all
errors" facility is not being able to quickly see the state of objects/
variables at that moment.  Admittedly, most of the time a breakpoint
and a reload will make it happen again - but there are times when you
need to be able to see things there and then.  And especially if the
fault is on the page load, clicking of the "pause" button isn't going
to be possible.

I can see where you're coming from (not liking the old or current
solutions) - it's a difficult one to call, and no I can't see any
obvious GUI solution either.

Sorry I can't be more help - will keep thinking about it as I'm using
the system, and in the unlikely event that I have a brainwave I'll get
back to you

Cheers,
Tom

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[Mike Ratcliffe-2]

"especially if the fault is on the page load, clicking of the "pause"
button isn't going to be possible."

That is a good point, I had not realized this.

On Oct 27, 10:22 am, Tom <tomhartl...@...> wrote:

> > > Hi John, thanks for the quick reply.
>
> > > I've uninstalled 1.4.3 and installed 1.5Xb1.
> > > "Break on all errors" has gone from the Scripts tab popup menu, and
> > > javascript errors are showing the red "1 Error" in the console frame
> > > in the status bar.
>
> > You can click on the red 1 Error, the console opens, and if the error
> > is breakpointable, you can set a breakpoint on it in the console.
>
> > > Does that mean "break on all errors" has gone altogether, as I can
> > > find it in any of the options?
>
> > We are trying to get rid of these invisible options. To break on
> > errors that can appear in the Console, click the pause button, [ || ].
> > It will throb, then break when you hit an error.
>
> > We're not completely happy with the current solution. We don't like
> > the old solution. We are looking for suggestions. Contenders need to
> > be visible and very compact, competitive with our current solution in
> > these regards.
>
> > A separate issue is stickiness: currently the break on any error in
> > the console turns off when you hit.
>
> > Try the b1 solution and let us know what you think.
>
> > jjb
>
> Hi John,
>
> Apologies for the delay in replying - had quite a lot on my plate
> recently, and need a bit of time to think about what exactly I expect
> from the system.
>
> One of the major downsides of not having an always-on "break on all
> errors" facility is not being able to quickly see the state of objects/
> variables at that moment.  Admittedly, most of the time a breakpoint
> and a reload will make it happen again - but there are times when you
> need to be able to see things there and then.  And especially if the
> fault is on the page load, clicking of the "pause" button isn't going
> to be possible.
>
> I can see where you're coming from (not liking the old or current
> solutions) - it's a difficult one to call, and no I can't see any
> obvious GUI solution either.
>
> Sorry I can't be more help - will keep thinking about it as I'm using
> the system, and in the unlikely event that I have a brainwave I'll get
> back to you
>
> Cheers,
> Tom

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[John J Barton]

On Oct 27, 7:52 am, Mike Ratcliffe <mich...@...>
wrote:
> "especially if the fault is on the page load, clicking of the "pause"
> button isn't going to be possible."
>
> That is a good point, I had not realized this.

That's a bug we need to fix.
jjb

>
> On Oct 27, 10:22 am, Tom <tomhartl...@...> wrote:
>
> > > > Hi John, thanks for the quick reply.
>
> > > > I've uninstalled 1.4.3 and installed 1.5Xb1.
> > > > "Break on all errors" has gone from the Scripts tab popup menu, and
> > > > javascript errors are showing the red "1 Error" in the console frame
> > > > in the status bar.
>
> > > You can click on the red 1 Error, the console opens, and if the error
> > > is breakpointable, you can set a breakpoint on it in the console.
>
> > > > Does that mean "break on all errors" has gone altogether, as I can
> > > > find it in any of the options?
>
> > > We are trying to get rid of these invisible options. To break on
> > > errors that can appear in the Console, click the pause button, [ || ].
> > > It will throb, then break when you hit an error.
>
> > > We're not completely happy with the current solution. We don't like
> > > the old solution. We are looking for suggestions. Contenders need to
> > > be visible and very compact, competitive with our current solution in
> > > these regards.
>
> > > A separate issue is stickiness: currently the break on any error in
> > > the console turns off when you hit.
>
> > > Try the b1 solution and let us know what you think.
>
> > > jjb
>
> > Hi John,
>
> > Apologies for the delay in replying - had quite a lot on my plate
> > recently, and need a bit of time to think about what exactly I expect
> > from the system.
>
> > One of the major downsides of not having an always-on "break on all
> > errors" facility is not being able to quickly see the state of objects/
> > variables at that moment.  Admittedly, most of the time a breakpoint
> > and a reload will make it happen again - but there are times when you
> > need to be able to see things there and then.  And especially if the
> > fault is on the page load, clicking of the "pause" button isn't going
> > to be possible.
>
> > I can see where you're coming from (not liking the old or current
> > solutions) - it's a difficult one to call, and no I can't see any
> > obvious GUI solution either.
>
> > Sorry I can't be more help - will keep thinking about it as I'm using
> > the system, and in the unlikely event that I have a brainwave I'll get
> > back to you
>
> > Cheers,
> > Tom

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[Nicolas Hatier-2]

A sticky "break on error" would likely be helpful. I understand the point about it buried in a menu not being a good idea, but I'm sure there's a better place for it. Maybe change the throbbing Pause button by a two or three-state push button - one click it throbs, another click it stays down (sticky), a third click it's up (disabled).

Nicolas

John J Barton wrote:

On Oct 27, 7:52 am, Mike Ratcliffe mich...@...
wrote:
  

"especially if the fault is on the page load, clicking of the "pause"
button isn't going to be possible."

That is a good point, I had not realized this.
    

That's a bug we need to fix.
jjb

  

On Oct 27, 10:22 am, Tom tomhartl...@... wrote:

    

Hi John, thanks for the quick reply.
          

I've uninstalled 1.4.3 and installed 1.5Xb1.
"Break on all errors" has gone from the Scripts tab popup menu, and
javascript errors are showing the red "1 Error" in the console frame
in the status bar.
          

You can click on the red 1 Error, the console opens, and if the error
is breakpointable, you can set a breakpoint on it in the console.
        

Does that mean "break on all errors" has gone altogether, as I can
find it in any of the options?
          

We are trying to get rid of these invisible options. To break on
errors that can appear in the Console, click the pause button, [ || ].
It will throb, then break when you hit an error.
        

We're not completely happy with the current solution. We don't like
the old solution. We are looking for suggestions. Contenders need to
be visible and very compact, competitive with our current solution in
these regards.
        

A separate issue is stickiness: currently the break on any error in
the console turns off when you hit.
        

Try the b1 solution and let us know what you think.
        

jjb
        

Hi John,
      

Apologies for the delay in replying - had quite a lot on my plate
recently, and need a bit of time to think about what exactly I expect
from the system.
      

One of the major downsides of not having an always-on "break on all
errors" facility is not being able to quickly see the state of objects/
variables at that moment.  Admittedly, most of the time a breakpoint
and a reload will make it happen again - but there are times when you
need to be able to see things there and then.  And especially if the
fault is on the page load, clicking of the "pause" button isn't going
to be possible.
      

I can see where you're coming from (not liking the old or current
solutions) - it's a difficult one to call, and no I can't see any
obvious GUI solution either.
      

Sorry I can't be more help - will keep thinking about it as I'm using
the system, and in the unlikely event that I have a brainwave I'll get
back to you
      

Cheers,
Tom
      

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.


  

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.