On Wed, Dec 24, 2008 at 4:43 AM, Edward Z. Yang <edwardzy...@thewritingpot.com> wrote: > > Hello all, > > After having quashed most regular test fails in my PHP HTML 5 tokenizer, > I've started looking at tests involving doctypes and parse errors. As > I've been combing through my 58 failures, it seems to me that my > behavior is more correct than the test case. For example, "<!DOCTYPEa > SYSTEM''!" in test3.test supposedly emits a doctype token that doesn't > have force-quirks mode, but my intuition and my reading of the spec says > that quirks mode should be turned on for this doctype. (Upon further > inspection, all of my failures stem from test3.test.)
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.) -- Philip Taylor exc...@gmail.com --~--~---------~--~----~------------~-------~--~----~ 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