Philip Taylor wrote: > 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.
And committed! > 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. No, not really. I was just pointing out the fact that this test was presumably designed to test for case-sensitivity, and now that we're case-insensitive it's not striclty necessary. The parse error is odd, but I have studied tree building enough to really say anything about it (that's my next task :-). 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 [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 -~----------~----~----~----~------~----~------~--~---
