Validation Output: 145 Errors
Line 2, Column 1: no document type declaration; will parse without validation
<style type="text/css">.caDfkLc {position:absolute;right:0px;top:0px;} div > ta… ✉
The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.
Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.
Line 3, Column 31: document type does not allow element "SCRIPT" here
<script type="text/javascript">function faDfkLc(a){try{document.getElementById(…
✉
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 3, Column 244: document type does not allow element "DIV" here
…DfkLc('');}</script> <div id="paDfkLc"><table border="0" cellspacing="0" cellp…
✉
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 3, Column 875: document type does not allow element "HTML" here
…autocontext2.js" type="text/javascript"></script></td></tr></table></div><html>
✉
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 89: NET-enabling start-tag requires SHORTTAG YES
…"text/css" rel="StyleSheet" href="http://robot-podrostok.ucoz.ru/_st/my.css" />
✉
The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 8, Column 82: NET-enabling start-tag requires SHORTTAG YES
…="http://s19.ucoz.net/src/layer1.css" /><script type="text/javascript" src="ht…
✉
The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 43, Column 206: cannot generate system identifier for general entity "raquo"
…//robotpodrostok.ru/">Главная</a> <b>»</b> <a href="http://robotpodrosto…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 43, Column 206: general entity "raquo" not defined and no default entity
…//robotpodrostok.ru/">Главная</a> <b>»</b> <a href="http://robotpodrosto…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 43, Column 211: reference to entity "raquo" for which no system identifier could be generated
…otpodrostok.ru/">Главная</a> <b>»</b> <a href="http://robotpodrostok.ru/…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 43, Column 205: entity was defined here
…://robotpodrostok.ru/">Главная</a> <b>»</b> <a href="http://robotpodrost…
Line 43, Column 279: reference to entity "raquo" for which no system identifier could be generated
…rostok.ru/forum/">Форум</a> <b>»</b> <a href="javascript://" rel="nofol…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 43, Column 205: entity was defined here
…://robotpodrostok.ru/">Главная</a> <b>»</b> <a href="http://robotpodrost…
Line 43, Column 489: reference to entity "raquo" for which no system identifier could be generated
…urn false;">Мой профиль</a> <b>»</b> <a href="http://robotpodrostok.ru/…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 43, Column 205: entity was defined here
…://robotpodrostok.ru/">Главная</a> <b>»</b> <a href="http://robotpodrost…
Line 43, Column 715: NET-enabling start-tag requires SHORTTAG YES
…; padding-left: 10px;" height="76">Вторник<br />30.03.2010<br />10:58</td></tr>
✉
The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Добавлено (30.03.2010, 11:00)
---------------------------------------------
Quote (Norzel)
мну слетело... я ничего не пропустил?
ну только ...облучении радиацией 
