 Line 1, Column 1: no document type declaration; implying "" Line 1, Column 1: no document type declaration; implying ""- <html>The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
 Line 4, Column 67: an attribute value literal can occur in an attribute specification list only after a VI delimiter Line 4, Column 67: an attribute value literal can occur in an attribute specification list only after a VI delimiter- "
Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is 
attribute="value". Line 5, Column 49: document type does not allow element "META" here
 Line 5, Column 49: document type does not allow element "META" here>
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).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "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 6, Column 100: document type does not allow element "META" here
 Line 6, Column 100: document type does not allow element "META" here… content="Videos, Videos,Youtube Videos,watched now,recent videos,most viewed">
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).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "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 7, Column 53: NET-enabling start-tag requires SHORTTAG YES
 Line 7, Column 53: NET-enabling start-tag requires SHORTTAG YES/
For the current document, the validator interprets strings like 
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: 
W3C. In such cases, the solution is to put quotation marks around the value. Line 7, Column 53: document type does not allow element "LINK" here
 Line 7, Column 53: document type does not allow element "LINK" here/
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).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "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 9, Column 7: required attribute "TYPE" not specified
 Line 9, Column 7: required attribute "TYPE" not specified
 
No comments:
Post a Comment