This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 912 - Incorrectly stating error of unencoded URL
Summary: Incorrectly stating error of unencoded URL
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.0
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: Terje Bless
QA Contact: qa-dev tracking
Depends on:
Reported: 2004-10-12 08:06 UTC by Robert
Modified: 2004-10-12 08:15 UTC (History)
0 users

See Also:


Description Robert 2004-10-12 08:06:41 UTC
In the  <option> and <td> tags of a HTML page, if text is found
starting with 'http://' (for example, 'http://goto&') the 
validator will identify these as errors, stating the URL should be encoded.  

They should not be listed as errors because:

a) they are not links

b) they are to be presented to the user, so you would NOT want to encode
them as you would a similar href link.

NOTE:  There may be other similar instances where this occurs, these are
the only ones I have found so far.  My suggestion is that the validator
ONLY checks addresses which are specifically used as links in the HTML page.
Comment 1 Bj 2004-10-12 08:15:46 UTC
Sorry but it is irrelevant where this might appear or how it is used, HTML and 
XHTML have rules for when special characters need to be escaped, these need to 
be followed. These rules exist so that it is clear what you mean. Consider your 
example was




Now, how should a browser know whether you mean &nbsp; / <p> or &amp;nbsp; / 
&lt;p&gt;? It cannot know, hence you need to escape the special characters to 
make this clear.

Also note that the Validator is not the right place to discuss such rules, the 
Validator just implements the rules defined by others, for HTML see the Status 
section of on how to send comments on the