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 811 - Odd behaviour with custom FPI/SI
Summary: Odd behaviour with custom FPI/SI
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.6.7
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Terje Bless
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-25 05:51 UTC by Bj
Modified: 2005-02-05 04:14 UTC (History)
0 users

See Also:

Attachments

Description Bj 2004-06-25 05:51:58 UTC 
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Foo//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-foo.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<p><font>...</font></p>
</body>
</html>

Validator claims

  This Page Is Valid -//W3C//DTD XHTML 1.0 Foo//EN!

But Validation should clearly fail as the FPI is not known and 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-foo.dtd does not exist.
The example slightly modified

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Foo//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<p><font>...</font></p>
</body>
</html>

Again:

  This Page Is Valid -//W3C//DTD XHTML 1.0 Foo//EN!

http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd does exist and prohibes the 
<font> element, so this should not validate either.
Comment 1 Terje Bless 2005-02-05 04:14:44 UTC 
Fixed in CVS.