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 4915 - &ensp gives unexplained error at other place in document
Summary: &ensp gives unexplained error at other place in document
Status: RESOLVED DUPLICATE of bug 4892
Alias: None
Product: Validator
Classification: Unclassified
Component: Parser (show other bugs)
Version: HEAD
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
Depends on:
Reported: 2007-08-04 20:12 UTC by Harald Rudell
Modified: 2007-08-05 23:04 UTC (History)
0 users

See Also:


Description Harald Rudell 2007-08-04 20:12:03 UTC
Try validating this page:
(you can click the Validate! link in the document)

validator output is:
Validation Output:  1 Error

   1. Error Line 28, Column 0: 18 up 164 days, 3:49, 1 user, load average: 0.00, 0.00, 0.00<br .

a. markup is valid, there should not be an error
b. the document only has 18 lines, the location given is incorrect. Often some random markup line is provided by the validator
c. the cause is the &ensp; entry in column 17 on line 13, if these six characters are removed, no validation error is given

complete document below:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "">
<html xmlns="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Is this really invalid xhtml 1.1?</title>
<link rel="stylesheet" type="text/css" media="screen" href="style/default-temp.css" />
<p><a href="">Validate!</a></p>
<p>an &amp;ensp inserted in the paragraph below causes the w3c xhtml 1.1 validator service to incorrectly report an error in the column of the &amp;ensp but at a random line in the document.</p>
				<p>root@hrudell:~# uptime; uname<br />
				&ensp;17:28:18 up 164 days, 3:49, 1 user, load average: 0.00, 0.00, 0.00<br />

Otherwise, I enjoy the validation services very much!


Harald Rudell
Comment 1 Olivier Thereaux 2007-08-05 23:04:41 UTC

*** This bug has been marked as a duplicate of bug 4892 ***