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 7089 - CDATA escapes need to close upon --\s*!>
Summary: CDATA escapes need to close upon --\s*!>
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2009-07-08 08:30 UTC by Henri Sivonen
Modified: 2010-10-04 14:56 UTC (History)
3 users (show)

See Also:


Description Henri Sivonen 2009-07-08 08:30:27 UTC
Gecko bug

Compat with existing content seems to require CDATA escape to end with -- !>

Comment 1 Henri Sivonen 2009-07-09 13:56:48 UTC
I think we should have a 'comment end space bang' state for comments that you can enter from 'comment end space'. This needs to be distinct from 'comment end bang' only in order to get the end of the comment data right.

Then we should have all the corresponding states for [R]CDATA escapes. (The spec currently doesn't have real states for espaces, but I elected to implement escapes as states anyway. See )
Comment 2 Ian 'Hixie' Hickson 2009-08-09 21:08:26 UTC
In markup:
Opera and IE8 do not terminate for either --!> or -- > or --! > or -- !>
Safari does not terminate for either -- > or --! > or -- !>, it does for --!>
HTML5 and HTML5 Gecko do not terminate for --! > or -- !>, but do for --!> and -- >

In script:
Opera and IE8 are as above.
Safari is the same as above.
HTML5 and HTML5 Gecko are like Opera and IE8.

The page in question:
...renders differently in every browser I tried.

I am skeptical about making the crazy behaviour in raw text elements even crazier. It's already really hard to explain; making it harder seems bad. Are there many other pages affected by this?

I'd actually rather remove the --!>/-- > behaviour than add more crazy behaviour here.
Comment 3 Maciej Stachowiak 2010-03-14 14:48:25 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.