On Fri, Dec 26, 2008 at 3:01 AM, Edward Z. Yang <[email protected]> wrote: > > Hello all, > > I was running the Python parser tests and noticed that a few of the > tests were failing because <!DOCTYPE HTML> was expected, but <!DOCTYPE > html> was received. It seems to me that either the tests are wrong. If > there are no objections, I am going to fix the tests by converting the > #document expectation to lowercase.
I updated the tokeniser and tokeniser tests a few days ago, to do the lowercased doctype names. I didn't upate the tree-construction test cases at the same time, since I only wanted to worry about the tokeniser. So I believe those tests ought to be updated to expect lowercased doctype names, and if you can patch them then that'd be great. > Something that puzzles me, however, are tests like this: > > #data > <!DOCTYPE hTmL><html></html> > #errors > Line: 1 Col: 28 Unexpected end tag (html) after the (implied) root element. > #document > | <!DOCTYPE hTmL> > | <html> > | <head> > | <body> Is it the existence of the parse error that's confusing? That particular example is non-conforming anyway because it's missing the <title> element, but I think <!doctype html><title></title></html> should be conforming yet it still gives a parse error... I'll post something to the WHATWG list about that. -- 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 -~----------~----~----~----~------~----~------~--~---
