Your SlideShare is downloading. ×
09-06-2011                                          [Invalid] Markup Validation of http://b…                              ...
09-06-2011                                [Invalid] Markup Validation of http://b…          One common cause for this erro...
09-06-2011                                [Invalid] Markup Validation of http://b…          vendor proprietary extensions ...
09-06-2011                     [Invalid] Markup Validation of http://b…        …"application/x-shockwave-flash" width= " 5...
09-06-2011                               [Invalid] Markup Validation of http://b…          flash.            Line 432, Col...
Upcoming SlideShare
Loading in...5
×

W3c markup validator

1,241

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,241
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of " W3c markup validator"

  1. 1. 09-06-2011 [Invalid] Markup Validation of http://b… Markup Validation Service Chec k the mar kup ( HTML, XHTML, …) of Web doc uments Jump To: Validation Output Errors found while checking this document as XHTML 1.0 Transitional! Result: 12 Errors Address : http://blogs.ua.pt/Euragora/ Encoding : utf-8 (detect automatically) XHTML 1.0 (detect automatically) Doctype : Transitional Root Element: html Root Namespace: http://www.w3.org/1999/xhtml The W3C validators are hosted on server technology donated by HP, and supported by community donations. Donate and help us build better tools for a better web. Options List Messages Sequentially Group Error Show Source Show Outline Messages by Type Clean up Markup with HTML-Tidy Validate error pages Verbose Output Help on the options is available. Revalidate ↑ TOP Validation Output: 12 Errors Line 58, Column 44: document type does not allow element "div" here ✉ … tip = $(<div class="tipsy" > <div class="tipsy-inner"> + $(this).at… The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).validator.w3.org/check?uri=http%3A… 1/5
  2. 2. 09-06-2011 [Invalid] Markup Validation of http://b… One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTMLs rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTMLs "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error). Line 148, Column 120: "allowfullscreen" is not a member of a group specified for any attribute ✉ …://www.youtube.com/embed/kO1D4jF7yX8" frameborder="0" allowfullscreen > </iframe> Line 238, Column 216: required attribute "alt" not specified ✉ …/blogs.ua.pt/Euragora/wp-content/uploads/2011/03/uniao-europeia.jpg" / > </a></p> The attribute given above is required for an element that youve 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> . Line 408, Column 69: there is no attribute "type" ✉ …o player" class="youtube-player" type= " text/html" width="425" height="344" src… 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. Line 408, Column 185: there is no attribute "allowFullScreen" ✉ …be.com/embed/tY7NN3CRdkE" frameborder="0" allowFullScreen= " true"> </iframe></p> 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 usingvalidator.w3.org/check?uri=http%3A… 2/5
  3. 3. 09-06-2011 [Invalid] Markup Validation of http://b… 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. Line 432, Column 237: there is no attribute "src" ✉ …ss" value="always"></param><embed src= " http://www.youtube.com/v/6-9nWt04oSI?ve… 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. Line 432, Column 291: there is no attribute "type" ✉ …ube.com/v/6-9nWt04oSI?version=3" type= " application/x-shockwave-flash" width="5… 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. Line 432, Column 329: there is no attribute "width" ✉validator.w3.org/check?uri=http%3A… 3/5
  4. 4. 09-06-2011 [Invalid] Markup Validation of http://b… …"application/x-shockwave-flash" width= " 500" height="400" allowscriptaccess="al… 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. Line 432, Column 342: there is no attribute "height" ✉ …x-shockwave-flash" width="500" height= " 400" allowscriptaccess="always" allowfu… 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. Line 432, Column 366: there is no attribute "allowscriptaccess" ✉ …="500" height="400" allowscriptaccess= " always" allowfullscreen="true"></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 validvalidator.w3.org/check?uri=http%3A… 4/5
  5. 5. 09-06-2011 [Invalid] Markup Validation of http://b… flash. Line 432, Column 391: there is no attribute "allowfullscreen" ✉ …t="400" allowscriptaccess="always" allowfullscreen= " true"></embed></object></p> 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. Line 432, Column 397: element "embed" undefined ✉ …t="400" allowscriptaccess="always" allowfullscreen="true" > </embed></object></p> 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). ↑ TOP Home About... News Docs Help & FAQ Feedback Contribute This service runs the W3C Markup Validator, v1.2+hg. COPYRIGHT © 1994-2011 W3C® (MIT, ERCIM, KEIO), ALL RIGHTS RESERVED. W3C LIABILITY, TRADEMARK, DOCUMENT USE AND SOFTWARE LICENSING RULES APPLY. YOUR INTERACTIONS WITH THIS SITE ARE IN ACCORDANCE WITH OUR PUBLIC AND MEMBER PRIVACY STATEMENTS.validator.w3.org/check?uri=http%3A… 5/5

×