Javascript compliancy

Regular Joined: Oct 13, 2007 Posts: 61

Hi,
I have been trying to validate my site, and I have one error left that I can't seem to resolve. It says I need a meta-tag, which I have tried to put in meta.php but it doesn't seem to make any change. I originally had two similar errors, one for Content-Style-Type, that error cleared after I added a meta-tag, I tried to do the same with this javascript one, but I still have the error. I don't really know how to specify it in HTTP Headers, in fact, I don't really know much about HTTP Headers at all, Embarassed

and what I tried didn't work, so I gave up!

Please could someone help me understand this better.

The error I got is shown below

Thanks
Jane Smile

THE ERROR
When using embedded events (Event-Handler), script language must be specified within Meta-Tag
(z.B. <meta http-equiv="Content-Script-Type" content="text/javascript" />)
or HTTP-Header (Content-Script-Type: text/javascript)
Error Position: out="this.style.background='#F7B3FA'" onclick="window.location.href='index.p

Posted: Tue Nov 27, 2007 9:44 am

Well something like this is an embedded (javascript) event;

Code:

out="this.style.background='#F7B3FA'" onclick="window.location.href='index.p

But you have to make clear to browsers that you are using javascript (or at least for the validator to pass Wink

).

So you should add the following to you <head> within meta.php

Code:

<meta http-equiv="Content-Script-Type" content="text/javascript" />

Posted: Tue Nov 27, 2007 4:41 pm

Thanks for your help again Smile

Its validated but would you believe now I have another problem!

The validome validator has always shown these two remarks even though its now validated

<b>This XHTML 1.0 document was delivered with MIME-Type text/html. This MIME-Type should not be used, if the document does not correspond to the HTML Compatibility Guidelines.

Ther was no charset encoding found. Because of this a fallback to UTF-8 was made</b>

But the W3c validator never showed anything like that before and I now have this warning on there too - <b>No Character Encoding Found! Falling back to UTF-8.</b> which has either occured since I started correcting the errors that were shown by Validome or it could be since I've messed around with the forums on my site (I switched the forum css over to the anagram theme css and deleted the css in the overall header.php. The w3c css validator also now shows quite a few errors that all seem to be related to the forum css now in the theme css, whereas before it validated ok.

My main problem though seems to the charset encoding, so how do I correct it?

Thanks for any help!
Jane

Posted: Tue Nov 27, 2007 5:37 pm

Just an update, I now know the problem is nothing to do with the forums, as I've sorted that out now. Smile

Posted: Tue Nov 27, 2007 6:07 pm

And a further update, I corrected the charset problem supposedly in the W3C validator, it is now fine, but when I tried to validate on the Validome, I get back the original two errors that I had - Content-Script-Type and Content-Style-Type for no reason and there is still a charset problem there. There is certainly some kind of confliction of views between the two validators, so I guess its better to just stick to one...and in my case I think the W3C has been far nicer to me! Smile