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 7726 - legacy doctype syntax allows <!DOCTYPE HTML SYSTEM"about:legacy-compat">
Summary: legacy doctype syntax allows <!DOCTYPE HTML SYSTEM"about:legacy-compat">
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: NoReply
Depends on:
Blocks:
 
Reported: 2009-09-25 10:07 UTC by Julian Reschke
Modified: 2010-10-04 14:47 UTC (History)
5 users (show)

See Also:

Attachments

Description Julian Reschke 2009-09-25 10:07:28 UTC 
Note the missing whitespace after SYSTEM
Comment 1 Simon Pieters 2009-09-28 14:46:58 UTC 
This is intentional, because the parser doesn't require a space there (nor between the FPI and SI). It's not an error in SGML, unless I'm mistaken.

If you want the parser to signal an error for missing spaces, then reopen. It would result in a few more states to the tokenizer.
Comment 2 Julian Reschke 2009-09-28 14:58:18 UTC 
It's an error in XML, as far as I can tell.

The purpose of the legacy doctype is to allow specific serializers to produce conformant HTML5, so it's beyond me why we would want to allow that variation.

Unless you have evidence of producers that require this.
Comment 3 Julian Reschke 2009-09-28 15:01:43 UTC 
In particular, it contradicts:

"In other words, <!DOCTYPE HTML SYSTEM "about:legacy-compat"> or <!DOCTYPE HTML SYSTEM 'about:legacy-compat'>, case-insensitively except for the bit in quotes."
Comment 4 Simon Pieters 2009-09-28 18:05:54 UTC 
Personally, I think the spaces should be required, because it looks ugly without them. The space between "<!doctype" and "html" is required because it looks ugly without it.
Comment 5 Ian 'Hixie' Hickson 2009-09-29 10:50:38 UTC 
This resulted in three new tokeniser states. What a waste of the world's resources.
Comment 6 contributor 2009-09-29 10:51:01 UTC 
Checked in as WHATWG revision r4051.
Check-in comment: Report parse error for missing spaces in DOCTYPEs.
http://html5.org/tools/web-apps-tracker?from=4050&to=4051
Comment 7 contributor 2009-09-29 10:53:03 UTC 
Checked in as WHATWG revision r4052.
Check-in comment: Authoring-side change for the previous checkin.
http://html5.org/tools/web-apps-tracker?from=4051&to=4052
Comment 8 Julian Reschke 2009-09-29 10:58:28 UTC 
That's not sufficient reason for a RFC2119-level requirement.
Comment 9 Ian 'Hixie' Hickson 2009-09-29 11:15:02 UTC 
As far as I can tell I did exactly what you asked for here.

Maybe you reopened the wrong bug?
Comment 10 Julian Reschke 2009-09-29 15:33:33 UTC 
Indeed.
Comment 11 Maciej Stachowiak 2010-03-14 14:51:47 UTC 
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
  http://dev.w3.org/html5/decision-policy/decision-policy.html

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.