Play the best free cartoon games at playtoongames.com. Play different kinds of ben 10 games, mario games, cartoon games, sonic games, transformers games, sponge bob games, kids games, toon games. ...

playtoongames.com
  • Domain Name
    playtoongames.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #24845
  • Page Size
    86 KB
  • Ip Address
    173.192.222.206
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    59 GIF, 2 JPG, 3 PNG

Website Meta Analysis

  • Title
    Play Toon Games - Play the best cartoon games
  • Meta Keyword
    playtoon games,ben 10 games,mario vs sonic racing games,spongebob games,power rangers games,cartoon games
  • Meta Description
    Play the best free cartoon games at playtoongames.com. Play different kinds of ben 10 games, mario games, cartoon games, sonic games, transformers games, sponge bob games, kids games, toon games.

Technical Analysis

  • Webserver
    Apache/2.2.3 (CentOS)
  • Ip Address
    173.192.222.206
  • Domain Age
    1 Years, 9 Months, 23 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from playtoongames.com.

HTML Analysis

  • date: Thu, 31 Jan 2013 09:28:20 GMT
  • server: Apache/2.2.3 (CentOS)
  • x-powered-by: PHP/5.1.6
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: max-age=2419200, public
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: PLAYTOONGAMES.COM
Created on: 19-Apr-11
Expires on: 19-Apr-13
Last Updated on: 19-Apr-11

Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS1.PLAYTOONGAMES.COM
NS2.PLAYTOONGAMES.COM

DNS Analysis


DNS servers
ns2.playtoongames.com [173.192.222.206]
ns1.playtoongames.com [173.192.222.206]


DNS Records

Answer records
playtoongames.com MX
preference: 10
exchange: mail.playtoongames.com
86400s
playtoongames.com TXT v=spf1 +a +mx -all 86400s
playtoongames.com SOA
server: ns.playtoongames.com
email: admin@mpdedicated.com
serial: 1303480808
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
playtoongames.com NS  ns2.playtoongames.com 86400s
playtoongames.com NS  ns.playtoongames.com 86400s
playtoongames.com NS  ns1.playtoongames.com 86400s
playtoongames.com A 173.192.222.206 86400s

Authority records

Additional records
mail.playtoongames.com A 173.192.222.206 86400s
ns.playtoongames.com A 173.192.222.206 86400s

IP 173.192.222.206 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Dallas
  • Continent Code
    75207
  • Latitude
    214
  • Longitude
    623
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 173.192.222.206"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=173.192.222.206?showDetails=true&showARIN=false&ext=netref2
    #

    SoftLayer Technologies Inc. SOFTLAYER-4-8 (NET-173-192-0-0-1) 173.192.0.0 - 173.193.255.255
    Hosting Services Inc. NET-173-192-222-192 (NET-173-192-222-192-1) 173.192.222.192 - 173.192.222.223


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 187 Errors
  • 72 Warnings
Ratio Text/Html
  • 0.7250286700503004
Message Error
  • Warning Line 44, Column 95: cannot generate system identifier for general entity "block"
    …4game.com/www/delivery/edito.php?zones=26680&block=1&blockcampaign=1'></script>

    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.

    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.

  • Error Line 44, Column 95: general entity "block" not defined and no default entity
    …4game.com/www/delivery/edito.php?zones=26680&block=1&blockcampaign=1'></script>

    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.

  • Error Line 44, Column 100: reference to entity "block" for which no system identifier could be generated
    …4game.com/www/delivery/edito.php?zones=26680&block=1&blockcampaign=1'></script>

    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.

  • Info Line 44, Column 94: entity was defined here
    …4game.com/www/delivery/edito.php?zones=26680&block=1&blockcampaign=1'></script>
  • Warning Line 44, Column 103: cannot generate system identifier for general entity "blockcampaign"
    …4game.com/www/delivery/edito.php?zones=26680&block=1&blockcampaign=1'></script>

    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.

    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.

  • Error Line 44, Column 103: general entity "blockcampaign" not defined and no default entity
    …4game.com/www/delivery/edito.php?zones=26680&block=1&blockcampaign=1'></script>

    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.

  • Error Line 44, Column 116: reference to entity "blockcampaign" for which no system identifier could be generated
    …4game.com/www/delivery/edito.php?zones=26680&block=1&blockcampaign=1'></script>

    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.

  • Info Line 44, Column 102: entity was defined here
    …4game.com/www/delivery/edito.php?zones=26680&block=1&blockcampaign=1'></script>
  • Warning Line 67, Column 91: cannot generate system identifier for general entity "rotateur"
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=36761"></script>

    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.

    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.

  • Error Line 67, Column 91: general entity "rotateur" not defined and no default entity
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=36761"></script>

    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.

  • Error Line 67, Column 99: reference to entity "rotateur" for which no system identifier could be generated
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=36761"></script>

    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.

  • Info Line 67, Column 90: entity was defined here
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=36761"></script>
  • Error Line 69, Column 193: delimiter """ invalid: only S separators and TAGC allowed here
    …eA5z58737&channel=0&cb=" + new Date().getTime() + "'></scri" + "pt>");</script>
  • Error Line 69, Column 193: end tag for element "SCRI" which is not open
    …eA5z58737&channel=0&cb=" + new Date().getTime() + "'></scri" + "pt>");</script>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 146, Column 8: element "CENTER" undefined
    <center>

    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).
  • Warning Line 149, Column 88: NET-enabling start-tag requires SHORTTAG YES
    …://www.playtoongames.com/wtsFlags.css"/><!--WTS_NOT_TRANSLATE_START--><a href=…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 149, Column 88: document type does not allow element "LINK" here
    …://www.playtoongames.com/wtsFlags.css"/><!--WTS_NOT_TRANSLATE_START--><a href=…

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

  • Warning Line 149, Column 278: NET-enabling start-tag requires SHORTTAG YES
    …://www.playtoongames.com/wtsClear.gif'/></a><a href='http://www.playtoongames.…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 149, Column 447: NET-enabling start-tag requires SHORTTAG YES
    …://www.playtoongames.com/wtsClear.gif'/></a><a href='http://www.playtoongames.…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 149, Column 618: NET-enabling start-tag requires SHORTTAG YES
    …://www.playtoongames.com/wtsClear.gif'/></a><a href='http://www.playtoongames.…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 149, Column 785: NET-enabling start-tag requires SHORTTAG YES
    …://www.playtoongames.com/wtsClear.gif'/></a><a href='http://www.playtoongames.…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 149, Column 952: NET-enabling start-tag requires SHORTTAG YES
    …://www.playtoongames.com/wtsClear.gif'/></a><a href='http://www.playtoongames.…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 149, Column 1117: NET-enabling start-tag requires SHORTTAG YES
    …c='http://www.playtoongames.com/wtsClear.gif'/></a><!--WTS_NOT_TRANSLATE_END-->

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 153, Column 8: required attribute "TYPE" not specified
    <script>(function(d, s, id) {

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

  • Warning Line 181, Column 128: NET-enabling start-tag requires SHORTTAG YES
    …://www.playtoongames.com/members/avatar/no-avatar.jpg' width='50' height='50'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 181, Column 128: required attribute "ALT" not specified
    …://www.playtoongames.com/members/avatar/no-avatar.jpg' width='50' height='50'/>

    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 184, Column 161: there is no attribute "ALIGN"
    …png' width='15px' height='15px' align='absmiddle' />&nbsp;<input type='text' n…

    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.

  • Warning Line 184, Column 173: NET-enabling start-tag requires SHORTTAG YES
    …15px' height='15px' align='absmiddle' />&nbsp;<input type='text' name='usernam…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 184, Column 173: required attribute "ALT" not specified
    …15px' height='15px' align='absmiddle' />&nbsp;<input type='text' name='usernam…

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

  • Warning Line 184, Column 262: NET-enabling start-tag requires SHORTTAG YES
    …e='text' name='username' style='width:170px; border: 2px solid #efb9ff'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 185, Column 172: NET-enabling start-tag requires SHORTTAG YES
    …'15px' height='15px' align='absmiddle'/>&nbsp;<input type='password' name='pwd…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 185, Column 172: required attribute "ALT" not specified
    …'15px' height='15px' align='absmiddle'/>&nbsp;<input type='password' name='pwd…

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

  • Warning Line 185, Column 260: NET-enabling start-tag requires SHORTTAG YES
    …pe='password' name='pwd' style='width:170px; border: 2px solid #efb9ff'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 186, Column 48: there is no attribute "ALIGN"
    …                           <div align='center' class='login'><b><a href='http:…

    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.

  • Warning Line 186, Column 231: NET-enabling start-tag requires SHORTTAG YES
    …mit' name='login_btn' value='Sign In' style='border: 2px solid #efb9ff'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 188, Column 35: end tag for "DIV" omitted, but its declaration does not permit this
                                </form>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 183, Column 33: start tag was here
                                    <div style='float:left; width:200px; margin-lef…
  • Warning Line 192, Column 90: NET-enabling start-tag requires SHORTTAG YES
    …input type='text' name='search' style='border: 2px solid #efb9ff;width:110px'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 193, Column 115: "TIMES" is not a member of a group specified for any attribute
    … #efb9ff; font-family:Georgia, 'Times New Roman', Times, serif;' value='Search…
  • Error Line 193, Column 119: "NEW" is not a member of a group specified for any attribute
    …efb9ff; font-family:Georgia, 'Times New Roman', Times, serif;' value='Search'/>
  • Error Line 193, Column 124: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …efb9ff; font-family:Georgia, 'Times New Roman', Times, serif;' value='Search'/>

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Warning Line 194, Column 106: NET-enabling start-tag requires SHORTTAG YES
    … name='searchType' value='games' checked='checked' style="visibility:hidden"/> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 263, Column 13: ID "MENU" already defined
        <ul id="menu">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 249, Column 13: ID "MENU" first defined here
        <ul id="menu">
  • Error Line 291, Column 28: element "CENTER" undefined
                        <center>

    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).
  • Warning Line 326, Column 206: NET-enabling start-tag requires SHORTTAG YES
    …5_A.gif' width='150' height='112' class='thumb' alt='Avatar Bmx Racing'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 326, Column 213: end tag for "A" omitted, but its declaration does not permit this
    …5_A.gif' width='150' height='112' class='thumb' alt='Avatar Bmx Racing'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 326, Column 1: start tag was here
    <a href='http://www.playtoongames.com/play/Avatar_Bmx_Racing'><img src='http://…
  • Error Line 327, Column 153: end tag for element "A" which is not open
    …ne; font-weight:bold'>Avatar Bmx Racing</div></a></div></div><!-- Variables -->

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 342, Column 193: NET-enabling start-tag requires SHORTTAG YES
    …_650x420.gif' width='150' height='112' class='thumb' alt='Lego Ironman'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 342, Column 200: end tag for "A" omitted, but its declaration does not permit this
    …_650x420.gif' width='150' height='112' class='thumb' alt='Lego Ironman'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 342, Column 1: start tag was here
    <a href='http://www.playtoongames.com/play/Lego_Ironman'><img src='http://www.p…
  • Error Line 343, Column 148: end tag for element "A" which is not open
    …on:none; font-weight:bold'>Lego Ironman</div></a></div></div><!-- Variables -->

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 358, Column 206: NET-enabling start-tag requires SHORTTAG YES
    …00.gif' width='150' height='112' class='thumb' alt='Mario Tractor 2013'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 358, Column 213: end tag for "A" omitted, but its declaration does not permit this
    …00.gif' width='150' height='112' class='thumb' alt='Mario Tractor 2013'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 358, Column 1: start tag was here
    <a href='http://www.playtoongames.com/play/Mario_Tractor_2013'><img src='http:/…
  • Error Line 359, Column 154: end tag for element "A" which is not open
    …e; font-weight:bold'>Mario Tractor 2013</div></a></div></div><!-- Variables -->

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 371, Column 258: NET-enabling start-tag requires SHORTTAG YES
    …75_600x400.gif' width='150' height='112' class='thumb' alt='Super Zero'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 371, Column 265: end tag for "A" omitted, but its declaration does not permit this
    …75_600x400.gif' width='150' height='112' class='thumb' alt='Super Zero'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 371, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 372, Column 146: end tag for element "A" which is not open
    …:#000000; text-decoration:none; font-weight:bold'>Super Zero</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 386, Column 259: NET-enabling start-tag requires SHORTTAG YES
    …5_180x135.jpg' width='150' height='112' class='thumb' alt='Toon Racing'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 386, Column 266: end tag for "A" omitted, but its declaration does not permit this
    …5_180x135.jpg' width='150' height='112' class='thumb' alt='Toon Racing'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 386, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 387, Column 147: end tag for element "A" which is not open
    …#000000; text-decoration:none; font-weight:bold'>Toon Racing</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 401, Column 264: NET-enabling start-tag requires SHORTTAG YES
    …736x489.gif' width='150' height='112' class='thumb' alt='Bad Piggies 2'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 401, Column 271: end tag for "A" omitted, but its declaration does not permit this
    …736x489.gif' width='150' height='112' class='thumb' alt='Bad Piggies 2'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 401, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 402, Column 149: end tag for element "A" which is not open
    …00000; text-decoration:none; font-weight:bold'>Bad Piggies 2</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 416, Column 269: NET-enabling start-tag requires SHORTTAG YES
    …tled-3.gif' width='150' height='112' class='thumb' alt='Oggy The Racer'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 416, Column 276: end tag for "A" omitted, but its declaration does not permit this
    …tled-3.gif' width='150' height='112' class='thumb' alt='Oggy The Racer'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 416, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 417, Column 150: end tag for element "A" which is not open
    …0000; text-decoration:none; font-weight:bold'>Oggy The Racer</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 431, Column 272: NET-enabling start-tag requires SHORTTAG YES
    … 135.GIF' width='150' height='112' class='thumb' alt='Ben10 Bike Champ'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 431, Column 279: end tag for "A" omitted, but its declaration does not permit this
    … 135.GIF' width='150' height='112' class='thumb' alt='Ben10 Bike Champ'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 431, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 432, Column 152: end tag for element "A" which is not open
    …00; text-decoration:none; font-weight:bold'>Ben10 Bike Champ</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 446, Column 262: NET-enabling start-tag requires SHORTTAG YES
    …_180x135.gif' width='150' height='112' class='thumb' alt='Sgt.Mayhem  '/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 446, Column 269: end tag for "A" omitted, but its declaration does not permit this
    …_180x135.gif' width='150' height='112' class='thumb' alt='Sgt.Mayhem  '/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 446, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 447, Column 148: end tag for element "A" which is not open
    …000000; text-decoration:none; font-weight:bold'>Sgt.Mayhem  </div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 461, Column 269: NET-enabling start-tag requires SHORTTAG YES
    …tled-3.gif' width='150' height='112' class='thumb' alt='Bad Piggies HD'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 461, Column 276: end tag for "A" omitted, but its declaration does not permit this
    …tled-3.gif' width='150' height='112' class='thumb' alt='Bad Piggies HD'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 461, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 462, Column 150: end tag for element "A" which is not open
    …0000; text-decoration:none; font-weight:bold'>Bad Piggies HD</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 476, Column 265: NET-enabling start-tag requires SHORTTAG YES
    …80x135.gif' width='150' height='112' class='thumb' alt='Christmas Race'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 476, Column 272: end tag for "A" omitted, but its declaration does not permit this
    …80x135.gif' width='150' height='112' class='thumb' alt='Christmas Race'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 476, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 477, Column 150: end tag for element "A" which is not open
    …0000; text-decoration:none; font-weight:bold'>Christmas Race</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 491, Column 264: NET-enabling start-tag requires SHORTTAG YES
    …650.480.gif' width='150' height='112' class='thumb' alt='Birdy Bicycle'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 491, Column 271: end tag for "A" omitted, but its declaration does not permit this
    …650.480.gif' width='150' height='112' class='thumb' alt='Birdy Bicycle'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 491, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 492, Column 149: end tag for element "A" which is not open
    …00000; text-decoration:none; font-weight:bold'>Birdy Bicycle</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 506, Column 255: NET-enabling start-tag requires SHORTTAG YES
    …45_sog.gif' width='150' height='112' class='thumb' alt='Ben10 Vs Santa'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 506, Column 262: end tag for "A" omitted, but its declaration does not permit this
    …45_sog.gif' width='150' height='112' class='thumb' alt='Ben10 Vs Santa'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 506, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 507, Column 150: end tag for element "A" which is not open
    …0000; text-decoration:none; font-weight:bold'>Ben10 Vs Santa</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 521, Column 256: NET-enabling start-tag requires SHORTTAG YES
    …0x75_ptg2.gif' width='150' height='112' class='thumb' alt='Mario ATV 2'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 521, Column 263: end tag for "A" omitted, but its declaration does not permit this
    …0x75_ptg2.gif' width='150' height='112' class='thumb' alt='Mario ATV 2'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 521, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 522, Column 147: end tag for element "A" which is not open
    …#000000; text-decoration:none; font-weight:bold'>Mario ATV 2</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 536, Column 292: NET-enabling start-tag requires SHORTTAG YES
    …th='150' height='112' class='thumb' alt='Sponge Bob Christmas Delivery'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 536, Column 299: end tag for "A" omitted, but its declaration does not permit this
    …th='150' height='112' class='thumb' alt='Sponge Bob Christmas Delivery'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 536, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 537, Column 165: end tag for element "A" which is not open
    …ration:none; font-weight:bold'>Sponge Bob Christmas Delivery</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 551, Column 256: NET-enabling start-tag requires SHORTTAG YES
    …00x75_ptg.gif' width='150' height='112' class='thumb' alt='Santa Drive'/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 551, Column 263: end tag for "A" omitted, but its declaration does not permit this
    …00x75_ptg.gif' width='150' height='112' class='thumb' alt='Santa Drive'/></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 551, Column 69: start tag was here
    …ass='thumbNailBG'><div align='center'><a href='http://www.playtoongames.com/pl…
  • Error Line 552, Column 147: end tag for element "A" which is not open
    …#000000; text-decoration:none; font-weight:bold'>Santa Drive</div></a></div>   

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 557, Column 28: element "CENTER" undefined
                        <center>

    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).
  • Warning Line 582, Column 232: NET-enabling start-tag requires SHORTTAG YES
    …x75_PTG.gif' width='150' height='112' class='thumb' alt='Crazy Monster Truck'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 583, Column 174: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …ecoration:none; font-weight:bold; margin-top:1px">Crazy Monster Truck</a></div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 583, Column 197: end tag for "DIV" omitted, but its declaration does not permit this
    …ecoration:none; font-weight:bold; margin-top:1px">Crazy Monster Truck</a></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 583, Column 33: start tag was here
                                    <div align='center' style="font:Verdana, Arial,…
  • Warning Line 593, Column 239: NET-enabling start-tag requires SHORTTAG YES
    …Sky Impact.gif' width='150' height='112' class='thumb' alt='Sonic Sky Impact'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 594, Column 174: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …t-decoration:none; font-weight:bold; margin-top:1px">Sonic Sky Impact</a></div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 594, Column 194: end tag for "DIV" omitted, but its declaration does not permit this
    …t-decoration:none; font-weight:bold; margin-top:1px">Sonic Sky Impact</a></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 594, Column 33: start tag was here
                                    <div align='center' style="font:Verdana, Arial,…
  • Warning Line 604, Column 210: NET-enabling start-tag requires SHORTTAG YES
    …/978696_100x75_rog.gif' width='150' height='112' class='thumb' alt='Kawairun'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 605, Column 174: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …000; text-decoration:none; font-weight:bold; margin-top:1px">Kawairun</a></div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 605, Column 186: end tag for "DIV" omitted, but its declaration does not permit this
    …000; text-decoration:none; font-weight:bold; margin-top:1px">Kawairun</a></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 605, Column 33: start tag was here
                                    <div align='center' style="font:Verdana, Arial,…
  • Warning Line 615, Column 242: NET-enabling start-tag requires SHORTTAG YES
    …og.gif' width='150' height='112' class='thumb' alt='Legend Of The Wu Sisters'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 616, Column 174: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …tion:none; font-weight:bold; margin-top:1px">Legend Of The Wu Sisters</a></div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 616, Column 202: end tag for "DIV" omitted, but its declaration does not permit this
    …tion:none; font-weight:bold; margin-top:1px">Legend Of The Wu Sisters</a></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 616, Column 33: start tag was here
                                    <div align='center' style="font:Verdana, Arial,…
  • Warning Line 626, Column 236: NET-enabling start-tag requires SHORTTAG YES
    …5_rog.gif' width='150' height='112' class='thumb' alt=' Doraemon Tank Attack'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 627, Column 174: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …oration:none; font-weight:bold; margin-top:1px"> Doraemon Tank Attack</a></div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 627, Column 199: end tag for "DIV" omitted, but its declaration does not permit this
    …oration:none; font-weight:bold; margin-top:1px"> Doraemon Tank Attack</a></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 627, Column 33: start tag was here
                                    <div align='center' style="font:Verdana, Arial,…
  • Warning Line 637, Column 218: NET-enabling start-tag requires SHORTTAG YES
    …422_100x75_rog.gif' width='150' height='112' class='thumb' alt='Tigress Jump'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 638, Column 174: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    … text-decoration:none; font-weight:bold; margin-top:1px">Tigress Jump</a></div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 638, Column 190: end tag for "DIV" omitted, but its declaration does not permit this
    … text-decoration:none; font-weight:bold; margin-top:1px">Tigress Jump</a></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 638, Column 33: start tag was here
                                    <div align='center' style="font:Verdana, Arial,…
  • Error Line 646, Column 26: end tag for element "DIV" which is not open
                        </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 650, Column 33: end tag for element "DIV" which is not open
                               </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 652, Column 26: end tag for element "DIV" which is not open
                        </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 654, Column 24: end tag for element "DIV" which is not open
                      </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 655, Column 22: end tag for element "DIV" which is not open
                    </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 667, Column 14: end tag for element "DIV" which is not open
            </div>        

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 684, Column 259: NET-enabling start-tag requires SHORTTAG YES
    …ge-rog.gif' width='150' height='112' class='thumb' alt='Naruto Bmx Challenge'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 685, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …:none; font-weight:bold; margin-top:1px">Naruto Bmx Challenge</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 685, Column 197: end tag for "DIV" omitted, but its declaration does not permit this
    …:none; font-weight:bold; margin-top:1px">Naruto Bmx Challenge</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 685, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Warning Line 695, Column 268: NET-enabling start-tag requires SHORTTAG YES
    …p.gif' width='150' height='112' class='thumb' alt='Johnny Bravo Soccer Champ'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 696, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Johnny Bravo Soccer Champ</a>        </…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 696, Column 202: end tag for "DIV" omitted, but its declaration does not permit this
    …; font-weight:bold; margin-top:1px">Johnny Bravo Soccer Champ</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 696, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Warning Line 706, Column 236: NET-enabling start-tag requires SHORTTAG YES
    …x75_PTG.gif' width='150' height='112' class='thumb' alt='Crazy Monster Truck'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 707, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …n:none; font-weight:bold; margin-top:1px">Crazy Monster Truck</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 707, Column 196: end tag for "DIV" omitted, but its declaration does not permit this
    …n:none; font-weight:bold; margin-top:1px">Crazy Monster Truck</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 707, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Warning Line 717, Column 240: NET-enabling start-tag requires SHORTTAG YES
    …5_rog.gif' width='150' height='112' class='thumb' alt=' Doraemon Tank Attack'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 718, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …none; font-weight:bold; margin-top:1px"> Doraemon Tank Attack</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 718, Column 198: end tag for "DIV" omitted, but its declaration does not permit this
    …none; font-weight:bold; margin-top:1px"> Doraemon Tank Attack</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 718, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Warning Line 728, Column 218: NET-enabling start-tag requires SHORTTAG YES
    …31128_100x75_rog.gif' width='150' height='112' class='thumb' alt='Ben 10 BMX'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 729, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …decoration:none; font-weight:bold; margin-top:1px">Ben 10 BMX</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 729, Column 187: end tag for "DIV" omitted, but its declaration does not permit this
    …decoration:none; font-weight:bold; margin-top:1px">Ben 10 BMX</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 729, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 734, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 739, Column 244: NET-enabling start-tag requires SHORTTAG YES
    …rog.gif' width='150' height='112' class='thumb' alt='Super Mario Truck Rider'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 740, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Super Mario Truck Rider</a>        </di…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 740, Column 200: end tag for "DIV" omitted, but its declaration does not permit this
    …ne; font-weight:bold; margin-top:1px">Super Mario Truck Rider</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 740, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 745, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 750, Column 244: NET-enabling start-tag requires SHORTTAG YES
    …PTG.gif' width='150' height='112' class='thumb' alt='Ben10 Upgrade Vs Aliens'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 751, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Ben10 Upgrade Vs Aliens</a>        </di…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 751, Column 200: end tag for "DIV" omitted, but its declaration does not permit this
    …ne; font-weight:bold; margin-top:1px">Ben10 Upgrade Vs Aliens</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 751, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 756, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 761, Column 250: NET-enabling start-tag requires SHORTTAG YES
    ….gif' width='150' height='112' class='thumb' alt='Batman Dynamic Double Team'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 762, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Batman Dynamic Double Team</a>        <…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 762, Column 203: end tag for "DIV" omitted, but its declaration does not permit this
    … font-weight:bold; margin-top:1px">Batman Dynamic Double Team</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 762, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 767, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 772, Column 238: NET-enabling start-tag requires SHORTTAG YES
    …75_rog.gif' width='150' height='112' class='thumb' alt='Ben10 in Mario World'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 773, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …:none; font-weight:bold; margin-top:1px">Ben10 in Mario World</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 773, Column 197: end tag for "DIV" omitted, but its declaration does not permit this
    …:none; font-weight:bold; margin-top:1px">Ben10 in Mario World</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 773, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 778, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 783, Column 235: NET-enabling start-tag requires SHORTTAG YES
    …apaign_Icon_N.gif' width='150' height='112' class='thumb' alt='Campaign Race'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 784, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …oration:none; font-weight:bold; margin-top:1px">Campaign Race</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 784, Column 190: end tag for "DIV" omitted, but its declaration does not permit this
    …oration:none; font-weight:bold; margin-top:1px">Campaign Race</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 784, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 789, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 794, Column 219: NET-enabling start-tag requires SHORTTAG YES
    …360098_180x135.gif' width='150' height='112' class='thumb' alt='Zombie Racer'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 795, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …coration:none; font-weight:bold; margin-top:1px">Zombie Racer</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 795, Column 189: end tag for "DIV" omitted, but its declaration does not permit this
    …coration:none; font-weight:bold; margin-top:1px">Zombie Racer</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 795, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 800, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 805, Column 237: NET-enabling start-tag requires SHORTTAG YES
    …75_ptg2.gif' width='150' height='112' class='thumb' alt='Ben 10 Street Stunt'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 806, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …n:none; font-weight:bold; margin-top:1px">Ben 10 Street Stunt</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 806, Column 196: end tag for "DIV" omitted, but its declaration does not permit this
    …n:none; font-weight:bold; margin-top:1px">Ben 10 Street Stunt</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 806, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 811, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 815, Column 30: end tag for element "DIV" which is not open
                            </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 816, Column 26: end tag for element "DIV" which is not open
                        </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 817, Column 24: end tag for element "DIV" which is not open
                      </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 839, Column 268: NET-enabling start-tag requires SHORTTAG YES
    …p.gif' width='150' height='112' class='thumb' alt='Johnny Bravo Soccer Champ'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 840, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Johnny Bravo Soccer Champ</a>        </…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 840, Column 202: end tag for "DIV" omitted, but its declaration does not permit this
    …; font-weight:bold; margin-top:1px">Johnny Bravo Soccer Champ</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 840, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Warning Line 850, Column 242: NET-enabling start-tag requires SHORTTAG YES
    …rog 2.gif' width='150' height='112' class='thumb' alt='Mario Vs Sonic Racing'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 851, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …none; font-weight:bold; margin-top:1px">Mario Vs Sonic Racing</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 851, Column 198: end tag for "DIV" omitted, but its declaration does not permit this
    …none; font-weight:bold; margin-top:1px">Mario Vs Sonic Racing</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 851, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Warning Line 861, Column 226: NET-enabling start-tag requires SHORTTAG YES
    …7_100x75_rog.gif' width='150' height='112' class='thumb' alt='Pokemon Rescue'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 862, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …ration:none; font-weight:bold; margin-top:1px">Pokemon Rescue</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 862, Column 191: end tag for "DIV" omitted, but its declaration does not permit this
    …ration:none; font-weight:bold; margin-top:1px">Pokemon Rescue</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 862, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Warning Line 872, Column 237: NET-enabling start-tag requires SHORTTAG YES
    …75_ptg2.gif' width='150' height='112' class='thumb' alt='Ben 10 Street Stunt'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 873, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …n:none; font-weight:bold; margin-top:1px">Ben 10 Street Stunt</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 873, Column 196: end tag for "DIV" omitted, but its declaration does not permit this
    …n:none; font-weight:bold; margin-top:1px">Ben 10 Street Stunt</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 873, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 878, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 883, Column 230: NET-enabling start-tag requires SHORTTAG YES
    …100x75_rog.gif' width='150' height='112' class='thumb' alt='Ben10 Power Jump'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 884, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …tion:none; font-weight:bold; margin-top:1px">Ben10 Power Jump</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 884, Column 193: end tag for "DIV" omitted, but its declaration does not permit this
    …tion:none; font-weight:bold; margin-top:1px">Ben10 Power Jump</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 884, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 889, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 894, Column 246: NET-enabling start-tag requires SHORTTAG YES
    …og.gif' width='150' height='112' class='thumb' alt='Incredibles Save The Day'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 895, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Incredibles Save The Day</a>        </d…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 895, Column 201: end tag for "DIV" omitted, but its declaration does not permit this
    …e; font-weight:bold; margin-top:1px">Incredibles Save The Day</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 895, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 900, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 905, Column 218: NET-enabling start-tag requires SHORTTAG YES
    …31128_100x75_rog.gif' width='150' height='112' class='thumb' alt='Ben 10 BMX'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 906, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …decoration:none; font-weight:bold; margin-top:1px">Ben 10 BMX</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 906, Column 187: end tag for "DIV" omitted, but its declaration does not permit this
    …decoration:none; font-weight:bold; margin-top:1px">Ben 10 BMX</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 906, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 911, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 916, Column 242: NET-enabling start-tag requires SHORTTAG YES
    …80x135.gif' width='150' height='112' class='thumb' alt='Mario Bike Challenge'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 917, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …:none; font-weight:bold; margin-top:1px">Mario Bike Challenge</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 917, Column 197: end tag for "DIV" omitted, but its declaration does not permit this
    …:none; font-weight:bold; margin-top:1px">Mario Bike Challenge</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 917, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 922, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 927, Column 246: NET-enabling start-tag requires SHORTTAG YES
    …TG.gif' width='150' height='112' class='thumb' alt='Ben10 Vs Rex Truck Champ'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 928, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Ben10 Vs Rex Truck Champ</a>        </d…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 928, Column 201: end tag for "DIV" omitted, but its declaration does not permit this
    …e; font-weight:bold; margin-top:1px">Ben10 Vs Rex Truck Champ</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 928, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 933, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 938, Column 246: NET-enabling start-tag requires SHORTTAG YES
    …og.gif' width='150' height='112' class='thumb' alt='Legend Of The Wu Sisters'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 939, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Legend Of The Wu Sisters</a>        </d…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 939, Column 201: end tag for "DIV" omitted, but its declaration does not permit this
    …e; font-weight:bold; margin-top:1px">Legend Of The Wu Sisters</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 939, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 944, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 949, Column 244: NET-enabling start-tag requires SHORTTAG YES
    …PTG.gif' width='150' height='112' class='thumb' alt='Ben 10 Aliens Kill Zone'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 950, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Ben 10 Aliens Kill Zone</a>        </di…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 950, Column 200: end tag for "DIV" omitted, but its declaration does not permit this
    …ne; font-weight:bold; margin-top:1px">Ben 10 Aliens Kill Zone</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 950, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 955, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 960, Column 224: NET-enabling start-tag requires SHORTTAG YES
    …523_rog2mrio.gif' width='150' height='112' class='thumb' alt='Mario Beatdown'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 961, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …ration:none; font-weight:bold; margin-top:1px">Mario Beatdown</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 961, Column 191: end tag for "DIV" omitted, but its declaration does not permit this
    …ration:none; font-weight:bold; margin-top:1px">Mario Beatdown</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 961, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 966, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 971, Column 232: NET-enabling start-tag requires SHORTTAG YES
    …00x75_ptg.gif' width='150' height='112' class='thumb' alt='Sonic Racing Zone'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 972, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …ion:none; font-weight:bold; margin-top:1px">Sonic Racing Zone</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 972, Column 194: end tag for "DIV" omitted, but its declaration does not permit this
    …ion:none; font-weight:bold; margin-top:1px">Sonic Racing Zone</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 972, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 977, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 982, Column 234: NET-enabling start-tag requires SHORTTAG YES
    …0x75_rog.gif' width='150' height='112' class='thumb' alt='Tom N Jerry Frenzy'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 983, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …on:none; font-weight:bold; margin-top:1px">Tom N Jerry Frenzy</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 983, Column 195: end tag for "DIV" omitted, but its declaration does not permit this
    …on:none; font-weight:bold; margin-top:1px">Tom N Jerry Frenzy</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 983, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 988, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 993, Column 224: NET-enabling start-tag requires SHORTTAG YES
    …51_100x75_PTG.gif' width='150' height='112' class='thumb' alt='Ben10 Rampage'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 994, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …oration:none; font-weight:bold; margin-top:1px">Ben10 Rampage</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 994, Column 190: end tag for "DIV" omitted, but its declaration does not permit this
    …oration:none; font-weight:bold; margin-top:1px">Ben10 Rampage</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 994, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 999, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 1004, Column 246: NET-enabling start-tag requires SHORTTAG YES
    …og.gif' width='150' height='112' class='thumb' alt='Johnny Bravo Beach Stunt'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1005, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Johnny Bravo Beach Stunt</a>        </d…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1005, Column 201: end tag for "DIV" omitted, but its declaration does not permit this
    …e; font-weight:bold; margin-top:1px">Johnny Bravo Beach Stunt</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1005, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 1010, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 1015, Column 236: NET-enabling start-tag requires SHORTTAG YES
    …10VSREX_Secure.gif' width='150' height='112' class='thumb' alt='Ben10 Vs Rex'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1016, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …coration:none; font-weight:bold; margin-top:1px">Ben10 Vs Rex</a>        </div>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1016, Column 189: end tag for "DIV" omitted, but its declaration does not permit this
    …coration:none; font-weight:bold; margin-top:1px">Ben10 Vs Rex</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1016, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 1021, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 1026, Column 262: NET-enabling start-tag requires SHORTTAG YES
    …f' width='150' height='112' class='thumb' alt='KungFu Panda Racing Challenge'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1027, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">KungFu Panda Racing Challenge</a>      …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1027, Column 206: end tag for "DIV" omitted, but its declaration does not permit this
    …nt-weight:bold; margin-top:1px">KungFu Panda Racing Challenge</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1027, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 1032, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 1037, Column 242: NET-enabling start-tag requires SHORTTAG YES
    …_ptg.gif' width='150' height='112' class='thumb' alt='Ben 10 Super Stunt BMX'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1038, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Ben 10 Super Stunt BMX</a>        </div…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1038, Column 199: end tag for "DIV" omitted, but its declaration does not permit this
    …one; font-weight:bold; margin-top:1px">Ben 10 Super Stunt BMX</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1038, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 1043, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 1048, Column 244: NET-enabling start-tag requires SHORTTAG YES
    …PTG.gif' width='150' height='112' class='thumb' alt='Ben10 Upgrade Vs Aliens'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1049, Column 173: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …one; font-weight:bold; margin-top:1px">Ben10 Upgrade Vs Aliens</a>        </di…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1049, Column 200: end tag for "DIV" omitted, but its declaration does not permit this
    …ne; font-weight:bold; margin-top:1px">Ben10 Upgrade Vs Aliens</a>        </div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1049, Column 32: start tag was here
                                   <div align='center' style="font:Verdana, Arial, …
  • Error Line 1054, Column 37: end tag for element "DIV" which is not open
                                   </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1058, Column 30: end tag for element "DIV" which is not open
                            </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1059, Column 26: end tag for element "DIV" which is not open
                        </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1060, Column 24: end tag for element "DIV" which is not open
                      </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1071, Column 16: end tag for element "DIV" which is not open
              </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1128, Column 18: ID "FB-ROOT" already defined
            <div id="fb-root"></div><script src="http://connect.facebook.net/en_US/…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 152, Column 10: ID "FB-ROOT" first defined here
    <div id="fb-root"></div>
  • Error Line 1128, Column 95: required attribute "TYPE" not specified
    …ect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like-box href="http://www.…

    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 1128, Column 123: there is no attribute "HREF"
    …s#xfbml=1"></script><fb:like-box href="http://www.facebook.com/pages/PlayToonG…

    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 1128, Column 194: there is no attribute "WIDTH"
    …ayToonGamescom/160591517348482" width="160" height="730" show_faces="true" bor…

    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 1128, Column 207: there is no attribute "HEIGHT"
    …m/160591517348482" width="160" height="730" show_faces="true" border_color="" …

    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 1128, Column 224: there is no attribute "SHOW_FACES"
    …" width="160" height="730" show_faces="true" border_color="" stream="false" he…

    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 1128, Column 244: there is no attribute "BORDER_COLOR"
    …="730" show_faces="true" border_color="" stream="false" header="false"></fb:li…

    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 1128, Column 254: there is no attribute "STREAM"
    … show_faces="true" border_color="" stream="false" header="false"></fb:like-box>

    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 1128, Column 269: there is no attribute "HEADER"
    … show_faces="true" border_color="" stream="false" header="false"></fb:like-box>

    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 1128, Column 276: element "FB:LIKE-BOX" undefined
    … show_faces="true" border_color="" stream="false" header="false"></fb:like-box>

    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 1213, Column 53: document type does not allow element "STYLE" here
                                  <style type="text/css">

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

  • Error Line 1287, Column 46: element "CENTER" undefined
    …<div style="visibility:hidden"><center><script id="_wauv5n">var _wau = _wau ||…

    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 1287, Column 58: there is no attribute "ID"
    …visibility:hidden"><center><script id="_wauv5n">var _wau = _wau || []; _wau.pu…

    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 1287, Column 67: required attribute "TYPE" not specified
    …y:hidden"><center><script id="_wauv5n">var _wau = _wau || []; _wau.push(["smal…

    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 1310, Column 6: end tag for element "DIV" which is not open
    </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1313, Column 14: end tag for element "DIV" which is not open
            </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1331, Column 8: there is no attribute "TARGET"
    target="_blank"><img class="statcounter"

    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 1337, Column 11: element "G:PLUSONE" undefined
    <g:plusone></g:plusone>

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

Visitor Analysis

Daily Visitor
  • 8.167 visits
Daily Visitor