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 5863 - Tokeniser: "Bogus comment" state unclear
Summary: Tokeniser: "Bogus comment" state unclear
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2008-07-13 16:33 UTC by Andrew Sidwell
Modified: 2010-10-04 14:47 UTC (History)
3 users (show)

See Also:


Description Andrew Sidwell 2008-07-13 16:33:43 UTC
The spec says:

"Consume every character up to the first U+003E GREATER-THAN SIGN character (>) or the end of the file (EOF), whichever comes first. Emit a comment token whose data is the concatenation of all the characters starting from and including the character that caused the state machine to switch into the bogus comment state, up to and including the last consumed character before the U+003E character, if any, or up to the end of the file otherwise. (If the comment was started by the end of the file (EOF), the token is empty.)"

It would be clearer if the first sentence specified "Consume every character up to *and including* the first ...".
Comment 1 Ian 'Hixie' Hickson 2008-07-23 00:56:11 UTC
Generally cleaned this up. Let me know if it's still confusing.
Comment 2 Maciej Stachowiak 2010-03-14 13:15:13 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.