Danny: Welcher Browser unterstuezt W3C am besten?

Beitrag lesen

Kein Wunder!

Ergebnis der W3C-Validators (nach Content-Typ-Fix):

Line 6, column 6: required attribute "TYPE" not specified

<style>

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>.

&#9993;

Line 62, column 135: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"

...bs/emo/BL/laugh.gif' ALIGN='absmiddle'> </td>

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the selected attribute must be either minimized as selected or spelled out in full as selected="selected"; a value like selected="true" is not allowed.

&#9993;

Line 62, column 136: required attribute "ALT" not specified

...s/emo/BL/laugh.gif' ALIGN='absmiddle'> </td>

&#9993;

Line 73, column 202: cannot generate system identifier for general entity "img"

....com/whitepages/online?icq=263083078&img=5" border="0"></a><br></td>

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 "&amp;" (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 &aelig; are different characters.

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.

&#9993;

Line 73, column 202: general entity "img" not defined and no default entity

....com/whitepages/online?icq=263083078&img=5" border="0"></a><br></td>

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.

&#9993;

Line 73, column 205: reference to entity "img" for which no system identifier could be generated

...m/whitepages/online?icq=263083078&img=5" border="0"></a><br></td>

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.

&#9993;

Line 73, column 201: entity was defined here

...q.com/whitepages/online?icq=263083078&img=5" border="0"></a><br></td>

Line 73, column 219: required attribute "ALT" not specified

...nline?icq=263083078&img=5" border="0"></a><br></td>

&#9993;

Line 74, column 166: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"

...s/emo/BL/biggrin.gif' ALIGN='absmiddle'></td>

&#9993;

Line 74, column 167: required attribute "ALT" not specified

.../emo/BL/biggrin.gif' ALIGN='absmiddle'></td>

&#9993;

Line 86, column 173: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"

.../gbs/emo/BL/love.gif' ALIGN='absmiddle'></td>

&#9993;

Line 86, column 174: required attribute "ALT" not specified

...gbs/emo/BL/love.gif' ALIGN='absmiddle'></td>

&#9993;

Line 110, column 193: reference to entity "img" for which no system identifier could be generated

...m/whitepages/online?icq=111049001&img=5" border="0"></a><br><a href="http://w

&#9993;

Line 73, column 201: entity was defined here

...q.com/whitepages/online?icq=263083078&img=5" border="0"></a><br></td>

Line 110, column 207: required attribute "ALT" not specified

...nline?icq=111049001&img=5" border="0"></a><br><a href="http://www.bastianschn

&#9993;

Line 111, column 183: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"

...bs/emo/BL/biggrin.gif' ALIGN='absmiddle'></td>

&#9993;

Line 111, column 184: required attribute "ALT" not specified

...s/emo/BL/biggrin.gif' ALIGN='absmiddle'></td>

&#9993;

Line 118, column 29: required attribute "TYPE" not specified

<script language="JavaScript">

&#9993;

Line 118, column 29: document type does not allow element "SCRIPT" here

<script language="JavaScript">

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).

&#9993;

Line 131, column 70: required attribute "TYPE" not specified

...ts.funpic.de/counter/count.php?username=admin2"></script>

&#9993;

Line 131, column 70: document type does not allow element "SCRIPT" here

...ts.funpic.de/counter/count.php?username=admin2"></script>

Fazit: Das Gästebuch ist totaler Müll!

Noch Fragen?