We could report errors in the status bar, but not without adding overhead to every page load. jjb
On Mar 29, 5:23 am, alfonsoml <[email protected]> wrote: > I think that the "autodisable" of firebug will bring lots of reports > about broken functionality. > Since the very beginning of firebug I was able to set the domains that > I'm working on, and without the need to keep firebug open I was able > to quickly see any javascript error in the status bar. At that moment > I open Firebug and check what's the error and start the debugging. > Now I'm finding myself that sometimes a page doesn't work, but I don't > see any warning, so I fire up IE8 and it quickly shows a dialog > informing of the problem and the ability to debug it. Even using the > most basic installation of IE6 anyone is able to see the exclamation > icon in the status bar informing of the error. > > On 26 mar, 02:56, John J Barton <[email protected]> wrote: > > > I just finished a blog post about the new enablement approach in > > Firebug 1.4,http://blog.getfirebug.com/?p=124 > > > 1.4a14 has this new approach implemented and we'd be interested in > > feedback.http://getfirebug.com/releases > > > jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
