For reference: This thread started at https://groups.google.com/forum/#!topic/firebug/mXqMM__js8A.
>> 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. > Again, the message says *"If* <script> tags have a "type" attribute, it should equal "text/javascript" or "application/javascript".". So I believe it's clear enough. >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 see. So your main file is actually also a PHP script. Note that Firebug only sees the HTML, JavaScript and CSS output. It doesn't see any PHP includes. > >>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. > Ok, in this case it really sounds unlikely. But with cut and paste you can also do mistakes. > 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. > That's why you should have a look at the *Net* panel first and check, if the JavaScript code was actually transferred. >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. > Ok, so when nothing was displayed inside the Console panel, it could be that there really was no error. But it could also have been that there was a transferring error or the error display was just turned off. Therefore please always make sure you have *Show JavaScript Errors* and *Show JavaScript Warnings* checked inside the Console panel options<http://getfirebug.com/wiki/index.php/Console_Panel#Options_Menu> . > 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. > I can completely understand that. This also often happened to me. It's clear that you're searching the error in your code in the first line, but of course the Firebug programmers also make mistakes and it could be that Firebug was the culprit here. Though from my experience errors resulting in this message most often lie at the user-side. Anyway, if you see the problem again, just follow the steps described at our wiki page <http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug%21>. With these steps you should be able find out if it's a problem at your side, in another extension or in Firebug itself and create a test case<http://getfirebug.com/wiki/index.php/Creating_a_Test_Case>for it when it's really caused by Firebug. 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
