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 8569 - I just checked Firefox, Safari, Opera, Chrome and IE, and Firefox seems to be the only browser treating two subsequent HYPHEN-MINUS characters in a comment as a signature of comment end. I suggest to allow subsequent HYPHEN-MINUS characters in comments, a
Summary: I just checked Firefox, Safari, Opera, Chrome and IE, and Firefox seems to be...
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-12-30 15:46 UTC by contributor
Modified: 2010-10-04 13:59 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-12-30 15:46:42 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#comments

Comment:
I just checked Firefox, Safari, Opera, Chrome and IE, and Firefox seems to be
the only browser treating two subsequent HYPHEN-MINUS characters in a comment
as a signature of comment end. I suggest to allow subsequent HYPHEN-MINUS
characters in comments, as long as they're not followed by a GREATER-THAN
SIGN. This would make commenting out text blocks much easier.

Posted from: 217.28.251.173
Comment 1 Ian 'Hixie' Hickson 2010-01-11 04:52:46 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: The reason for disallowing it is that it is disallowed in XML, not because of legacy Firefox behaviour (though that would be a valid reason also). It's the same reason we allow xmlns="" in certain places, and /> on void element start tags, and so on.