And now... it's gone away. Was happening last night and not this morning. I did threaten to reprogram my laptop with an axe, but it's never listened to me before. I doubt it's that.
Curiouser and curiouser. Oh well. If it happens again, I do further analysis. I had thought it had something to do with setting a variable watch, but that doesn't appear to be the case. On Thursday, September 18, 2014 11:39:40 AM UTC-5, Carl Franz wrote: > > I'm having the same problem. Same version of Firebug (2.0.4), version > 32.0.1 of Firefox. > > I'm not sure whether it has anything to do with the code being for an > event handler or not. > > > I have no idea whether my process is reproducible or not given that I > cannot stop it from happening and then go through the process again to get > it to happen. It seems that once a breakpoint is set, I can unset it and > the debugger will stop there anyway. For a while. I think, I could set a > conditional of "1==2" to get it to stop but even that isn't working now. > > You want I'll send you the code and HTML/CSS. It's just a simple Suduko > process I was doing to learn JavaScript. > -- 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/926f0f9a-8da4-4f2e-a44d-21244ceb9272%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
