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 24439 - Consider removing "nor contain two consecutive U+002D HYPHEN-MINUS characters (--), nor end with a U+002D HYPHEN-MINUS character (-)" (and equivalent in the parser) since old browsers are old
Summary: Consider removing "nor contain two consecutive U+002D HYPHEN-MINUS characters...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-29 11:25 UTC by contributor
Modified: 2014-01-30 20:11 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2014-01-29 11:25:39 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/syntax.html
Multipage: http://www.whatwg.org/C#text-0
Complete: http://www.whatwg.org/c#text-0
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
Consider removing "nor contain two consecutive U+002D HYPHEN-MINUS characters
(--), nor end with a U+002D HYPHEN-MINUS character (-)" (and equivalent in the
parser) since old browsers are old

Posted from: 90.230.218.37 by simonp@opera.com
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.90 Safari/537.1
Comment 1 Ian 'Hixie' Hickson 2014-01-29 17:51:51 UTC 
Isn't that for similarity with XML or something?
Comment 2 Simon Pieters 2014-01-30 11:01:36 UTC 
I think it was primarily for compat with Acid2-era browsers. http://lists.w3.org/Archives/Public/public-whatwg-archive/2006Jan/0209.html

But allowing it would introduce a thing where conforming text/html can't be serialized as XML without changing or dropping the comment, sure. (Do we ban non-Char in comments?)
Comment 3 Henri Sivonen 2014-01-30 11:20:06 UTC 
I would prefer not expanding the set of valid documents that need mangling in order to be representable through XML-oriented APIs in a non-browser context. That such mangling is needed at all seems confusing enough to users of the Validator.nu HTML Parser and I'm not keen to make the mangling code and the error reporting code diverge more.
Comment 4 Ian 'Hixie' Hickson 2014-01-30 20:11:52 UTC 
Yeah. The spec intro even mentions this kind of thing (search for "Errors that involve areas that affect authors migrating to and from XHTML").

Marking WONTFIX for now.