Philip Taylor wrote:
> The case you mentioned is:
>
> {"description":"<!DOCTYPEa SYSTEM\"!",
> "input":"<!DOCTYPEa SYSTEM\"!",
> "output":["ParseError", "ParseError", ["DOCTYPE", "a", null, "!", false]]},
>
> so it's expecting a doctype with correctness=false (i.e.
> force-quirks=true), which is sensible because it's got an EOF while in
> "DOCTYPE public identifier (double-quoted) state" which makes it "Set
> the DOCTYPE token's force-quirks flag to on". So I don't see a problem
> here yet...
The test-case I'm looking at is:
{"description":"<!DOCTYPE a SYSTEM''!",
"input":"<!DOCTYPE a SYSTEM''!",
"output":["ParseError", ["DOCTYPE", "a", null, "", true]]},
Somehow the space before the a in my original email went missing. If you
grep for "true" in test3.test you'll find many other examples.
Cheers,
Edward
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"html5lib-discuss" group.
To post to this group, send email to html5lib-discuss@googlegroups.com
To unsubscribe from this group, send email to
html5lib-discuss+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/html5lib-discuss?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4