Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 12,
Column 7:
required attribute "type" not specified
<style>body{background:#e0eeff;color:#707070;font:10pt Verdana;margin:0px 0px 0…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>.
Line 13,
Column 7:
required attribute "type" not specified
<style>form{margin:0px}label{cursor:default}.inlineimg{vertical-align:middle}</…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>.
Line 14,
Column 144:
required attribute "type" not specified
…,qv==388b2.pagespeed.jc.h2xLeMybuZ.js"></script><script>eval(mod_pagespeed_f8t…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>.
Line 14,
Column 161:
required attribute "type" not specified
…eed.jc.h2xLeMybuZ.js"></script><script>eval(mod_pagespeed_f8tBMlwrqj);</script…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>.
Line 15,
Column 8:
required attribute "type" not specified
<script>eval(mod_pagespeed_yS88cGWH$m);</script>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>.
Line 24,
Column 183:
required attribute "type" not specified
…qv==370b5h.pagespeed.jc.nO42zUhyZl.js"></script><script>eval(mod_pagespeed_oEj…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>.
Line 24,
Column 200:
required attribute "type" not specified
…eed.jc.nO42zUhyZl.js"></script><script>eval(mod_pagespeed_oEjcosUmWF);</script…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>.
Line 27,
Column 24:
there is no attribute "name"
<div id='mypopup' name='mypopup' style='z-index:1000;position:absolute;backgrou…You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 27,
Column 100:
document type does not allow element "div" here; assuming missing "object" start-tag
…opup' style='z-index:1000;position:absolute;background:none;border:none'></div><script>eval(mod_pagespeed_ojv3JnxGwL);</script>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>.
Line 29,
Column 8:
required attribute "type" not specified
<script>eval(mod_pagespeed_c2v9_k2ZqZ);</script>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>.
Line 30,
Column 7:
document type does not allow element "title" here
<title>WAOAnime - Best Anime Community Online</title>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 31,
Column 7:
end tag for "object" omitted, but OMITTAG NO was specified
</head>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 27,
Column 1:
start tag was here
<div id='mypopup' name='mypopup' style='z-index:1000;position:absolute;backgrou…</head>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.
Line 42,
Column 178:
there is no attribute "width"
….pagespeed.ic.T5rEpHxMoJ.png" class="wao-search-button" width="30" height="28">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 42,
Column 190:
there is no attribute "height"
….pagespeed.ic.T5rEpHxMoJ.png" class="wao-search-button" width="30" height="28">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 42,
Column 195:
end tag for "input" omitted, but OMITTAG NO was specified
….pagespeed.ic.T5rEpHxMoJ.png" class="wao-search-button" width="30" height="28">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 42,
Column 1:
start tag was here
<input type="image" src="http://www.waoanime.tv/wp-content/themes/watchanimeon-…<li><a href="http://www.waoanime.tv/"><span>Anime</span></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>").
Line 60,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><a href="http://www.citymanga.com"><span>Manga</span></a></li>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>").
Line 61,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><a href="arcade.php"><span>Games</span></a></li>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>").
Line 62,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><a href="http://www.waoanime.tv/anime-news/"><span>News</span></a></li>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>").
Line 63,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><a href="/"><span>Forums</span></a></li>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>").
Line 64,
Column 5:
end tag for "li" omitted, but OMITTAG NO was specified
</ul>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 47,
Column 1:
start tag was here
<li><a href="http://www.waoanime.tv/random/"><span>Random</span></a><script>eval(mod_pagespeed_bhdpOlPc2b);</script>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>.
Line 82,
Column 227:
end tag for "input" omitted, but OMITTAG NO was specified
…g.pagespeed.ic.9aUssV5Mzn.png" class="wao-login-button" width="70" height="23">You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 82,
Column 1:
start tag was here
<input type="image" value="Log in" accesskey="s" src="http://images1.waoanime.t…
Line 111,
Column 84:
character "&" is the first character of a delimiter but occurred as data
… href="http://www.watchanimeon.com/forums/album.php">Pictures & Albums</a></li>This message may appear in several cases:
Line 118,
Column 23:
document type does not allow element "style" here
<style type="text/css">body{font:11px Verdana}</style>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 119,
Column 106:
an attribute value literal can occur in an attribute specification list only after a VI delimiter
…" cellpadding="6" cellspacing="0" style="background-color:#fff;align=" center">
Have you forgotten the "equal" sign marking the separation
between the attribute and its declared value?
Typical syntax is attribute="value".
Line 119,
Column 107:
character data is not allowed here
…" cellpadding="6" cellspacing="0" style="background-color:#fff;align=" center">You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 136,
Column 116:
required attribute "type" not specified
…,qv==388b2.pagespeed.jc.Hlvnj--tm6.js"></script><script>eval(mod_pagespeed_7jv…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>.
Line 136,
Column 133:
required attribute "type" not specified
…eed.jc.Hlvnj--tm6.js"></script><script>eval(mod_pagespeed_7jv9Mwc9DD);</script…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>.
Line 140,
Column 92:
ID "navbar_username" already defined
…ze:11px" name="vb_login_username" id="navbar_username" size="10" accesskey="u"…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).
Line 80,
Column 49:
ID "navbar_username" first defined here
…e="text" name="vb_login_username" id="navbar_username" accesskey="u" tabindex=……kieuser" value="1" tabindex="103" id="cb_cookieuser_navbar" accesskey="c"/>Rem…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).
Line 83,
Column 69:
ID "cb_cookieuser_navbar" first defined here
…kieuser" value="1" tabindex="103" id="cb_cookieuser_navbar" accesskey="c" chec……ze:11px" name="vb_login_password" id="navbar_password" size="10" tabindex="102…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).
Line 81,
Column 53:
ID "navbar_password" first defined here
… type="password" name="vb_login_password" id="navbar_password" tabindex="102"/>…border" cellpadding="9" cellspacing="2" border="0" width="100%" align="center">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 283,
Column 24:
document type does not allow element "div" here
<div class="cat_spacer"></div>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 284,
Column 94:
document type does not allow element "table" here
…border" cellpadding="9" cellspacing="2" border="0" width="100%" align="center">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 424,
Column 24:
document type does not allow element "div" here
<div class="cat_spacer"></div>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 425,
Column 94:
document type does not allow element "table" here
…border" cellpadding="9" cellspacing="2" border="0" width="100%" align="center">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 591,
Column 24:
document type does not allow element "div" here
<div class="cat_spacer"></div>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 592,
Column 94:
document type does not allow element "table" here
…border" cellpadding="9" cellspacing="2" border="0" width="100%" align="center">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 600,
Column 8:
end tag for element "tbody" which is not open
</tbody>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.
Line 602,
Column 24:
document type does not allow element "div" here
<div class="cat_spacer"></div>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 603,
Column 94:
document type does not allow element "table" here
…border" cellpadding="9" cellspacing="2" border="0" width="100%" align="center">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 632,
Column 7:
document type does not allow element "tbody" here
<tbody>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 641,
Column 8:
end tag for "tbody" omitted, but OMITTAG NO was specified
</table>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 612,
Column 1:
start tag was here
<tbody id="collapseobj_forumbit_30" style=""><script>eval(mod_pagespeed_hB$icgjcZ2);</script>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>.
Line 642,
Column 8:
document type does not allow element "script" here; assuming missing "caption" start-tag
<script>eval(mod_pagespeed_hB$icgjcZ2);</script>…border" cellpadding="9" cellspacing="2" border="0" width="100%" align="center">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>").
Line 715,
Column 470:
end tag for "span" omitted, but OMITTAG NO was specified
…span style="color:red">agaric1</strong></span></a>, <a href="members/305026/" …You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 715,
Column 431:
start tag was here
…/21915/" title="Today, 18:48"><strong><span style="color:red">agaric1</strong>……yle="color:red">agaric1</strong></span></a>, <a href="members/305026/" title="…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.
Line 715,
Column 3495:
end tag for "span" omitted, but OMITTAG NO was specified
…<span style="color:red">Izzy2k</strong></span></a>, <a href="members/118350/" …You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 715,
Column 3457:
start tag was here
…bers/1/" title="Today, 13:28"><strong><span style="color:red">Izzy2k</strong><……tyle="color:red">Izzy2k</strong></span></a>, <a href="members/118350/" title="…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.
Line 715,
Column 4176:
end tag for "span" omitted, but OMITTAG NO was specified
…an style="color:red">linkermod</strong></span></a>, <a href="members/39988/" t…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 715,
Column 4135:
start tag was here
…/41922/" title="Today, 18:09"><strong><span style="color:red">linkermod</stron……e="color:red">linkermod</strong></span></a>, <a href="members/39988/" title="T…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.
Line 721,
Column 200:
end tag for "span" omitted, but OMITTAG NO was specified
…yle="color:red">Administrators</strong></span> - <font style="color:#0f0"><str…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 721,
Column 154:
start tag was here
… Moderators</strong></font> - <strong><span style="color:red">Administrators</……oderators</strong></font> - <span style="color:gray">Banned Users</span></span>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.
Line 765,
Column 63:
document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<table cellpadding="0" cellspacing="2" border="0" width="100%">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>").
Line 782,
Column 20:
document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<div align="center">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>").
Line 794,
Column 6:
end tag for "caption" omitted, but OMITTAG NO was specified
</div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 642,
Column 1:
start tag was here
<script>eval(mod_pagespeed_hB$icgjcZ2);</script></div></div>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 172,
Column 1:
start tag was here
<table class="tborderb" cellpadding="9" cellspacing="2" border="0" width="100%"…</table>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 121,
Column 1:
start tag was here
<td></table>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 120,
Column 1:
start tag was here
<tr></div></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.
Line 872,
Column 522:
there is no attribute "pagespeed_no_defer"
…;}</script><script pagespeed_no_defer="" type="text/javascript">(function(){va…You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 872,
Column 613:
character "&" is the first character of a delimiter but occurred as data
…Component,f=window,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Conte…This message may appear in several cases:
Line 872,
Column 620:
cannot generate system identifier for general entity "cs"
…nt,f=window,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 872,
Column 620:
general entity "cs" not defined and no default entity
…nt,f=window,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 872,
Column 622:
reference not terminated by REFC delimiter
…,f=window,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type",…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 872,
Column 622:
reference to entity "cs" for which no system identifier could be generated
…,f=window,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type",…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 872,
Column 619:
entity was defined here
…ent,f=window,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Typ……ow,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type",t="Micr…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 872,
Column 629:
general entity "n" not defined and no default entity
…ow,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type",t="Micr…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 872,
Column 630:
reference not terminated by REFC delimiter
…w,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type",t="Micro…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 872,
Column 630:
reference to entity "n" for which no system identifier could be generated
…w,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type",t="Micro…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 872,
Column 628:
entity was defined here
…dow,g="length",k="",l="&",n="&cs=",p="&n=",q=",",r="?",s="Content-Type",t="Mic……[z+b];a[z+b]=function(){c.call(this);d&&d.call(this)}}};f.pagespeed=f.pagespee…This message may appear in several cases:
Line 872,
Column 945:
cannot generate system identifier for general entity "d.call"
…+b];a[z+b]=function(){c.call(this);d&&d.call(this)}}};f.pagespeed=f.pagespeed|…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 872,
Column 945:
general entity "d.call" not defined and no default entity
…+b];a[z+b]=function(){c.call(this);d&&d.call(this)}}};f.pagespeed=f.pagespeed|…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 872,
Column 951:
reference not terminated by REFC delimiter
…z+b]=function(){c.call(this);d&&d.call(this)}}};f.pagespeed=f.pagespeed||{};va…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 872,
Column 951:
reference to entity "d.call" for which no system identifier could be generated
…z+b]=function(){c.call(this);d&&d.call(this)}}};f.pagespeed=f.pagespeed||{};va…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 872,
Column 944:
entity was defined here
…z+b];a[z+b]=function(){c.call(this);d&&d.call(this)}}};f.pagespeed=f.pagespeed……a=y+this.i+p+this.h,a=a+n,b=0;b<this.c[g];++b){var c=0<b?q:k,c=c+e(this.c[b]);……a=y+this.i+p+this.h,a=a+n,b=0;b<this.c[g];++b){var c=0<b?q:k,c=c+e(this.c[b]);…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:
Line 873,
Column 90:
character "?" not allowed in attribute specification list
…h,a=a+n,b=0;b<this.c[g];++b){var c=0<b?q:k,c=c+e(this.c[b]);if(131072<a[g]+c[g……c=0<b?q:k,c=c+e(this.c[b]);if(131072<a[g]+c[g])break;a+=c}C.criticalCssBeaconD……ry{d=new ActiveXObject(t)}catch(m){}}d&&(d.open(v,b+(-1==b.indexOf(r)?r:l)+A+e…This message may appear in several cases:
Line 873,
Column 334:
character "&" is the first character of a delimiter but occurred as data
…y{d=new ActiveXObject(t)}catch(m){}}d&&(d.open(v,b+(-1==b.indexOf(r)?r:l)+A+e(…This message may appear in several cases:
Line 874,
Column 47:
character "&" not allowed in attribute specification list
…ype.d=function(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null……ype.d=function(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null…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:
Line 874,
Column 49:
cannot generate system identifier for general entity "this.a"
…e.d=function(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null!=…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 874,
Column 49:
general entity "this.a" not defined and no default entity
…e.d=function(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null!=…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 874,
Column 55:
reference not terminated by REFC delimiter
…nction(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null!=docume…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 874,
Column 55:
reference to entity "this.a" for which no system identifier could be generated
…nction(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null!=docume…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 874,
Column 48:
entity was defined here
…pe.d=function(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null!……a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null!=document.quer……a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null!=document.quer…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:
Line 874,
Column 127:
character "&" is the first character of a delimiter but occurred as data
…document.querySelector(this.b[this.a])&&this.c.push(this.b[this.a])}catch(c){}…This message may appear in several cases:
Line 874,
Column 129:
cannot generate system identifier for general entity "this.c.push"
…cument.querySelector(this.b[this.a])&&this.c.push(this.b[this.a])}catch(c){}th…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 874,
Column 129:
general entity "this.c.push" not defined and no default entity
…cument.querySelector(this.b[this.a])&&this.c.push(this.b[this.a])}catch(c){}th…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 874,
Column 140:
reference not terminated by REFC delimiter
…ySelector(this.b[this.a])&&this.c.push(this.b[this.a])}catch(c){}this.a<this.b…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 874,
Column 140:
reference to entity "this.c.push" for which no system identifier could be generated
…ySelector(this.b[this.a])&&this.c.push(this.b[this.a])}catch(c){}this.a<this.b…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 874,
Column 128:
entity was defined here
…ocument.querySelector(this.b[this.a])&&this.c.push(this.b[this.a])}catch(c){}t……his.b[this.a])}catch(c){}this.a<this.b[g]?f.setTimeout(this.d.bind(this),0,a):……his.b[this.a])}catch(c){}this.a<this.b[g]?f.setTimeout(this.d.bind(this),0,a):…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:
Line 874,
Column 274:
character "&" is the first character of a delimiter but occurred as data
…n(a,b,c,d,h){if(document.querySelector&&Function.prototype.bind){var m=new D(a…This message may appear in several cases:
Line 874,
Column 276:
cannot generate system identifier for general entity "Function.prototype.bind"
…a,b,c,d,h){if(document.querySelector&&Function.prototype.bind){var m=new D(a,b…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 874,
Column 276:
general entity "Function.prototype.bind" not defined and no default entity
…a,b,c,d,h){if(document.querySelector&&Function.prototype.bind){var m=new D(a,b…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 874,
Column 299:
reference not terminated by REFC delimiter
…querySelector&&Function.prototype.bind){var m=new D(a,b,c,d,h);B(f,x,function(…If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 874,
Column 299:
reference to entity "Function.prototype.bind" for which no system identifier could be generated
…querySelector&&Function.prototype.bind){var m=new D(a,b,c,d,h);B(f,x,function(…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 874,
Column 275:
entity was defined here
…(a,b,c,d,h){if(document.querySelector&&Function.prototype.bind){var m=new D(a,……hQiHTSw',pagespeed.selectors);</script><noscript class="psa_add_styles"><link …You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 874,
Column 173:
start tag was here
….push(this.b[this.a])}catch(c){}this.a<this.b[g]?f.setTimeout(this.d.bind(this……hQiHTSw',pagespeed.selectors);</script><noscript class="psa_add_styles"><link …You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 874,
Column 55:
start tag was here
…nction(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)try{null!=docume……hQiHTSw',pagespeed.selectors);</script><noscript class="psa_add_styles"><link …You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 874,
Column 40:
start tag was here
….prototype.d=function(a){for(var b=0;b<this.e&&this.a<this.b[g];++b,++this.a)t……hQiHTSw',pagespeed.selectors);</script><noscript class="psa_add_styles"><link …You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 873,
Column 121:
start tag was here
…r c=0<b?q:k,c=c+e(this.c[b]);if(131072<a[g]+c[g])break;a+=c}C.criticalCssBeaco……hQiHTSw',pagespeed.selectors);</script><noscript class="psa_add_styles"><link …You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 873,
Column 88:
start tag was here
…s.h,a=a+n,b=0;b<this.c[g];++b){var c=0<b?q:k,c=c+e(this.c[b]);if(131072<a[g]+c……hQiHTSw',pagespeed.selectors);</script><noscript class="psa_add_styles"><link …You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 873,
Column 65:
start tag was here
…or(var a=y+this.i+p+this.h,a=a+n,b=0;b<this.c[g];++b){var c=0<b?q:k,c=c+e(this……ss" type="text/css" id="vbulletin_css"><link rel="stylesheet" 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).
Line 875,
Column 1849:
end tag for "link" omitted, but OMITTAG NO was specified
…s" type="text/css" id="vbulletin_css"><link rel="stylesheet" type="text/css" h…You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 875,
Column 1702:
start tag was here
…ript><noscript class="psa_add_styles"><link rel="stylesheet" href="clientscrip……qv=388b2.pagespeed.cf._KLyuoYcor.css"/><link href="http://images1.watchanimeon…The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 875,
Column 2106:
document type does not allow element "link" here
…e/forumstyle.css?v=1" rel="stylesheet" type="text/css"/><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).
Line 875,
Column 2129:
document type does not allow element "style" here
…e/forumstyle.css?v=1" rel="stylesheet" type="text/css"/><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).
Line 879,
Column 373:
character "<" is the first character of a delimiter but occurred as data
…pt"); var r = []; for (var i = 0; i < n.length; ++i) { var e = n[i]; i…This message may appear in several cases:
Line 879,
Column 494:
character "<" is the first character of a delimiter but occurred as data
…r.push(e); } } for (var i = 0; i < r.length; ++i) { var e = r[i]; v…This message may appear in several cases:
