8259 2009-11-11 12:16:25 +0000 There is one case of "The public identifier is set to" in amongst all the "The public identifier starts with". This seems like something that could easily lead to bugs. Please reorder the list to group together by the condition. 2010-10-04 14:49:06 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#quirks-mode-doctypes P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 29497 0 contributor 2009-11-11 12:16:25 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#quirks-mode-doctypes Comment: There is one case of "The public identifier is set to" in amongst all the "The public identifier starts with". This seems like something that could easily lead to bugs. Please reorder the list to group together by the condition. Posted from: 88.131.66.80 29499 1 zcorpan 2009-11-11 14:50:47 +0000 Actually there are three cases: The public identifier is set to: "-//W3O//DTD W3 HTML Strict 3.0//EN//" The public identifier is set to: "-/W3C/DTD HTML 4.0 Transitional/EN" The public identifier is set to: "HTML" Why don't the first two use the same convention as the others? 30465 2 ian 2010-01-05 07:52:44 +0000 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: Rejected Change Description: no spec change Rationale: They're pretty close to each other already, I don't think it's a huge problem. We'll just have to make sure we have test cases for this. The convention isn't followed for those two because they're not valid FPIs (one ends in // and the other one uses single /s).