W3C home > Mailing lists > Public > www-validator@w3.org > January 2011

Re: Unicorn can't see (X)HTML?

From: Philip Taylor (Webmaster, Ret'd) <P.Taylor@Rhul.Ac.Uk>
Date: Sun, 02 Jan 2011 17:46:45 +0000
Message-ID: <4D20BA05.1040207@Rhul.Ac.Uk>
To: Gordon Edwards <gordon451@westnet.net.au>
CC: www-validator@w3.org, public-unicorn@w3.org


Gordon Edwards wrote:
> Hi -
>
> I was having trouble with "Opera features"
> <http://www.opera.com/browser/features/>, and decided to validate it (Opera
> 9.51).

> Then I gave it to Unicorn
> <http://validator.w3.org/unicorn/check?ucn_uri=www.opera.com%2Fbrowser%2Ffea
> tures%2F&ucn_task=conformance#>.  But Unicorn's General Conformance only
> found an Opera RSS feed<http://www.opera.com/press/rss/>  and passed the
> entire page as "Congratulations!  This is a valid RSS feed."

For http://validator.w3.org/check?uri=http://www.opera.com/browser/features/
I get this :

Validation Output: 2 Errors

    1. Error Line 106, Column 245: ID "features" already defined

       …"on"><a href="/browser/features/" id="features">Features</a></li><li><a href="…

       ✉

       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).
    2. Info Line 66, Column 11: ID "features" first defined here

       <body id="features"><div id="page"><div id="nav"><p class="yank"><a href="#bran…

    3. Error Line 275, Column 79: there is no attribute "rel"

       …ps/products/browser/features/opera11/win/scr-tabs.png" rel="platform" alt="" />

       ✉

       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.

Philip Taylor
Received on Sunday, 2 January 2011 17:49:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:45 GMT