Jump to content

My Validation Code


Html

Recommended Posts

Hi there.My page validates now with twenty five errors, it was nineteeen, but I had edited the "center" tags to centre. So that was the increase. Leaving that aside.The rest I'm notsure how to sort out.Thank you for the help.If this looks a mess down below, you can alternatively, Code validated

# Error Line 25, Column 8: element "centre" undefined. Did you mean "center" or "textarea"?<centre>✉You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).# Error Line 27, Column 49: end tag for "param" omitted, but OMITTAG NO was specified…"hdsubsurf4" value="hdsubsurf4.sw…✉You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".# Info Line 27: start tag was here><param name="hdsubsurf4" value="hdsubsurf4.swf"># Error Line 28, Column 12: Attribute "src" exists, but can not be used for this element.<embed src="hdsubsurf4.swf" width="300" height="300">✉You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.# Error Line 28, Column 35: Attribute "width" exists, but can not be used for this element.<embed src="hdsubsurf4.swf" width="300" height="300">✉You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.# Error Line 28, Column 48: Attribute "height" exists, but can not be used for this element.<embed src="hdsubsurf4.swf" width="300" height="300">✉You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.# Error Line 28, Column 53: element "embed" undefined. Did you mean "meta" or "em"?<embed src="hdsubsurf4.swf" width="300" height="300">✉You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).# Error Line 33, Column 8: element "centre" undefined. Did you mean "center" or "textarea"?<centre>✉You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).# Error Line 37, Column 8: element "centre" undefined. Did you mean "center" or "textarea"?<centre>✉You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).# Error Line 45, Column 8: element "centre" undefined. Did you mean "center" or "textarea"?<centre>✉You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).# Error Line 47, Column 164: required attribute "alt" not specified…ternet.co.uk/image.cgi?type=banner"/></a>✉The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.# Error Line 49, Column 8: element "centre" undefined. Did you mean "center" or "textarea"?<centre>✉You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).# Error Line 50, Column 218: end tag for "img" omitted, but OMITTAG NO was specified…Campaign for liberty image link"></a>✉You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".# Info Line 50, Column 44: start tag was here…="http://www.campaignforliberty.com"><img border="0" src="campaignforliberty.# Error Line 52, Column 8: element "centre" undefined. Did you mean "center" or "textarea"?<centre>✉You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).# Error Line 53, Column 306: end tag for "img" omitted, but OMITTAG NO was specified…s book" alt="RichardDawkins.net"></a>✉You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".# Info Line 53, Column 53: start tag was here…richarddawkins.net/" target="_blank"><img src="http://richarddawkins.net/bann# Error Line 30, Column 9: XML Parsing Error: Opening and ending tag mismatch: param line 27 and object</object>✉# Error Line 31, Column 9: XML Parsing Error: Opening and ending tag mismatch: object line 26 and centre</centre>✉# Error Line 50, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 50 and a…><img border="0" src="campaignforliberty.jpg" title="I'm not an American but …✉# Error Line 51, Column 9: XML Parsing Error: Opening and ending tag mismatch: a line 50 and centre</centre>✉# Error Line 53, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 53 and a…="_blank"><img src="http://richarddawkins.net/banners/392x72_RDFbanner.jpg" w…✉# Error Line 54, Column 9: XML Parsing Error: Opening and ending tag mismatch: a line 53 and centre</centre>✉# Error Line 56, Column 7: XML Parsing Error: Opening and ending tag mismatch: centre line 52 and body</body>✉# Error Line 57, Column 7: XML Parsing Error: Opening and ending tag mismatch: centre line 49 and html</html>✉# Error Line 57, Column 7: XML Parsing Error: Premature end of data in tag centre line 25</html>✉# Error Line 57, Column 7: XML Parsing Error: Premature end of data in tag body line 20</html>✉# Error Line 57, Column 7: XML Parsing Error: Premature end of data in tag html line 2</html>
Link to comment
Share on other sites

Your <param> tags aren't closed properly, some of your <img> tags aren't closed properly, <embed> is not a valid HTML element, all <img> elements require an alt attribute.

Link to comment
Share on other sites

no, you should. It's not about being a slave, it's just doing things the right way. did you learn about using the object tag instead of embed? What are your remaining errors?

Link to comment
Share on other sites

There are now six errors.

Validation Output: 6 Errors 1. Error Line 28, Column 68: Attribute "src" exists, but can not be used for this element. …urf4" value="hdsubsurf4.swf"></param><embed src="hdsubsurf4.swf" width="350" ✉ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 2. Error Line 28, Column 91: Attribute "width" exists, but can not be used for this element. …m><embed src="hdsubsurf4.swf" width="350" ✉ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 3. Error Line 29, Column 8: Attribute "height" exists, but can not be used for this element. height="300"></embed> ✉ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. 4. Error Line 29, Column 13: element "embed" undefined. Did you mean "meta" or "em"? height="300"></embed> ✉ You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: * incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case). 5. Error Line 47, Column > 80: XML Parsing Error: attributes construct error …k/aff.cgi?entry=sSQnd0IACBNQWHOfsBidIg"><img border="0" src="http://customer.… ✉ 6. Error Line 47, Column > 80: XML Parsing Error: Couldn't find end of Start Tag img line 47 …k/aff.cgi?entry=sSQnd0IACBNQWHOfsBidIg"><img border="0" src="http://customer.…
I haven't gotten anywhere with the flash object, I just restored it to its original code.At least my CSS validates. :) Well Ivory soap is only 99.4% pure. :)
Link to comment
Share on other sites

I tried that, it didn't work out.
It works for everybody else. The problem is that you most likely didn't understand it well and implemented it wrong. The Flash-Satay method cannot fail.
Link to comment
Share on other sites

It didn't work for me in IE or Firefox.The last piece of code is the complete one? I have skimmed read the page. Its a collection of well done this then done that.
You would do well in actually reading the article. That's the only way to learn things. I don't encourage going on as a web developer by simply copying and pasting code that you find around the place.
Link to comment
Share on other sites

<object width="350" height="300"><param name="hdsubsurf4" value="hdsubsurf4.swf"></param><embed src="hdsubsurf4.swf" width="350"height="300"></embed></object>

That is the one I am using. So I'd have to spend my time reading through all that just to achieve my web standards. I currently just don't have the patience. :)

Link to comment
Share on other sites

<object width="350" height="300"><param name="hdsubsurf4" value="hdsubsurf4.swf"></param><embed src="hdsubsurf4.swf" width="350"height="300"></embed></object>

That is the one I am using. So I'd have to spend my time reading through all that just to achieve my web standards. I currently just don't have the patience. :)

And that's the kind of attitude that will keep people from really wanting to help you out. People on this site are here (presumably) to learn, and for others to help them. We don't mind helping, but only if you want to learn. If you read the article, it actually takes a lot of time to help you understand why it is doing what it is doing. You wanted to know why you're page wasn't validating, and between the people who have posted and the article that was written, you have everything you need to know what the code is, but more importantly, to understand why. It's all too frustrating seeing people just trying to copy paste code without having any idea what it means or what it does. If it seems like we're being harsh, its because we emphasize good (read: standards compliant) habits, and a willingness to teach so that people may learn. Maybe you don't take this stuff seriously, so this kind of attention to detail may not mean much to you, but you did ask about how to make it standards compliant, and we pointed you in the right direction; not sure what was so hard about that.For the record, if you read the article, then you would have realized this is what an example of standards compliant, working code would look like.
<object type="application/x-shockwave-flash data="c.swf?path=movie.swf" width="400" height="300"><param name="movie" value="c.swf?path=movie.swf" /><img src="noflash.gif" width="200" height="100" alt="" /></object>

Link to comment
Share on other sites

No I don't think that what you've said was being harsh. Thats just my position thats all.I tried that example too.
That example will only work if you make a special flash file that goes with it. If you read thte article you'll understand.
Link to comment
Share on other sites

I see, that would mean using flash software. I had gotten someone on the web last year to do that for me, I had tried to do that myself, but the clips never worked. If I can't do this, then I'll have to leave it as it is. What else can I do?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...