This could be related to: Issue 4646: Incorrect marking of lines as executable
http://code.google.com/p/fbug/issues/detail?id=4646 Honza On Jun 30, 1:32 pm, Porcupine <[email protected]> wrote: > Hello, > > I think I found a bug in the way Firebug parses or handles Javascript code. > It is visible on the script panel: sometimes the line numbers of Javascript > code are incorrectly greyed out. You then cannot set breakpoints on those > lines. > > For example, on the > URLhttp://wwwhome.ewi.utwente.nl/~vriezekolke/Raster/beta3/it happens: > in file rasterMain.js on lines 989, 1002, and especially 2433. > in file rasterComponent.js on line 262. > in file rasterNodeCluster.js on line2 215, 223. > in file rasterNode.js on line 219 (very evident). > > Somehow it always happens with for-loops. Often a work-around is to make > sure that the body of the for-loop contains more than one line. Sometimes > even adding a comment line will do. > > I have tried 1.9.2 and 1.10 beta 2, both on Firefox 13.0.1 for Mac OS X > 10.6.8. > > Thanks for the excellent Firebug tool! > > (PS: second post, because first post disappeared?!) -- 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
