On Wed, Dec 24, 2008 at 1:42 PM, Edward Z. Yang
<[email protected]> wrote:
>
> Philip Taylor wrote:
>> As http://wiki.whatwg.org/wiki/Parser_tests says, doctype tokens are
>> represented as ["DOCTYPE", name, public_id, system_id, correctness],
>> and "correctness is either true or false; true corresponds to the
>> force-quirks flag being false, and vice-versa", i.e. it's the exact
>> opposite of force-quirks. That's certainly quite counter-intuitive,
>> but it's that way for historical reasons :-). (The spec originally had
>> a correctness flag rather than a force-quirks flag, and nobody has
>> considered it worthwhile to update the test format when the spec
>> negated the flag's meaning.)
>
> Right. And what I'm saying is that in some cases the "correctness" tag
> is true when it should be false, i.e. someone forgot it was a
> correctness tag rather than a force quirks tag. If I flip the boolean
> before performing tests, I still get a number of fails... just on all
> the other tests.
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...
--
Philip Taylor
[email protected]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"html5lib-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/html5lib-discuss?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
