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 7727 - legacy doc type does not need to be discouraged by "SHOULD NOT"
Summary: legacy doc type does not need to be discouraged by "SHOULD NOT"
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
Keywords: NE, WGDecision
Depends on:
Reported: 2009-09-25 10:36 UTC by Julian Reschke
Modified: 2010-12-16 13:29 UTC (History)
5 users (show)

See Also:


Description Julian Reschke 2009-09-25 10:36:35 UTC
There's no point in discouraging the legacy doc type with should not; there is no interop problem being solved by it.

Further discussion on IRC ( showed that potentially all doctypes that trigger standards mode should be allowed.
Comment 1 Ian 'Hixie' Hickson 2009-09-29 10:52:57 UTC
It should be discouraged because it wastes bytes and author's time.
Comment 2 Julian Reschke 2009-09-29 15:34:17 UTC
That's not sufficient reason for a RFC2119-level requirement.
Comment 3 Ian 'Hixie' Hickson 2009-09-29 22:35:48 UTC
That's probably true, but redefining the RFC2119 terms in HTML5 so that author and user benefits unrelated to interop are also in scope seems like an unnecessarily drastic solution compared to the option of just looking the other way like most specs do.

This requirement is an author and user benefit, and, like many others, would be a benefit to the entire network if followed by everyone. It isn't strictly needed for interop, but making life better is still a good thing.

Marking WONTFIX again; if you disagree, please escalate this to the chairs.
Comment 4 Michael[tm] Smith 2009-09-30 06:29:32 UTC
raised in Tracker as issue 84:
Comment 5 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:

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.