Validation Results

Jump To:

Results

File:	nokia-chooses-opera.html
Encoding:	utf-8
Doctype:	XHTML 1.0 Strict
Errors:	100

Note:

The Validator XML support has some limitations.

This page is not Valid XHTML 1.0 Strict!

Below are the results of attempting to parse this document with an SGML parser.

Line 21, column 133: end tag for "meta" omitted, but OMITTAG NO was specified
... Opera browser and its competition.">

You may have neglected to close a tag, or perhaps you meant to "self-close" a tag; that is, ending it with "/>" instead of ">".

✉
Line 21, column 0: start tag was here
<meta name="description" content="Opera Watch: The Unofficial Opera Blog. The la
Line 22, column 204: end tag for "meta" omitted, but OMITTAG NO was specified
...illa alternative Opera BLOG Browser">

✉
Line 22, column 0: start tag was here
<meta name="keywords" content="Opera Watch: The Unofficial Opera Blog The latest
Line 432, column 226: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
...conjunction with the Opera browser.<p>The tablet is being marketed as an alte

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 432, column 438: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
...nect to the Web and e-mail at home.<p>Instead of displaying stripped-down ver

✉
Line 432, column 608: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
...s as they'd appear on any computer.<p>Last November Opera announced a new tec

✉
Line 432, column 1130: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
...re is called "Fit to window width".<p>What does this mean for Opera and its u

✉
Line 432, column 1376: element "center" undefined
...rds, standard compliant).<br/><center><a href="http://www.nokiausa.com/770/1,

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), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).

✉
Line 432, column 1566: end tag for "img" omitted, but OMITTAG NO was specified
... Tablet" height="282" width="400"></a></center>

✉
Line 432, column 1431: start tag was here
...ww.nokiausa.com/770/1,7841,,00.html"><img src="http://i.i.com.com/cnwk.1d/i/n
Line 434, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div>

✉
Line 432, column 606: start tag was here
...tes as they'd appear on any computer.<p>Last November Opera announced a new t
Line 434, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div>

✉
Line 432, column 436: start tag was here
...onnect to the Web and e-mail at home.<p>Instead of displaying stripped-down v
Line 434, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div>

✉
Line 432, column 224: start tag was here
...n conjunction with the Opera browser.<p>The tablet is being marketed as an al
Line 434, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div>

✉
Line 431, column 6: start tag was here
<p>
Line 500, column 25: element "BR" undefined
<p>great news<BR/><BR/>this is a good news for opera. <BR/>congratulatio

✉
Line 500, column 30: element "BR" undefined
<p>great news<BR/><BR/>this is a good news for opera. <BR/>congratulatio

✉
Line 500, column 66: element "BR" undefined
.../>this is a good news for opera. <BR/>congratulations to opera developers, fa

✉
Line 500, column 127: element "BR" undefined
...a developers, fans, beta-testers <BR/>& to Nokia for making correct choice<..

✉
Line 500, column 128: character "&" is the first character of a delimiter but occurred as data
... developers, fans, beta-testers <BR/>& to Nokia for making correct choice</p>

If you wish to include the "<" character in your output, you should escape it as "<". Another possibility is that you forgot to close quotes in a previous tag.

✉
Line 538, column 27: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
<h2 class="sidebar-title">Opera Link Blog <br/><font size="-2">(updated daily)

✉
Line 538, column 60: there is no attribute "size"
<h2 class="sidebar-title">Opera Link Blog <br/><font size="-2">(updated daily)</font></h2>

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.

✉
Line 538, column 64: element "font" undefined
...="sidebar-title">Opera Link Blog <br/><font size="-2">(updated daily)</font></h2>

✉
Line 539, column 19: there is no attribute "language"
<script language="JavaScript" src="http://ns2.bigbold.com/digest/b6f9e485f92f/

✉
Line 539, column 96: required attribute "type" not specified
.../digest/b6f9e485f92f/fa0dbb6bff75.js"></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 540, column 61: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
...<a href="http://del.icio.us/operawatch">(more)</a></i><p>

✉
Line 542, column 2: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p><p></p>

✉
Line 542, column 5: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p><p></p>

✉
Line 545, column 27: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
<h2 class="sidebar-title">Advertisements</h2><br>

✉
Line 545, column 51: end tag for "br" omitted, but OMITTAG NO was specified
<h2 class="sidebar-title">Advertisements</h2><br>

✉
Line 545, column 47: start tag was here
<h2 class="sidebar-title">Advertisements</h2><br>
Line 562, column 2: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p><p>

✉
Line 562, column 5: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p><p>

✉
Line 564, column 27: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
<h2 class="sidebar-title">Previous Posts</h2>

✉
Line 565, column 21: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
<ul id="recently">

✉
Line 590, column 27: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
<h2 class="sidebar-title">More Links</h2>

✉
Line 591, column 29: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
<ul class="archive-list">

✉
Line 608, column 2: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p>

✉
Line 609, column 27: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
<h2 class="sidebar-title">Archives</h2>

✉
Line 610, column 28: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
<ul class="archive-list">

✉
Line 634, column 27: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
<h2 class="sidebar-title">Syndication</h2>

✉
Line 635, column 5: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p>This site's content is licensed under the <a href="http://creativecommons.

✉
Line 636, column 6: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p>

✉
Line 641, column 56: document type does not allow element "link" here
href="http://feeds.feedburner.com/OperaWatch" />

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 647, column 83: required attribute "alt" not specified
...pub/xml_button.gif" style="border:0"/></a>

✉
Line 649, column 4: end tag for "br" omitted, but OMITTAG NO was specified
<br>

✉
Line 649, column 0: start tag was here
<br>
Line 651, column 83: required attribute "alt" not specified
...pub/xml_button.gif" style="border:0"/></a>

✉
Line 653, column 2: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p>

✉
Line 656, column 66: there is no attribute "border"
...//www.bloglines.com/images/sub_modern3.gif" border="0" alt="Subscribe with Bloglines" />

✉
Line 659, column 2: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
<p>

✉
Line 664, column 9: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
<noscript>

✉
Line 665, column 71: there is no attribute "target"
...eter.com/stats.asp?site=s10operawatch" target="_top">

✉
Line 665, column 77: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
...ts.asp?site=s10operawatch" target="_top">

✉
Line 671, column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<font size=1 color=white>

✉
Line 671, column 19: there is no attribute "color"
<font size=1 color=white>

✉
Line 671, column 19: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<font size=1 color=white>

✉
Line 671, column 24: element "font" undefined
<font size=1 color=white>

✉
Line 673, column 49: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
<img src="http://t1.extreme-dm.com/i.gif" height=38

✉
Line 674, column 7: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
border=0 width=41 alt=""></a><script language="javascript1.2"><!--

✉
Line 674, column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
border=0 width=41 alt=""></a><script language="javascript1.2"><!--

✉
Line 674, column 28: end tag for "img" omitted, but OMITTAG NO was specified
border=0 width=41 alt=""></a><script language="javascript1.2"><!--

✉
Line 673, column 0: start tag was here
<img src="http://t1.extreme-dm.com/i.gif" height=38
Line 674, column 61: required attribute "type" not specified
...r=0 width=41 alt=""></a><script language="javascript1.2"><!--

✉
Line 677, column 38: required attribute "type" not specified
</script><script language="javascript"><!--

✉
Line 682, column 31: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
</script><noscript><img height=1 width=1 alt=""

✉
Line 682, column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
</script><noscript><img height=1 width=1 alt=""

✉
Line 683, column 47: cannot generate system identifier for general entity "j"
src="http://t0.extreme-dm.com/c.g?tag=operablg&j=n"></noscript>

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.

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 683, column 47: general entity "j" not defined and no default entity
src="http://t0.extreme-dm.com/c.g?tag=operablg&j=n"></noscript>

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 683, column 48: reference not terminated by REFC delimiter
src="http://t0.extreme-dm.com/c.g?tag=operablg&j=n"></noscript>

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 683, column 48: reference to external entity in attribute value
src="http://t0.extreme-dm.com/c.g?tag=operablg&j=n"></noscript>

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.

✉
Line 683, column 48: reference to entity "j" for which no system identifier could be generated
src="http://t0.extreme-dm.com/c.g?tag=operablg&j=n"></noscript>

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 683, column 46: entity was defined here
src="http://t0.extreme-dm.com/c.g?tag=operablg&j=n"></noscript>
Line 683, column 51: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
src="http://t0.extreme-dm.com/c.g?tag=operablg&j=n"></noscript>

✉
Line 683, column 62: end tag for "img" omitted, but OMITTAG NO was specified
...tp://t0.extreme-dm.com/c.g?tag=operablg&j=n"></noscript>

✉
Line 682, column 19: start tag was here
</script><noscript><img height=1 width=1 alt=""
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 659, column 0: start tag was here
<p>
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 653, column 0: start tag was here
<p>
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 636, column 4: start tag was here
<p>
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 635, column 3: start tag was here
<p>This site's content is licensed under the <a href="http://creativecommons.
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 608, column 0: start tag was here
<p>
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 562, column 3: start tag was here
<p><p>
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 562, column 0: start tag was here
<p><p>
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 542, column 0: start tag was here
<p><p></p>
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 540, column 59: start tag was here
<i><a href="http://del.icio.us/operawatch">(more)</a></i><p>
Line 687, column 9: end tag for "p" omitted, but OMITTAG NO was specified
</div></div></div>

✉
Line 535, column 0: start tag was here
<p>

Markup Validation Service

Note:

This page is not Valid XHTML 1.0 Strict!