This just happened to me as well. In my case, I was debugging happy and content. Then I started getting this message. This may or may not help but on the Mac, a three finger swipe will go back a page. I did that by accident. When I clicked forward, I started getting the "No javascript" (described above) message. I tried refresh and shift/refresh, dancing a polka, etc. No change.
When I saw this post, I decided to just quit Firefox and restart it. That solved my problem. On Friday, June 1, 2012 4:00:31 AM UTC-5, Sebastian Zartner wrote: > > I looked this up on the Web and found that it means exactly what it >> says, except that it can also be caused by a <script> tag that does >> not specify type="text/javascript". >> > That's incorrect. Firebug also displays the script when you don't specify > the type attribute. > > I went to work on my script's main file. >> >> That was insane, because the main file contains no JavaScript at all >> -- only references to include files that I'd already cleared. But it >> worked! When I eliminated the entire body of the script, FireBug >> worked correctly. >> > I assume with "main file" you mean your HTML file? And by "references to > include files" you mean <script src="xyz.js" > type="text/javascript"></script>, no? > > I then started putting stuff back in, expecting to zero in on the bit >> of code that was getting Firebug upset. >> >> Wrong. I eventually reinserted the entire script, leaving it exactly >> as it was when I started, and Firebug continued to work correctly. >> >> Now I can begin debugging my script, after a couple of hours of >> totally unproductive problem identification. >> >> I hope someone can explain what happened here, and how to prevent a >> repeat. > > The only explanation I have is that you didn't put it back in exactly as > it was before. E.g. a simple typo in your <script> tag won't load the > file. Or you had a syntax error in your file before, which also won't let > you see the script inside the *Script* panel. > Since it's working again now, we unfortunately don't have a test case for > this to check out what went wrong. > > The next time this occurs, your first sight should go to the *Net* panel > to see if the script was really loaded correctly. If it was, you should > have a look inside the *Console* panel for any syntax errors your code > might have. If there's nothing listed, confirm this via the Firefox Error > Console. > If it was loaded correctly and works fine, but the *Script* panel still > claims that there is no JavaScript on the page, then probably something > weird is going on. > In that case please contact us again *before* you change anything on your > script. If it's possible you should send us that files or somehow give us > access to them, so we're able to reproduce the problem on our machines. > Without a reproducible test case we can just guess what's wrong. > > Sebastian > -- 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
