In general we try not to be skeptical about bug reports. In my opinion, any problem a user has is a bug.
On the other hand we know that new watch expressions work and we have a test we run to verify it. So if a user says it fails for them, what should we do? Mostly we try to get users to repeat the problem in a controlled way, usually by asking them to use a new firefox profile. Lots of problems get fixed this way. We're open to other suggestions on how to reproduce user problems. Short of that we just have to wait for someone like yourself to come along with more information. The new watch function requires both the script and console panels to be enabled. The bug here is that the UI does not tell you this important fact. jjb On Mar 19, 4:38 pm, Jim R <[email protected]> wrote: > I had this same problem, which the FireBug developers seemed skeptical > about. > > Anyway, I turned off debugging for the host (in my case, localhost), > using the Script tab dropdown; then I reenabled for localhost, and > this time checked the three checkboxes for Console, Script, and Net. > Then it started working again. > > On Mar 9, 4:35 pm, boy_named_Goo <[email protected]> wrote: > > > While at a breakpoint, I can't type an expression into the "New watch > > expression" field. It just seems like that field is dead. Clicking > > it doesn't show me a text cursor. > > > I'm using Firebug 1.3.3 with Firefox 3.0.7 on Windows Vista Ultimate > > 64 bit. It was working great for me on a prior version of Firefox and > > Firebug, and I used it a lot. > > > How do I fix it? Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
