Yep, the same to me, I try to set a breakpoint in some correct JS inline line, but allways get set at the very last inline JS line!
It doesn't happens in latest Chrome. Tested in same website mentiones above... El sábado, 1 de agosto de 2015, 3:09:53 (UTC-3), Tanner Edwards escribió: > > I've noticed the same thing, but only on inline javascript. If my > javascript is in its own .js file then breakpoints work just fine, but if > it is inside a script tag, and multiple inline script tags occur on the > page, then the breakpoint will default to the last inline script tag on the > page. > > On Wednesday, July 8, 2015 at 2:23:34 PM UTC-6, [email protected] > wrote: >> >> Today the firefox debugger suddenly stopped working. I have the latest >> version of FF and have not upgraded. I did not add any extensions that may >> have caused the break. >> >> When I launch the debugger, the watch expression pane is closed. >> Previously, when it was working it would launch with this pane open. >> >> If I set a breakpoint, it is ignored. If I add a watch expression, they >> are not added to the variable display. Previously, this would be populated >> with all of the global script variables initially. >> >> I have tried rebooting, restarting, clearing the cache, installing a >> fresh copy and creating a new profile. Nothing has worked, and I don't know >> how to provide a test case because it happened spontaneously. >> > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/070fe693-5245-4f77-81d3-21659e8cb892%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
