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 1819 - Missing error reason for URL of DOCTYPE missing
Summary: Missing error reason for URL of DOCTYPE missing
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 0.7.0
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
URL: http://www.bobandgeorge.com/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-26 21:17 UTC by Naram Qashat
Modified: 2008-12-01 03:05 UTC (History)
1 user (show)

See Also:


Attachments

Description Naram Qashat 2005-07-26 21:17:47 UTC
When validating the above URL, the error comes up as

Line 1, column 62: no system id specified .

But there is no explanation under that.  The owner of that page has a DOCTYPE,
but the DOCTYPE is missing the URL of the DTD.
Comment 1 Olivier Thereaux 2005-07-26 23:37:15 UTC
This was not, per se, a bug, since many error messages, especially rare ones, do not have any additional 
explanation. We have a specific mechanism for users to contribute to the pool of explanations.

I have added an explanation for the warning you mention, see:
http://dev.w3.org/cvsweb/validator/htdocs/docs/errors.html.diff?r1=1.34&r2=1.35
Comment 2 reisio 2006-07-14 04:44:05 UTC
This error/warning should show up for HTML, too, not just XML-based.  I constantly run into people using Transitional HTML doctype declarations without a system identifier and they don't understand why their layouts are strangely rendered in foo browser (because quirks mode has been triggered).
Comment 3 Olivier Thereaux 2006-07-14 06:02:37 UTC
(In reply to comment #2)
> This error/warning should show up for HTML, too, not just XML-based.  I
> constantly run into people using Transitional HTML doctype declarations without
> a system identifier and they don't understand why their layouts are strangely
> rendered in foo browser (because quirks mode has been triggered).

Validation has nothing to do with browsers' proprietary behaviors. Please send a bug report to browser vendors if you feel valid markup trigger "quirk"y behavior in browsers