I'm sure you know this but you may not - you don't need to set break points in Firefox you can just use
debugger; next to the line you wish to debug at and the debugger will be triggered by that code. On Tue, Feb 3, 2009 at 1:00 AM, cahuja <[email protected]> wrote: > > Hello, > > I upgraded to 1.3 (and FF 3.x) and now this (firebug) very useful > tool has become my worst enemy. I am not sure if there is some > problem with my specific installation or .....does anyone else see > these problems ? I cleaned out and went back to FF 2.0.20.0 but the > problems still remain the same. > > Here are the 2 major problems that have brought my use of the tool to > a halt. > All suggestions/clues are welcomed... > > A) I have many .js files that load in a particular page - the last > one is called "cpcp.js". it does get loaded but i cannot find it in > the "Net" list. > in the old version, i had to find it in the "Net" list and > right click to "Inspect in Script window" - now it is already listed > in the scripts pull down menu so i can switch directly to it - and > thats good - BUT when i do switch to it... > - either the file only shows very few lines (first 29 out of 1200) so > i cannot see the line i want to set a breakpoint at OR > - if i have been clicking around and testing stuff and then i switch > to the script window, the lines shown do not correspond to the line > numbers in the file at all. In fact, looking closely i see multiple > copies of the file listed (one after the other) - for example i see > 3421 lines shown for a file that has only 1200 or so. This is same > regardless of whatever choice i made (static, static eval,...) > > B) Previously, i could type the name of a variable in the watch window > and if it wasnt in context, it would just show as undefined, then if a > breakpoint was hit, the watch window would update with the current > value of the variable (assuming it came into scope), in any case the > watched variable would always be listed, once i had typed it in. > Now, if i enter a variable name and the program is not currently in > any breakpoint, it simply disappears as if i never typed it. > > With (A) where i cannot see the line where the breakpoint is to be set > and (B) where i cannot enter watch variables, debugging has become > next to impossible. > All the new features of 1.3 look good, however the debugger has become > quite unusable and i'm not sure where the problem is. > > C) An old problem that still seems to exist in 1.3 is that once > firebug is opened and any script is being examined....even though i > reload the browser page, Firebug does not refresh - is there a menu > item or something to use to tell firebug to update its cache of files > with the new ones loaded. > (otherwise one is having to exit the browser completely after fixing > any particular bug....) > > So is there a place i can still get 1.2 so i can back down - > everywhere i look i see only 1.3... > > Help. > > If i need to provide screen shots and or test files, ore info please > let me know. Thanks. > > -chander > PS>> yes, i did try un-installing FF, rebooted, installed FF (3 and > 2.02) clean (i.e. no other extensions) and the problems above still > occur > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
