For reference: This thread is a duplicate of https://groups.google.com/forum/#!topic/firebug/PTDddr0B6Y8.
Sebastian On Saturday, June 30, 2012 9:30:41 AM UTC+2, Porcupine wrote: > > Hello, > > I think I discovered a bug in the way Firebug parses or handles Javascript > code. It is visible in the script panel. Sometimes, after an (apparently) > complex statement the line numbers of the remainder of the function are > greyed out. > > Example, on the page: > http://wwwhome.ewi.utwente.nl/~vriezekolke/Raster/beta3/ it is visible in > - file rasterNode.js line 150, > - file rasterMain.js line 1028, 2432, > - file rasterNodeCluster.js lines 223, 230, 237. > > Breakpoints do not work on the lines that have a grey number --> problem. > The issue seems to happen with some for-loops only, not with all. > Enclosing the body of the loop in { braces } does not help, but rewriting > the body of the loop so that it spans two lines does help. One of those > lines can even be a comment. Or the single statement in the body can be > split over two lines, instead of putting all on a single line. So there are > several workarounds, but it would be nice if they were not necessary. > This happens both with 1.9.2 and 1.10 beta 2. > > Thanks for this excellent tool! > -- 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 https://groups.google.com/forum/#!forum/firebug
