On Aug 26, 7:29 pm, Daniel Gackle <[email protected]> wrote: > After using Firebug 1.6b1 in Firefox 3.6.8 for most of the day, I can > confirm that the problems mentioned in my previous report are still > apparent: (1) scrolling a large js file doesn't work (script window > flickers and jumps around erratically); (2) Firebug's mappings to > source code locations don't work; that is, on breakpoints or when > jumping to a function definition using shift-enter, the window > navigates to a completely incorrect location. Note that the latter > problem usually fixes itself if I shift-click the browser's refresh > button, but only for a little while. > > I should mention that this is on OS X. > > What can be done to track down these bugs? The source code in question > is unfortunately not public, but I could arrange private access if > that would help.
Open the Firebug Tracing tool and set ERRORS and SOURCEFILES, reproduce your problem, use Tracing > Tools > Save to store the trace, the post it to an issue on our list. See http://getfirebug.com/wiki/index.php/FAQ#Using_the_Tracing_Version_of_Firebug jjb > > Daniel > > On Aug 25, 3:01 pm, John J Barton <[email protected]> wrote: > > > On Aug 25, 1:23 pm, Daniel Gackle <[email protected]> wrote: > > > > Hi, our web app's JS is bundled into one big file of about 20K lines. > > > Scrolling this file in Firebug's script window doesn't work. The > > > window flickers and jumps around erratically when you hit the down > > > arrow of the scrollbar or drag the scroll thumb. > > > I have tested the scrolling in files >65k lines. There isn't really > > any reason large files to have problems. > > > You did not say what version of Firebug or browser you were using, so > > its hard to say if there may be another explanation. But I suggest you > > try Firebug 1.6b1 in Firefox 3.6.8 using a new profile. Then we can > > know for sure if you have found a bug. > > > > I've searched in vain for previous discussion of this problem, but it > > > (along with other significant issues, such as totally wrong source > > > code locations on break) happens consistently to us. I'm assuming it > > > is related to the size of the file, though Firebug has recently gotten > > > much faster at handling large JS files in general (yay). > > > Scrolling issues and wrong source locations should not be related. > > Source location issues should not be related to file size. Again the > > procedure above will be a great way to begin. > > > jjb > > > > Regards, > > > Dan Gackle -- 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.
