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 7616 - Move requirement about obsolete doctypes
Summary: Move requirement about obsolete doctypes
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: NE
Depends on:
Blocks:
 
Reported: 2009-09-14 18:03 UTC by Simon Pieters
Modified: 2010-10-04 13:56 UTC (History)
3 users (show)

See Also:

Attachments

Description Simon Pieters 2009-09-14 18:03:14 UTC 
The "should not" requirement about obsolete doctypes should probably be in the syntax section, written in the same way as the normal doctype and legacy-compat doctype, instead of being listed in the obsolete features section.
Comment 1 Ian 'Hixie' Hickson 2009-09-21 09:14:49 UTC 
Why?
Comment 2 Simon Pieters 2010-02-11 09:24:28 UTC 
Because it seems reasonable to assume that the syntax section covers all allowed syntax. Readers are likely to come to the conclusion that those doctypes are invalid.
Comment 3 Ian 'Hixie' Hickson 2010-02-17 21:30:12 UTC 
would that be a bad thing?
Comment 4 Simon Pieters 2010-02-18 10:40:26 UTC 
Yes. The spec should be clear about what the rules are. Otherwise people might give up trying to deduce rules from the spec (not just about syntax but in general).
Comment 5 Ian 'Hixie' Hickson 2010-02-25 04:52:59 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, 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

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 6 contributor 2010-02-25 04:54:47 UTC 
Checked in as WHATWG revision r4808.
Check-in comment: Define the obsolete permitted DOCTYPEs in the syntax section.
http://html5.org/tools/web-apps-tracker?from=4807&to=4808