canvas 2d context
Encrypted Media Extensions
HTML 5 spec
HTML 5: The Markup Language
HTML WG website
HTML5 differences from HTML4
HTML5 Spec - PR Blockers
Media Source Extensions
pre-LC1 alt techniques
pre-LC1 authoring guide
pre-LC1 HTML 5 spec
Erika Doyle Navara
Philippe Le Hégaret
Joshue O Connor
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."
Add notes (no markup allowed, URIs get automatically hyperlinked):
[MikeSmith]: see http://www.w3.org/Bugs/Public/show_bug.cgi?id=7727
The term "should not" appears in section 9.1.1:
The change proposal originally made for ISSUE-4 also addresses this issue, so there is now a proposal. I'll give myself an action item to update the proposal to make sure that legacy doc types that still are interpreted in standards mode are still allowed.
Apparently, the editor's draft of the HTML5 spec now allows some legacy doctypes. Whether this resolves the issue, I don't know, but I think it removes the link with ISSUE-4.
Resolved, by Working Group Decision: