On Oct 27, 7:52 am, Mike Ratcliffe <[email protected]> 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 <[email protected]> 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 [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.
