ISSUE-84
legacy-doctypes
Should spec discourage use of "legacy" doctypes?
- State:
- RAISED
- Product:
- HTML 5 spec
- Raised by:
- Michael(tm) Smith
- Opened on:
- 2009-09-30
- Description:
Quoting Julian Reschke from bug 7727: "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 (http://www.w3.org/2009/09/25-html-wg-irc) showed that potentially all doctypes that trigger standards mode should be allowed." http://www.w3.org/Bugs/Public/show_bug.cgi?id=7727
- Related Actions Items:
- No related actions
- Related emails:
- We now have Atom feeds for all Tracker issues [was: HTML Working Group Decision Policy - for discussion] (from mike@w3.org on 2009-11-17)
- Re: HTML Working Group Decision Policy - for discussion (from mike@w3.org on 2009-10-08)
- minutes of 2009-10-01 telcon (from mike@w3.org on 2009-10-02)
- Agenda for HTML WG telcon 2009-09-24 - CfCs, Accessibility TF, Testing TF, etc. (from mjs@apple.com on 2009-09-30)
- [Bug 7727] legacy doc type does not need to be discouraged by 'SHOULD NOT' (from bugzilla@wiggum.w3.org on 2009-09-30)
Related notes:
2009-09-30 06:26:34: [MikeSmith]: see http://www.w3.org/Bugs/Public/show_bug.cgi?id=7727
2009-10-01 16:31:49: The term "should not" appears in section 9.1.1:
http://www.w3.org/TR/html5/syntax.html#the-doctype [Philippe Le Hégaret]
Display change log
