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 8259 - 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.
Summary: There is one case of "The public identifier is set to" in amongst all the "Th...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-11 12:16 UTC by contributor
Modified: 2010-10-04 14:49 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-11-11 12:16:25 UTC 
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
Comment 1 Simon Pieters 2009-11-11 14:50:47 UTC 
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?
Comment 2 Ian 'Hixie' Hickson 2010-01-05 07:52:44 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: 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).