>> 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. In that case the message itself is incorrect. I realized after posting that it says both things. >>I went to work on my script's main file... >> -- 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? Yes. >And by "references to "include files" you mean ><script src="xyz.js">type="text/javascript"></script>, no? No. I mean files that are included in the script by a PHP "include" or "require_once" statement. They could contain any combination of PHP, HTML, and JavaScript code. >>I then started putting stuff back in, expecting to zero in on the bit... >> 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... I can't prove that that is not the case, but I think it's very unlikely, because I was not typing... I was strictly cutting and pasting... precisely to avoid typos. In any case, it's difficult to imagine what type of error I could accidentally fixed that would have made a difference to Firebug. As I said, the code I was experimenting with contained no JavaScript; if there an error in the HTML, my IDE would have flagged it; and even if there was in error in my PHP it never left the server. >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.... I'll keep these suggestions and try them if the problem recurs. I did check the Console panel, and it was empty. It looks like there's nothing you can do with this until I can send you a copy of the failing file. I understand that. I think you'll understand why I didn't save one: I was focused on getting FireBug to work so that I could debug my code, and the possibiility that FireBug was malfunctioning did not occur to me until near the end of the process, when the script in its original form was long gone. -- 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
