Please try Firebug 1.3, its about to become the release version. http://getfirebug.com/releases. If its ok, we're good. If you still have problems, try 1.4 from the same place. Let us know and then we can decide what to do. jjb
On Jan 6, 4:14 pm, sampablokuper <[email protected]> wrote: > Sometimes, when I enter a watch expression or console command in > Firebug, it doesn't respond, even though it normally would. > > For instance, normally if I enter alert("foo"); into the Firebug > console, normally I'll get an alert box with "foo" written in it, but > occasionally this does not work, even if it previously worked. > > When I say previously worked, I mean it worked in the same version of > Firefox, with the same page loaded, and with all DHTML, etc. in the > same state. > > The same problem sometimes occurs with watch expressions. Some > expressions that normally work fine for me just occasionally get no > result. I press the enter key, but the Watch pane just acts as though > I hadn't done so: it keeps the expression open for editing, rather > than giving me the expression's results, and it won't let me start a > new watch expression either. > > A colleague of mine has experienced the same behaviour on his PC. This > has happened to me on both Vista and Leopard, so it's not OS-specific. > > Does anyone know how to get around this? Can Firebug be "restarted" or > otherwise have its internal state - which is obviously messed up when > I get this behaviour - reset? > > Also, is this a reported bug, and if not, should I be posting it to > the FB bug tracker? > > Many thanks, > > Sam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
