| 10:05 | <Huvet> | have someone tried to write a test generator that takes random html and sends it through html5lib? |
| 10:05 | <Huvet> | sounds like it could be able to find some bugs perhaps |
| 10:07 | <jgraham> | Huvet: Yeah I did that a while ago but not recently |
| 10:07 | <jgraham> | Obviously we regressed somewhat since then :) |
| 10:07 | <Huvet> | heh :) |
| 10:07 | <jgraham> | Huvet: Thanks for all the bug reports though, they are great |
| 10:08 | <Huvet> | np, I'm glad to help |
| 10:09 | <jgraham> | The fact that the table handling has some problems is not so surprising because that is one of the scariest parts of the parser and one that has changed a bit recently |
| 10:09 | <Philip`> | It's easy to get hundreds of thousands of real pages and send them through, and see what happens |
| 10:09 | <Philip`> | though perhaps a little bit slow |
| 10:09 | <jgraham> | s/easy/slow :) |
| 10:09 | <jgraham> | AH, you beat me |
| 10:10 | <Huvet> | even better would be a program that makes minimal testcases from a crash |
| 10:10 | <Huvet> | shouldn't be that much work |
| 10:10 | <jgraham> | Huvet: Google jesse lithium |
| 10:11 | <jgraham> | It does basically what you want |
| 10:12 | <Huvet> | well, I'm not thinking about it for my sake, but for html5libs :) |
| 10:12 | <jgraham> | Huvet: Right, the main problem we have had is that we haven't found the bugs in the first place :) |
| 10:13 | <Huvet> | yeah, so a major crawl of the web, and then a reduction script that reports minimal bugs as it finds them |
| 10:13 | <jgraham> | That could work |
| 10:17 | <Huvet> | hmm... I see that at leaste this bug was fixed recently (http://code.google.com/p/html5lib/issues/detail?id=127), but when I do "hg up", I don't get any updates |
| 10:17 | <Huvet> | C:\Emils\Nerladdat\html5lib>hg up |
| 10:17 | <Huvet> | 0 files updated, 0 files merged, 0 files removed, 0 files unresolved |
| 10:17 | <jgraham> | hg pull |
| 10:18 | <Huvet> | ah, I should read up on hg |
| 10:18 | <jgraham> | (up updates from the local respository, pull pulls from a different repository) |
| 11:10 | <Huvet> | hmm... should the parser be able to handle strange encodings? |
| 11:10 | <Huvet> | <meta name=”robots” content=”noodp”> |
| 11:10 | <Huvet> | seems to crash on that |
| 11:11 | <Huvet> | (note the strange quotes) |
| 11:11 | <jgraham> | That seems.. bad |
| 11:11 | <Huvet> | new bug? |
| 11:12 | <jgraham> | Sure |
| 11:13 | <jgraham> | (btw for simple bugs, the best way to report them is to give the parse.py command line like |
| 11:13 | <jgraham> | python parse.py '<meta name=”robots” content=”noodp”>' and the error |
| 11:13 | <Huvet> | ah, good idea |
| 11:13 | <jgraham> | since that is the easiest way to try and reproduce them) |
| 11:14 | <jgraham> | (but things that can be run in a python repl are fine too) |
| 11:15 | <Huvet> | I think I need a separate file for this one... the windows cmd prompt converts the quotes to proper ones when I paste them there :) |
| 11:16 | <Huvet> | strange feature |
| 11:19 | <jgraham> | Fair enough |
| 11:21 | <Huvet> | http://code.google.com/p/html5lib/issues/detail?id=129 |
| 13:11 | <jgraham> | Huvet: Oops, looks like I checked in part of another patch by mistake |
| 13:11 | <jgraham> | Try deleting the line with finalize on it |
| 13:19 | <gsnedders> | jgraham: Did I break the parser a fair bit? |
| 13:21 | <jgraham> | gsnedders: I don't know if it's your fault |
| 13:21 | <jgraham> | Probably not :) |
| 13:21 | <Philip`> | jgraham: You should blame him anyway |
| 13:23 | <jgraham> | Philip`: I blame you for not fixing bugs that were obiously mine in ihatexml.py :) |
| 13:23 | <jgraham> | *obviously |
| 13:25 | <Huvet> | jgraham: no worries, it doesn't happen when parsning, only halfway through minimizing a testcase |
| 13:26 | <Huvet> | so I'll keep it broken |
| 13:26 | <jgraham> | Huvet: since it is a one line deletion I will push the fix in a moment |
| 13:31 | <jgraham> | Huvet: done |
| 13:31 | <Huvet> | thx |
| 13:32 | <Huvet> | works perfectly |
| 14:30 | <Lachy> | hsivonen, I believe this error from your validator is incorrect: "Error: When the attribute lang is specified, the element must also have the attribute lang in the XML namespace present with the same value." |
| 14:31 | <Lachy> | I can't see anywhere in the spec that says I have to specify xml:lang="" in an XHTML document if I specifiy lang="". It just says that if both are present, then they must have the same value. |
| 14:46 | <hsivonen> | Lachy: whoa. something has regressed |
| 14:49 | hsivonen | is puzzled |
| 14:51 | hsivonen | is even more puzzled |
| 14:51 | <hsivonen> | the string that I find in the source code makes sense: |
| 14:51 | <jgraham> | hsivonen: Welcome to my world |
| 14:51 | <hsivonen> | When the attribute \u201Cxml:lang\u201D in no namespace is specified, the element must also have the attribute \u201Clang\u201D present with the same value. |
| 14:52 | <Lachy> | so you can't find the error I quoted above in the source? |
| 14:52 | <hsivonen> | Lachy: right |
| 14:52 | <hsivonen> | Lachy: I do see it on the site |
| 14:52 | <Lachy> | huh, weird. |
| 14:54 | <hsivonen> | ok, now I see it |
| 14:55 | <Lachy> | was that error based on an old requirement in the spec, presumably since removed? |
| 14:55 | <hsivonen> | I don't recall the spec ever having had such a req |
| 14:57 | <hsivonen> | blame shows I wrote that line |
| 14:58 | <Lachy> | at one point, it seems lang="" was HTML only and xml:lang was XHTML only, according to this snapshot of the spec. http://www.whatwg.org/specs/web-apps/2007-10-26/#the-lang |
| 14:58 | <hsivonen> | ah. ok |
| 14:59 | gsnedders | wonders how much would break if lang parsed to xml:lang in HTML |
| 14:59 | <gsnedders> | (or rather, it parsed to namespaceURI "http://www.w3.org/1998/xml";, prefix null, localName, "lang" |
| 15:00 | <hsivonen> | gsnedders: if you really want to know, you could hack the Java to C++ translator not to remove that feature and compile Gecko with that feature enabled |
| 15:00 | <Lachy> | JohnResi1, yt? I have a question about your selectors-api tests |
| 15:01 | <gsnedders> | I mean, would that break anything apart from a script that checked the namespaceURI of it? |
| 15:01 | <hsivonen> | actually, there's an easier way to test it |
| 15:01 | <hsivonen> | without hacking the translator |
| 15:02 | <hsivonen> | maybe I should make a batch of builds with that feature one of these days |
| 15:02 | <gsnedders> | I can't think how it should break anything |
| 15:02 | <gsnedders> | And it would make HTML/XHTML DOMs more consistent |
| 15:03 | <hsivonen> | gsnedders: it could break pages that try to change an existing lang attribute using setAttribute |
| 15:03 | <gsnedders> | Ah |
| 15:03 | <hsivonen> | so that's what would break |
| 15:03 | <Lachy> | gsnedders, it would break attribute selectors that use [lang], I think |
| 15:04 | <hsivonen> | unless you start hacking special cases into the DOM |
| 15:04 | <hsivonen> | probably not worth the trouble |
| 15:04 | <gsnedders> | Yeah, I don't want to add a special case to the DOM |
| 15:05 | <Lachy> | I think it's best to just discourage people from using xml:lang at all in XHTML, and only use lang |
| 15:06 | <Lachy> | that way, there are no DOM differences to worry about |
| 15:09 | <hsivonen> | Lachy: I agree |
| 15:35 | <hsivonen> | Lachy: Fixed. thanks |
| 21:06 | Hixie | returns from vacation and finds he has a LOT of e-mail |
| 21:07 | Hixie | goes to work to read it tall |
| 21:07 | <othermaciej_> | hello Hixie! |
| 21:07 | <othermaciej_> | welcome back |
| 21:23 | <TabAtkins> | I was wondering why Hixie wasn't being active in chat lately. Wb, Hixie. |
| 22:10 | danbri | imagines google has a server-cluster set aside for hixie's vacation inbox |
| 22:20 | <jlebar> | Hixie: ping |
| 23:50 | <Hixie> | jlebar: pong |
| 23:50 | <Hixie> | so, what's been going on while i've been away |
| 23:50 | <Hixie> | any decisions made? :-) |
| 23:51 | <jlebar> | I didn't know you were away. Welcome back! |
| 23:51 | <jlebar> | I wanted to ask about the title parameter in push/replaceState. Can we nix it? |
| 23:53 | <Hixie> | why would we nix it? |
| 23:54 | <jlebar> | Well, in the last e-mail about it, you said you wanted the title to be separate from document.title, but shown in the drop-down list of history entries (the one that shows up when you click the down button next to the forward button). But if we're creating the notion of a per-history-entry title separate from document.title, that seems orthogonal from push/replaceState. |
| 23:56 | <jlebar> | (Put another way: If I just want to change that title, does it really make sense for me to call replaceState?) |