[Bug 26270] produce tokens for "/*" and "*/", or define an unclosed comment as a parse error

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26270

--- Comment #2 from Michael[tm] Smith <mike@w3.org> ---
(In reply to L. David Baron (Mozilla) from comment #1)
> Could it be a tokenization error instead of a parse error?

Yeah ideally it should be a tokenization error rather than a parse error -- to
the degree that the spec actually makes it possible to define tokenization
errors separately.

In other words, it should be possible to catch this case just using a
conforming tokenizer, without needing a conforming parser.

But as far as I can see the current spec doesn't actually define any
tokenization errors as such.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 5 July 2014 21:39:03 UTC