/irc-logs / freenode / #whatwg / 2007-06-19 / end

Options:

  1. # Session Start: Tue Jun 19 00:00:00 2007
  2. # Session Ident: #whatwg
  3. # [00:11] <Hixie> http://lists.w3.org/Archives/Public/public-html/2007Jun/0375.html
  4. # [00:11] <Hixie> o_O
  5. # [00:14] * Joins: epeus (i=KevinMar@nat/google/x-ae3d096f9a7b2381)
  6. # [00:16] * Quits: KevinMarks (i=KevinMar@pdpc/supporter/active/kevinmarks) (Nick collision from services.)
  7. # [00:16] * epeus is now known as KevinMarks
  8. # [00:21] * KevinMarks is now known as epeus
  9. # [00:25] * epeus is now known as KevinMarks
  10. # [00:41] * Joins: weinigLap (i=weinig@nat/apple/x-381797ab6be271dd)
  11. # [01:01] * Hixie wonders how it is "frequently unclear whether a suggestion is aimed at the language definition or at the browser behaviour specification"
  12. # [01:01] <Hixie> isn't it pretty obvious?
  13. # [01:03] <jgraham> Hixie: From Phillip's mail to public-html? That whole email made no sense to me.
  14. # [01:03] <Hixie> i have to say i generally understand mails to whatwg a whole lot better than those to p-h
  15. # [01:04] <Hixie> it's kinda annoying since it makes it harder for me to deal with the p-h ones
  16. # [01:05] <jgraham> whatwg (still) seems to be where all the work is getting done... maybe we can change the tag line to "Putting the 'work' into working group" or somesuch ;)
  17. # [01:06] <Hixie> no comment
  18. # [01:08] <jgraham> I'm joking of course...
  19. # [01:08] <jgraham> And, I think it is generally obvious what is a document conformance requirement and what is a US requirement
  20. # [01:09] <jgraham> I also think the spec makes for a poor reference for authors
  21. # [01:09] <Hixie> it certainly makes a poor reference to anyone who isn't technically minded
  22. # [01:10] <Hixie> i'm not really skilled enough to write text that is both unambiguous and clear to non-technical people, sadly
  23. # [01:18] * Joins: weinigLap_ (n=weinig@17.255.105.160)
  24. # [01:19] * Quits: weinigLap_ (n=weinig@17.255.105.160) (Read error: 104 (Connection reset by peer))
  25. # [01:19] * Joins: weinigLap_ (n=weinig@17.255.105.160)
  26. # [01:21] * Quits: billmason (n=billmaso@ip156.unival.com) (".")
  27. # [01:27] * Joins: jgraham_ (n=jgraham@81-86-210-186.dsl.pipex.com)
  28. # [01:29] * Quits: jgraham (n=jgraham@81-86-223-179.dsl.pipex.com) (Read error: 110 (Connection timed out))
  29. # [01:33] * Quits: weinigLap (i=weinig@nat/apple/x-381797ab6be271dd) (Read error: 110 (Connection timed out))
  30. # [01:45] <Hixie> ok so my experience with JAWS is somewhat poor
  31. # [01:45] * Quits: weinigLap_ (n=weinig@17.255.105.160)
  32. # [01:45] <Hixie> i can't even get past the first screen of the installer without accessibility problems
  33. # [01:49] <Hixie> ok, got it past the first screen by cheating
  34. # [01:50] <Hixie> it installed stuff, then said it had to reboot, and then crashed my machine hard.
  35. # [01:50] <Hixie> had to hard-power-reset it
  36. # [01:54] * Joins: weinigLap (n=weinig@17.255.105.160)
  37. # [01:54] * Quits: Lachy (n=Lachlan@203-158-59-119.dyn.iinet.net.au) (Read error: 104 (Connection reset by peer))
  38. # [02:02] * Joins: karlUshi (n=karl@dhcp-247-173.mag.keio.ac.jp)
  39. # [02:20] * Quits: jgraham_ (n=jgraham@81-86-210-186.dsl.pipex.com) (Read error: 110 (Connection timed out))
  40. # [02:26] <Hixie> holy fornicating rabbits, if jaws is the state of the art in speech reading software i'm not _surprised_ that accessibility people are so cranky
  41. # [02:26] <Hixie> sweet jesus
  42. # [02:40] * Quits: weinigLap (n=weinig@17.255.105.160)
  43. # [02:56] * Joins: weinigLap (i=weinig@nat/apple/x-e10388a24d47d624)
  44. # [03:03] * Joins: MikeSmith (n=MikeSmit@58.157.21.205)
  45. # [03:41] * Quits: mpt (n=mpt@121-72-128-43.dsl.telstraclear.net) ("This computer has gone to sleep")
  46. # [03:43] * Quits: h3h (n=w3rd@66-162-32-234.static.twtelecom.net) ("|")
  47. # [03:43] * Quits: kingryan (n=kingryan@corp.technorati.com)
  48. # [03:44] * Joins: aroben (n=adamrobe@h46065d8e.area1.spcsdns.net)
  49. # [03:44] * Quits: aroben (n=adamrobe@h46065d8e.area1.spcsdns.net) (Read error: 104 (Connection reset by peer))
  50. # [03:45] * Joins: aroben (n=adamrobe@h46065d8e.area1.spcsdns.net)
  51. # [03:50] * Joins: mpt (n=mpt@121-72-128-43.dsl.telstraclear.net)
  52. # [03:53] <Dashiva> I thought m12n was bad enough, now we have a11y?
  53. # [04:05] <karlUshi> for a long time it seems http://www.google.com/search?q=a11y
  54. # [04:06] * Quits: mpt (n=mpt@121-72-128-43.dsl.telstraclear.net) ("Leaving")
  55. # [04:08] * Quits: aroben (n=adamrobe@h46065d8e.area1.spcsdns.net)
  56. # [04:22] * Quits: othermaciej (n=mjs@17.255.99.40)
  57. # [04:30] * Joins: mpt (n=mpt@121-72-128-43.dsl.telstraclear.net)
  58. # [04:33] * Quits: MikeSmith (n=MikeSmit@58.157.21.205) ("Less talk, more pimp walk.")
  59. # [04:47] * Quits: KevinMarks (i=KevinMar@nat/google/x-ae3d096f9a7b2381) ("The computer fell asleep")
  60. # [04:49] * Quits: dbaron (n=dbaron@corp-242.mountainview.mozilla.com) ("8403864 bytes have been tenured, next gc will be global.")
  61. # [05:02] * Joins: KevinMarks (n=KevinMar@65.sub-75-211-169.myvzw.com)
  62. # [05:11] * Quits: weinigLap (i=weinig@nat/apple/x-e10388a24d47d624) (Read error: 110 (Connection timed out))
  63. # [05:16] * Quits: KevinMarks (n=KevinMar@65.sub-75-211-169.myvzw.com) ("The computer fell asleep")
  64. # [05:23] * Joins: weinigLap (i=weinig@nat/apple/x-a73ac92ab72be097)
  65. # [05:57] <Hixie> wow, the DOM that IE makes for <!DOCTYPE HTML><form> sure is... inretesting
  66. # [06:33] * Joins: othermaciej_ (i=mjs@nat/apple/x-f12ecc97b138037b)
  67. # [06:39] <hsivonen> Hixie: I'm awake now
  68. # [06:41] * othermaciej_ is now known as othermaciej
  69. # [06:42] <Hixie> hsivonen: i replied to mail instead
  70. # [06:42] * Joins: MikeSmith (n=MikeSmit@tea12.w3.mag.keio.ac.jp)
  71. # [06:42] * Joins: billyjack (n=MikeSmit@tea12.w3.mag.keio.ac.jp)
  72. # [06:43] <hsivonen> Hixie: ok
  73. # [06:44] * Quits: billyjack (n=MikeSmit@tea12.w3.mag.keio.ac.jp) (Client Quit)
  74. # [06:44] * Quits: MikeSmith (n=MikeSmit@tea12.w3.mag.keio.ac.jp) (Client Quit)
  75. # [06:45] * Joins: MikeSmith (n=MikeSmit@tea12.w3.mag.keio.ac.jp)
  76. # [07:13] <Hixie> nearly done with this doctype thread
  77. # [07:13] <Hixie> sheesh
  78. # [07:18] <Hixie> yay, finally done with it
  79. # [07:21] * Quits: csarven (n=nevrasc@modemcable081.152-201-24.mc.videotron.ca)
  80. # [07:32] <Hixie> i wonder why the definition for the HTML innerHTML setter starts with "Otherwise,"
  81. # [07:39] * Joins: othermaciej_ (n=mjs@17.255.99.40)
  82. # [07:50] * hsivonen finds out he followed up to a post with already a large number of follow-ups that weren't properly threaded. :-(
  83. # [07:54] * Quits: othermaciej (i=mjs@nat/apple/x-f12ecc97b138037b) (Read error: 110 (Connection timed out))
  84. # [08:01] * Quits: othermaciej_ (n=mjs@17.255.99.40)
  85. # [08:09] * Joins: zcorpan_ (n=zcorpan@pat.se.opera.com)
  86. # [08:28] <hsivonen> annevk: my impl passed html5lib/testdata/tokenizer/test1.test on the first try after the new doctype stuff. yay
  87. # [08:30] <hsivonen> test2.test revealed one bug. fixed
  88. # [08:48] <Hixie> you guys have already got that implemented?
  89. # [08:48] <Hixie> sheesh
  90. # [08:48] <Hixie> talk about bleeding edge
  91. # [08:50] <hsivonen> Hixie: well, I implemented the tokenization part--not yet the tree builder part
  92. # [08:50] <Hixie> ah ok
  93. # [08:52] <zcorpan_> </><!doctype html> is another interesting case (because the token doesn't reach the tree construction stage). though handled the same as </ foo ><!doctype html> in browsers
  94. # [08:52] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  95. # [08:53] <Hixie> yeah i
  96. # [08:53] <Hixie> er
  97. # [08:54] <Hixie> yeah i'm sure there are lots of edge cases that act slightly differently between the spec and browsers
  98. # [08:54] <Hixie> those are usually the cases that aren't really important and that the browsers all do differently anyway
  99. # [08:54] <zcorpan_> perhaps
  100. # [08:55] * Joins: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  101. # [09:05] <hsivonen> people say that authors know HTML 4.01 and, therefore, they want to know the diff to HTML 5, but commentary suggests that usually people don't really know the HTML 4.01 details. witness optional tags
  102. # [09:06] <Hixie> i keep saying that
  103. # [09:06] <Hixie> people don't believe me though
  104. # [09:07] <othermaciej> I love the people staring at gape-jawed horror at the optional tags
  105. # [09:08] <othermaciej> and suggesting that XML syntax is a good way to teach HTML
  106. # [09:08] <othermaciej> *shudder*
  107. # [09:09] <zcorpan_> Hixie: the doctype 1024 bytes thing is firefox, not opera or ie. dunno about safari. reproducable from local disk
  108. # [09:09] <Hixie> zcorpan_: yeah, i reproduced it eventually myself too (with your help)
  109. # [09:09] <karlUshi> othermaciej: it is. XHTML syntax makes it a lot easier. believe me.
  110. # [09:09] <karlUshi> By experience
  111. # [09:09] <karlUshi> I have taught both languages
  112. # [09:10] <Hixie> zcorpan_: doesn't seem to happen for only spaces, only happens if there's some thing before the doctype other than whitespace
  113. # [09:10] <othermaciej> karlUshi: the problem is if you assume XML syntax actually applies
  114. # [09:10] <othermaciej> and start doing things like <div id="placeholder" />
  115. # [09:10] <othermaciej> or <script src="foo.js" />
  116. # [09:11] <Hixie> btw, the html5 parser spec is starting to get good enough that when people report bugs with them, it's usually the case that the bug is actually in one browser and that most of hte other browsers don't have that quirk
  117. # [09:11] <karlUshi> but it is not what people do :) this is a geek comment.
  118. # [09:11] <zcorpan_> Hixie: you can have whitespace within the doctype, with nothing before the doctype. if the > is not within the first 1024 bytes then firefox gets quirks mode
  119. # [09:11] * Quits: gavin (n=gavin@firefox/developer/gavin) (Remote closed the connection)
  120. # [09:11] <Hixie> <script src="foo.js" /> is far too common
  121. # [09:11] * Joins: gavin (n=gavin@people.mozilla.com)
  122. # [09:11] <Hixie> so common we might have to in fact put it in the spec, though i really hope not
  123. # [09:11] <othermaciej> <canvas /> is also distressingly common
  124. # [09:12] * othermaciej apologizes for that one
  125. # [09:12] <karlUshi> hehe
  126. # [09:12] <Hixie> zcorpan_: i had 1024 x ' ' followed by a doctype and i got standards mode. but a bogus comment then 1024 x ' ' then the doctype, and it's quirks.
  127. # [09:12] <Hixie> othermaciej: not so much on the web, only mostly in dashboard widgets, thankfully
  128. # [09:12] * karlUshi is going to look for his whips in the closets. oh and ropes
  129. # [09:12] <othermaciej> karlUshi: teaching people that some tags don't need a close tag seems simpler to me than teaching them that <foo /> is a self-closing tag, but can only be used for a fixed small set of tags
  130. # [09:12] <karlUshi> it is not because it depends on the tag
  131. # [09:13] <othermaciej> karlUshi: even though the XML spec you are nominally following says it can be used for anything
  132. # [09:13] <zcorpan_> Hixie: i don't get standards mode with 1024 x ' ' followed by a doctype in firefox
  133. # [09:13] <othermaciej> I agree that XML syntax would be easier to teach if you could actually use XML syntax
  134. # [09:13] <othermaciej> but as it is, teaching a well-structured version of HTML syntax seems better
  135. # [09:13] <karlUshi> plus things like I was typing yesterday on the channel
  136. # [09:13] <othermaciej> (i.e. tell people to close non-empty tags that don't need it to avoid confusion)
  137. # [09:15] * Quits: weinigLap (i=weinig@nat/apple/x-a73ac92ab72be097)
  138. # [09:17] <zcorpan_> Hixie: or wait, nm, you're right
  139. # [09:18] <karlUshi> weeeell, from my *practical* teaching experience, xhtml rules create far less misunderstanding. and what I heard from most teachers is the same. But we might have had different contacts with different people
  140. # [09:19] <othermaciej> a lot of people writing XHTML don't understand that the browser is not going to use an XML parser
  141. # [09:19] <othermaciej> (possibly most)
  142. # [09:20] <karlUshi> here again you see it on the geek side.
  143. # [09:21] <karlUshi> it is not relevant for most people to know which parser is used.
  144. # [09:21] <karlUshi> but for web developers when reading and maintaining the code it is relevant
  145. # [09:21] <karlUshi> hmmm
  146. # [09:21] <karlUshi> I have something in my head to publish on HTML viewed from different angles
  147. # [09:21] <karlUshi> and people refusing to accept the other camps
  148. # [09:22] <karlUshi> it is kind of funny because I do the same kind of arguments on both sides
  149. # [09:22] <othermaciej> here's the thing, it's not just that people are unsure
  150. # [09:22] <othermaciej> they are deeply factually convinced that XHTML is parsed as XML when served as text/html, or that at least it should be
  151. # [09:22] <othermaciej> even prominent w3c working group members are often confused on this point
  152. # [09:23] <hsivonen> Hixie: I definitely didn't mean to ask for a 1024 char limit when I asked for doing what Gecko and WebKit do
  153. # [09:23] <karlUshi> it is not a problem for web developers :)
  154. # [09:23] <othermaciej> when many people actively believe something false, that says to me there is a problem
  155. # [09:23] <othermaciej> if web developers choose not to think about it that is one thing, but like I said many have an active belief that is contrary to fact
  156. # [09:24] <Hixie> othermaciej: even w3c xhtml2 working group members are often confused on this point! and they invented the spec in question!
  157. # [09:24] <Hixie> hsivonen: ah ok
  158. # [09:24] <Hixie> hsivonen: good :-)
  159. # [09:24] <othermaciej> if I believed my CPU was a PPC chip not an Intel chip, it probably wouldn't matter to me most of the time
  160. # [09:24] <othermaciej> but the times that it does, it would seriously mess me up
  161. # [09:24] <othermaciej> especially if I refused to accept evidence that it was indeed an Intel chip
  162. # [09:25] <hsivonen> othermaciej: :-)
  163. # [09:25] <karlUshi> othermaciej: good example. When does it really matter? I'm really curious.
  164. # [09:25] * karlUshi having is life on macs for more than 10 years now
  165. # [09:25] <Hixie> annevk: yt?
  166. # [09:26] <othermaciej> karlUshi: as a developer, I have to care when writing inline assembly code, which is rare but sometimes necessary
  167. # [09:26] <zcorpan_> karlUshi: people use things like <span/> and expect it to close itself
  168. # [09:26] <Hixie> annevk: so you asked for <!-->--> to be treated like <!--->--&gt;
  169. # [09:26] <karlUshi> othermaciej: here again, talking about ubergeeks
  170. # [09:26] <Hixie> annevk: but it turns out only IE does that in no-quirks mode
  171. # [09:26] <othermaciej> karlUshi: as a user, I need to realize that PPC-only binaries will be running in emulation and so will be slower and will use a lot of memory
  172. # [09:26] <othermaciej> karlUshi: well, most people don't have to care what their CPU is
  173. # [09:26] <Hixie> annevk: so, do we want to change no-quirks-mode comment parsing, or do we want to introduce a quirks-mode tokeniser difference?
  174. # [09:26] <karlUshi> people who deals with xslt and xquery etc. Yes I agree with you will have to know what is XML
  175. # [09:27] <karlUshi> not most web developers
  176. # [09:27] <othermaciej> karlUshi: but if you call tech support and tell them you have a PowerPC chip instead of "I don't know", you could have problems
  177. # [09:27] <othermaciej> it's better not to know than to be convinced of the wrong thing
  178. # [09:27] <othermaciej> if you don't know, at least you know that you should look it up if you need to know
  179. # [09:27] <zcorpan_> Hixie: the former, imho, unless it breaks pages
  180. # [09:28] <Hixie> i wonder how to find out whether it breaks pages
  181. # [09:28] <Hixie> hm
  182. # [09:28] <karlUshi> Many people say they machine name at best, (sometimes the color and the shape) and when they bought it. The rest is
  183. # [09:28] <annevk> am now
  184. # [09:28] <annevk> Hixie, I think if IE does it it should be safe enough for other browsers
  185. # [09:29] <annevk> <!--> and <!---> btw
  186. # [09:29] <Hixie> (yeah)
  187. # [09:29] <Hixie> hmm
  188. # [09:29] <Hixie> that's a plausible argument i guess
  189. # [09:29] <annevk> it is for parsing
  190. # [09:29] <Hixie> right then
  191. # [09:29] <othermaciej> karlUshi: right, many people don't know what their CPU is, but few are certain that it's something other than what it is
  192. # [09:29] <annevk> if this was about DOM methods...
  193. # [09:30] <Hixie> we'll see what browser vendors say when they try to implement it! :-)
  194. # [09:30] <hsivonen> karlUshi: even if people don't know which CPU they have, they aren't vehemently believing that they have a different CPU than what they actually have
  195. # [09:32] <karlUshi> interesting, I hear people from this group asking for being real with people, and then sometimes to have people to require extreme knowledge of the technology... when obviously xhtml syntax rules worked for most people and made them developer beautiful xhtml/css web sites. :)
  196. # [09:32] <karlUshi> not. logical. at. all.
  197. # [09:32] <karlUshi> anyway
  198. # [09:32] <karlUshi> need to move my butt to the train
  199. # [09:32] * Quits: karlUshi (n=karl@dhcp-247-173.mag.keio.ac.jp) ("Where dwelt Ymir, or wherein did he find sustenance?")
  200. # [09:33] * hsivonen wonders how misrepresenting testable facts is being real
  201. # [09:33] <hsivonen> (i.e. teaching people that XHTML as text/html gets an XML treatment)
  202. # [09:34] <annevk> I wonder what the difference is between learning for which tags you can write <foo/> and for which you always have to write <bar></bar> and learning HTML
  203. # [09:34] <othermaciej> because the former is well-formed XML and the latter is tag soup
  204. # [09:34] <hsivonen> on the bright side, even if XHTML brings out irrational beliefs it doesn't make people as hostile as syndication feeds :-)
  205. # [09:35] <annevk> othermaciej, I see it now, makes perfect sense!
  206. # [09:35] * Joins: weinigLap (n=weinig@c-67-188-78-122.hsd1.ca.comcast.net)
  207. # [09:35] * Quits: weinigLap (n=weinig@c-67-188-78-122.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  208. # [09:36] * Joins: weinigLap (n=weinig@c-67-188-78-122.hsd1.ca.comcast.net)
  209. # [09:37] * othermaciej takes a bow
  210. # [09:38] <weinigLap> claps
  211. # [09:38] <Hixie> ok this comment thing is going to be a bitch
  212. # [09:38] <annevk> http://validator.whatwg.org/ is cool!
  213. # [09:38] <Hixie> to get the right parse errors i have to add two new states!
  214. # [09:38] <Hixie> annevk: heh, it's been there since forever (though it used to give a 403)
  215. # [09:38] <Hixie> but the link seemed useful, indeed
  216. # [09:42] * Quits: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  217. # [09:46] <MikeSmith> so what reason do you give to those already indoctrinated in closing-tag-required-on-empty-elements for why <script src="foo.js" /> is not conformant?
  218. # [09:47] * Joins: jgraham (n=jgraham@81-86-214-247.dsl.pipex.com)
  219. # [09:48] <annevk> MikeSmith, IE doesn't support that?
  220. # [09:48] <annevk> nor do lots of older browsers
  221. # [09:49] <annevk> it's not backwards compatible at all
  222. # [09:49] <Hixie> MikeSmith: they're writing HTML4. And it's not conforming HTML4.
  223. # [09:50] <Hixie> MikeSmith: for the same reason that {script} isn't conforming HTML4. it's just not HTML4's syntax.
  224. # [09:57] <MikeSmith> or to point out that you can create a well-formed, valid XHTML1 document that is no HTML4-conformant ... ?
  225. # [09:58] <MikeSmith> not HTML4-conformant
  226. # [09:58] <othermaciej> it's pretty hard to make a document that's both conforming XHTML1 and conforming HTML4
  227. # [09:58] <annevk> it's impossible
  228. # [09:58] <zcorpan_> annevk: nope, you can play with PIs
  229. # [09:59] <zcorpan_> they end with > in html and ?> in xml
  230. # [09:59] * annevk wonders how that would solve stuff
  231. # [09:59] <Hixie> it is indeed possible, though not at all useful
  232. # [09:59] <hsivonen> IIRC, there's one on damowmow
  233. # [09:59] <Hixie> indeed
  234. # [10:00] <Hixie> http://damowmow.com/playground/html-or-xml.html
  235. # [10:00] <Hixie> http://damowmow.com/playground/html-or-xml.xml
  236. # [10:00] <Hixie> (same file)
  237. # [10:00] <Hixie> technically it's not conforming to either HTML4 nor XHTML1, but it validates as both
  238. # [10:01] <zcorpan_> Hixie: why is it not conforming?
  239. # [10:01] <Hixie> PIs aren't allowed
  240. # [10:01] <Hixie> iirc
  241. # [10:04] <annevk> Hixie, do you want replies to e-mails where I agree with your response (even if phrased as question)?
  242. # [10:04] * annevk isn't keen on flooding the list with "Yeah", "Yeah", ...
  243. # [10:05] <annevk> Hixie, cool
  244. # [10:05] <hsivonen> is a conforming application of SGML allowed to ban PIs?
  245. # [10:05] * hsivonen guesses no
  246. # [10:05] * hsivonen assumes HTML 4.01 isn't conforming
  247. # [10:06] <zcorpan_> html4 says that authors are discouraged from using sgml features with little support in html uas, or some such
  248. # [10:06] <zcorpan_> don't think xhtml bans pis
  249. # [10:07] <zcorpan_> except in appendix c
  250. # [10:09] <Hixie> annevk: no, don't bother sending mail unless you want me to change the spec
  251. # [10:09] <Hixie> (i mean, you can, but i'm not tracking the issues that i've replied to, so it doesn't really do much)
  252. # [10:10] <annevk> good
  253. # [10:12] * hsivonen still does not understand why Java JSON impls don't inherit JSONArray from LinkedList and JSONObject from HashMap
  254. # [10:13] <othermaciej> wouldn't you want an array to be an array, instead of a linked list?
  255. # [10:13] <annevk> Hixie, thanks for aligning the quirks mode sniffing with the html5lib implementation (whether intentional or not)
  256. # [10:14] * Quits: weinigLap (n=weinig@c-67-188-78-122.hsd1.ca.comcast.net) (Remote closed the connection)
  257. # [10:14] <othermaciej> also, wouldn't restricting the allowed key/value types for HashMap violate the Liskov Substitution Principle?
  258. # [10:14] * Joins: weinigLap (n=weinig@c-67-188-78-122.hsd1.ca.comcast.net)
  259. # [10:15] <hsivonen> othermaciej: given what "array" means in JSON, the obvious mutable Java mapping is an instance of the List interface
  260. # [10:16] <othermaciej> hsivonen: I'm assuming an array in JSON is much like a JavaScript Array
  261. # [10:16] <othermaciej> which is a sparse array, not a linked list
  262. # [10:16] * othermaciej is not sure if JSON allows the elision syntax, if not, it's non-sparse
  263. # [10:17] <hsivonen> othermaciej: not having a JSONValue common subtype indeed would make generics with JSONArray and JSONObject ugly, but having those take java.lang.Objects with magic restrictions would eliminate annoying boxing code
  264. # [10:18] <hsivonen> othermaciej: as far as I can tell, JSONArray is conceptually a java.util.List
  265. # [10:18] <hsivonen> othermaciej: doesn't matter if it is backed by LinkedList or ArrayList
  266. # [10:18] <othermaciej> well, performance-wise it does
  267. # [10:18] <othermaciej> it's almost never good to use a linked list instead of an array
  268. # [10:19] <hsivonen> of course, but in API terms both are better than this boxing/unboxing drudgery I have to deal with
  269. # [10:19] * othermaciej wonders what the difference is between ArrayList and Vector
  270. # [10:19] <Hixie> annevk: what did i change?
  271. # [10:19] <hsivonen> othermaciej: ArrayList doesn't do synchronized on its own
  272. # [10:20] <hsivonen> Vector is part of the overly thread-safe legacy
  273. # [10:20] <othermaciej> I see
  274. # [10:20] <hsivonen> would be cool to update onvdl to use non-synchronized collections some day
  275. # [10:21] <annevk> Hixie, the formatting and moving down the two doctypes for which the systemid has to be missing
  276. # [10:23] * Hixie looks up the Liskov substitution principle and wonders why it has such a fancy name instead of being called "common sense"
  277. # [10:23] <Hixie> annevk: i did it purely for readability reasons, but i'm glad it made things better :-)
  278. # [10:24] <othermaciej> Hixie: people shows more respect if you use a fancy term instead of saying "that violates common sense"
  279. # [10:24] <Hixie> fair point
  280. # [10:25] <Hixie> i had the same reaction when i learnt of De Morgan's laws at university
  281. # [10:26] <hsivonen> If I some day write my own JSON mapper for Java, JSONString will be a straight java.lang.String, JSONArray will be java.util.List<Object> and JSONObject will be java.util.Map<String, Object>
  282. # [10:26] <Hixie> i was like "wait, this has a name? i've been doing this since i was 10"
  283. # [10:26] <annevk> whatwg.org down?
  284. # [10:27] <Hixie> it's having issues
  285. # [10:28] <annevk> oh well, there are two repositories now :)
  286. # [10:29] <annevk> maybe someone should get ambitious and make the html5.org tracker handle timeouts by switching repository
  287. # [10:29] <Hixie> http://www.dreamhoststatus.com/ usually has information about why whatwg.org or hixie.ch are down
  288. # [10:29] <Hixie> though not this time
  289. # [10:32] <othermaciej> hsivonen: yeah, too bad you can't make the generics quite exactly perfect without introducing a base class for simple values
  290. # [10:32] <annevk> it's back up it seems
  291. # [10:32] <othermaciej> I guess you have to either box primitive types and strings or make the interface a little looser than Java likes
  292. # [10:33] <hsivonen> othermaciej: the latter is so much nicer to program with
  293. # [10:33] <hsivonen> othermaciej: also, in this case, it would have made equal() sane by default
  294. # [10:33] * hsivonen had to write an external JSON equality test
  295. # [10:33] <othermaciej> :-(
  296. # [10:33] <hsivonen> equals()
  297. # [10:34] <hsivonen> anyway, all that code is now done
  298. # [10:34] <hsivonen> and tests pass
  299. # [10:42] <annevk> Hixie, several changes such as &&, </ in <script>, etc. have only been updated in the parsing section and not in the "writing" equivalent sections
  300. # [10:43] <Hixie> oh, crap
  301. # [10:43] <Hixie> any idea what the "etc" are?
  302. # [10:44] <annevk> the other &... thingies
  303. # [10:44] * annevk checks for more
  304. # [10:44] <annevk> that's it
  305. # [10:44] <annevk> although maybe <p>test</body> needs something... dunno
  306. # [10:46] * Quits: weinigLap (n=weinig@c-67-188-78-122.hsd1.ca.comcast.net) (Read error: 113 (No route to host))
  307. # [10:51] * Joins: ROBOd (n=robod@86.34.246.154)
  308. # [10:52] * Joins: BenWard (i=BenWard@nat/yahoo/x-001a29df7e8451b9)
  309. # [10:59] * Joins: Ducki (i=Alex@dialin-145-254-189-212.pools.arcor-ip.net)
  310. # [11:03] <Hixie> good lord
  311. # [11:03] <Hixie> i can't work out how to write the requirements on magic cdata comment stuff for authors
  312. # [11:06] * Joins: hendry (i=hendry@conference/debconf/x-50485287dc1f604b)
  313. # [11:07] * Quits: zcorpan_ (n=zcorpan@pat.se.opera.com) (Read error: 110 (Connection timed out))
  314. # [11:07] <annevk> you already did that
  315. # [11:17] <Hixie> turns out it's wrong
  316. # [11:18] <Hixie> it disallows <!-- <!-- -->
  317. # [11:19] <annevk> that makes me wonder what <!-- <!--> --> does
  318. # [11:19] <Hixie> it disallows that too
  319. # [11:20] <Hixie> both should be allowed
  320. # [11:20] <annevk> you can nest them?
  321. # [11:23] * othermaciej is now known as om_sleep
  322. # [11:23] <Hixie> no
  323. # [11:23] <Hixie> <!-- <!--> --> is equivalent to <!- xx--> xxx
  324. # [11:33] * Joins: zcorpan_ (n=zcorpan@pat.se.opera.com)
  325. # [11:38] * holst_ is now known as didymos
  326. # [11:44] <Hixie> right, fixed
  327. # [11:53] <Hixie> ugh http://bugs.webkit.org/show_bug.cgi?id=12646
  328. # [11:53] <Hixie> html5 breaking pages
  329. # [11:53] <Hixie> bummer
  330. # [11:57] <zcorpan_> is it <h3><h4> vs <h3><a><h4>?
  331. # [11:57] <Hixie> yes
  332. # [11:59] <Hixie> wait... IE lets you nest them anyway
  333. # [11:59] <Hixie> wtf
  334. # [12:00] <zcorpan_> indeed
  335. # [12:00] <annevk> the rendering doesn't change though
  336. # [12:00] <annevk> nested <h1> keep the same font size
  337. # [12:01] <Hixie> sure, because they use absolute font sizes
  338. # [12:01] <annevk> I suppose that might have been the reason for other browsers to not do the nesting
  339. # [12:01] <zcorpan_> <h1><p>
  340. # [12:01] <Hixie> we could do that too with the 'rem' units
  341. # [12:01] <Hixie> hah
  342. # [12:01] <Hixie> IE is weird
  343. # [12:02] <Hixie> all browsers do <h1><p> as nesting
  344. # [12:02] <Hixie> as does the spec
  345. # [12:02] <zcorpan_> ah, ok
  346. # [12:03] <Hixie> what should we do? allow header nesting and require the stylesheet to use 'rem' or 'px' units?
  347. # [12:03] <Hixie> or special-case <a>?
  348. # [12:03] <Hixie> hmm
  349. # [12:03] <annevk> <h1><p>x</h1>x :(
  350. # [12:04] <Hixie> ":-(" ?
  351. # [12:04] <annevk> I get red text nodes in IE
  352. # [12:04] <Hixie> interoperable for me
  353. # [12:04] <Hixie> oh well yes
  354. # [12:04] <Hixie> IE goes red at a moment's notice
  355. # [12:04] <annevk> heh
  356. # [12:04] <annevk> I'd go for nested headers with rem I think...
  357. # [12:05] <annevk> (would be nice if rem took <body> into account...)
  358. # [12:06] <Hixie> it's sad since every other browser does it the same way
  359. # [12:06] <hsivonen> annevk: got tests for the crazy [R]CDATA escape flag?
  360. # [12:07] <annevk> yeah
  361. # [12:07] <annevk> tests5.dat
  362. # [12:07] <annevk> html5lib doesn't pass them though
  363. # [12:07] <hsivonen> annevk: ah. thanks. no tokenizer-level tests, though?
  364. # [12:08] <hsivonen> annevk: is it ok to write and check in some even if html5lib itself doesn't pass them yet?
  365. # [12:08] <hsivonen> annevk: shall I start a new file?
  366. # [12:08] <annevk> hsivonen, please make it a separate file
  367. # [12:08] <hsivonen> ok
  368. # [12:08] <annevk> hsivonen, I suppose some people want to disable it like they did with html5
  369. # [12:08] <annevk> euh, test5
  370. # [12:11] * Joins: ddfreyne (n=ddfreyne@d54C57894.access.telenet.be)
  371. # [12:13] * Quits: ddfreyne (n=ddfreyne@unaffiliated/ddfreyne) (Remote closed the connection)
  372. # [12:13] <Hixie> wouldn't tests that fail be the most useful kind of test?
  373. # [12:14] <hsivonen> Hixie: in TDD you want to pass tests--not fail :-)
  374. # [12:14] <Hixie> tdd?
  375. # [12:15] <zcorpan_> is the .constructor attribute specced anywhere? (can i use it in test cases?)
  376. # [12:15] <Hixie> zcorpan_: try ECMA262
  377. # [12:16] <hsivonen> Hixie: Test-Driven Development
  378. # [12:18] <hsivonen> argh. the % operator in Java is crazy
  379. # [12:18] <hsivonen> sane in Python
  380. # [12:18] <Hixie> ah
  381. # [12:18] <Hixie> well, sure, you want the tests to pass
  382. # [12:19] <Hixie> but when you write them they should fail
  383. # [12:19] <Hixie> new tests that pass seem pointless :-) (except for regression testing, of course, but that's boring :-P)
  384. # [12:19] * hsivonen failed due to -1 % 4 resulting in -1 instead of 3
  385. # [12:20] <zcorpan_> Hixie: thanks
  386. # [12:21] * Hixie comes across an e-mail showing yet another difference between IE and all other browsers
  387. # [12:21] <Hixie> <ol> <li> xxx </li> yyy </ol>
  388. # [12:21] <zcorpan_> yup
  389. # [12:21] <Hixie> i guess i'll sleep on it
  390. # [12:22] <Hixie> since we don't have a bug report for this one i'm tempted to leave it
  391. # [12:22] <annevk> I think we're fine with aligning more with IE
  392. # [12:22] * Joins: maikmerten (n=maikmert@T634f.t.pppool.de)
  393. # [12:22] <zcorpan_> in wysiwyg editors that use contentEditable or designMode, a nested list takes the form <ul><li>foo</li><ul><li>bar</li></ul></ul>
  394. # [12:22] <Hixie> if we don't, we'll end up putting comments and spaces in the wrong place
  395. # [12:22] <Hixie> zcorpan_: good times
  396. # [12:22] * hsivonen makes his first check-in to html5lib
  397. # [12:22] <zcorpan_> if you write content with ie the end result is conforming because the </li> is ignored. if you write with other browsers the end result is non-conforming
  398. # [12:23] <zcorpan_> people blame other browsers
  399. # [12:23] <Hixie> yeah
  400. # [12:23] <Hixie> oh?
  401. # [12:23] <Hixie> uri to blame-giving?
  402. # [12:23] <Hixie> i haven't seen people complain about that
  403. # [12:23] <Hixie> that's interesting
  404. # [12:23] <Hixie> i'd love to read more
  405. # [12:23] <zcorpan_> s/people/wysiwyg tool authors/
  406. # [12:24] <zcorpan_> only over IM
  407. # [12:24] <zcorpan_> in swedish
  408. # [12:24] <Hixie> heh ok
  409. # [12:24] <Hixie> well changing these things is very risky and expensive
  410. # [12:24] <Hixie> but we'll see
  411. # [12:24] <Hixie> first though, i shall sleep
  412. # [12:24] <Hixie> nn
  413. # [12:24] <zcorpan_> nn
  414. # [12:24] <hsivonen> nn
  415. # [12:26] <annevk> hmm
  416. # [12:26] <annevk> handling <!-- in CDATA requires either rearchitecture or hooking into the tree construction stage
  417. # [12:27] <hsivonen> annevk: huh. WFM in the tokenizer
  418. # [12:27] <annevk> and I don't have a clear plan for the rearchitecture either
  419. # [12:27] <annevk> hsivonen, does your tokenizer have knowledge of tag names?
  420. # [12:27] <hsivonen> annevk: it knows about void elements
  421. # [12:27] <zcorpan_> "The location attribute of the HTMLDocument interface must return the Location object for that Document object." -- i don't know how to test this
  422. # [12:30] <annevk> hsivonen, is your impl online somewhere?
  423. # [12:39] * Joins: rubys (n=rubys@cpe-075-182-064-252.nc.res.rr.com)
  424. # [12:39] <hsivonen> annevk: not yet. I had emailed cvsdude support about it. they just emailed my that I have to ask fantasai, so I emailed her to flip the switch
  425. # [12:40] <hsivonen> annevk: If you want it now, I can upload a .zip somewhere
  426. # [12:40] <hsivonen> s/my/me/
  427. # [12:41] <annevk> I can wait I suppose
  428. # [12:41] <annevk> there are some other changes I want to make
  429. # [12:41] <hsivonen> creating a dump now
  430. # [12:42] <rubys> anybody have plans to fix the tests that hsivonen just checked in?
  431. # [12:42] <hsivonen> rubys: fix the tests or fix the impl to pass the tests?
  432. # [12:42] <annevk> yes, but I'm not sure how
  433. # [12:42] <annevk> (talking about fixing the impl here)
  434. # [12:43] <rubys> hsivonen: I'm just trying to figure out whether this will be fixed shortly, or if these tests should be added to the todo list.
  435. # [12:44] <annevk> If someone can give me a plan for how to do it I'll fix the Python code
  436. # [12:44] <annevk> until that happens it's prolly TODO work
  437. # [12:44] <hsivonen> annevk: http://hsivonen.iki.fi/htmlparser-dump.zip
  438. # [12:44] <hsivonen> annevk: look in nu.validator.*
  439. # [12:44] <hsivonen> annevk: fi.iki.* is legacy
  440. # [12:45] <hsivonen> annevk: the impl should be in sync with June 17th spec for everything except entities which is in sync with June 12th
  441. # [12:49] * Joins: yod (n=ot@bas11-montreal02-1128535778.dsl.bell.ca)
  442. # [12:49] <hsivonen> annevk: see the last lines of read() as well as dataState()
  443. # [12:53] <annevk> HTML4 errors, nice
  444. # [12:54] <hsivonen> annevk: as for the plan, I suggest you do what I'm doing, but you need to figure which one of Python's data structures is the most effient one for that kind of low level stuff
  445. # [12:54] * hsivonen guesses either list or string
  446. # [12:56] <annevk> the problem is getting the last set of characters
  447. # [12:57] <annevk> getting this to work fast is another issue...
  448. # [12:57] <annevk> for instance, since < triggers closetagopen state that will emit a character '<' on its own
  449. # [12:57] * Joins: Ducki_ (n=Alex@dialin-212-144-083-124.pools.arcor-ip.net)
  450. # [12:57] <annevk> which is only accessible from the tree construction stage
  451. # [12:58] <hsivonen> annevk: can't whatever you use to read the next char put the char into a four-slot ring buffer?
  452. # [12:59] <annevk> just for the data state?
  453. # [12:59] <annevk> that makes some sense
  454. # [12:59] <hsivonen> annevk: don't you have an equivalent for my read()?
  455. # [12:59] <annevk> I do
  456. # [12:59] <annevk> so that would actually make it fairly trivial :)
  457. # [13:00] <annevk> I think...
  458. # [13:02] <hsivonen> if (contentModelFlag != ContentModelFlag.PCDATA) {
  459. # [13:02] <hsivonen> prevFourPtr++;
  460. # [13:02] <hsivonen> prevFourPtr %= 4;
  461. # [13:02] <hsivonen> prevFour[prevFourPtr] = c;
  462. # [13:02] <hsivonen> }
  463. # [13:02] <hsivonen> return c;
  464. # [13:03] <hsivonen> where the if may be a premature optimization
  465. # [13:04] * Quits: Ducki (i=Alex@dialin-145-254-189-212.pools.arcor-ip.net) (Read error: 104 (Connection reset by peer))
  466. # [13:04] <rubys> in python/ruby you do just as well with push and pop(0)
  467. # [13:05] <hsivonen> rubys: ok. I'm not familiar enough with the performance characteristics of python/ruby date structures for this kind of thing
  468. # [13:23] <annevk> hsivonen, do you just do that in the dataState?
  469. # [13:23] * annevk wonders if it covers <!</-- well enough
  470. # [13:24] <hsivonen> annevk: didn't Hixie spec it for the data state only?
  471. # [13:25] <hsivonen> annevk: read() updates the ring buffer from underneath the states
  472. # [13:28] <annevk> ah ok, that clarifies it
  473. # [13:29] <hsivonen> it's crazy how long the read() method needs to be in order to get all the right things done
  474. # [13:35] <annevk> our read method is on the iput stream object
  475. # [13:37] <hsivonen> for efficient SAX character data reporting, the tokenizer in Java needs to have access to its buffer
  476. # [13:48] * Quits: BenWard (i=BenWard@nat/yahoo/x-001a29df7e8451b9) (Remote closed the connection)
  477. # [14:18] <annevk> you actually only need to look at the last three characters, no?
  478. # [14:29] <zcorpan_> "The href attribute returns the address of the page represented by the associated Document object, as an absolute IRI reference." -- this means that both percent-encoded and not percent-encoded are ok, right?
  479. # [14:32] <annevk> prolly
  480. # [14:50] <annevk> reserializing this document gets ugly: <script><!--
  481. # [14:50] <hsivonen> annevk: yeah, the current character has already been seen, so it is sufficient to examine the three previous ones
  482. # [14:57] <annevk> hmm
  483. # [14:57] <annevk> it's sort of working but I'm hitting weird bugs I can't figure out
  484. # [14:57] * Joins: Ducki__ (n=Alex@dialin-145-254-189-135.pools.arcor-ip.net)
  485. # [15:04] * Joins: briansuda (n=briansud@82.221.34.106)
  486. # [15:05] * Quits: Ducki_ (n=Alex@dialin-212-144-083-124.pools.arcor-ip.net) (Read error: 113 (No route to host))
  487. # [15:23] * Ducki__ is now known as Ducki
  488. # [15:23] <annevk> hah, I think I nailed it
  489. # [15:23] <annevk> running tests it doesn't seem slower so far
  490. # [15:24] <annevk> time to update the tests
  491. # [15:37] * Joins: jcgregorio (i=chatzill@nat/ibm/x-fefa83629c897eff)
  492. # [15:39] <annevk> hsivonen, one of your tests has a bug
  493. # [15:40] <annevk> hmm
  494. # [15:41] <hsivonen> annevk: oh. which one?
  495. # [15:41] <annevk> foo<!--></bar><!-->baz</bar>
  496. # [15:41] <annevk> <!--> is either a single comment or the start of one
  497. # [15:42] <annevk> it's certainly not character data
  498. # [15:42] <hsivonen> annevk: why not?
  499. # [15:42] <annevk> after the first </bar> is emitted you switch to PCDATA
  500. # [15:43] <annevk> we do at least, I suppose that could differ per implementation
  501. # [15:44] <hsivonen> oh, right. the latter one
  502. # [15:44] <annevk> yeah, the second
  503. # [15:44] <zcorpan_> annevk: <!--> can be the start of a comment?
  504. # [15:44] <annevk> it also says "end tag surrounded"
  505. # [15:44] <annevk> zcorpan_, that was previously the case
  506. # [15:44] <zcorpan_> ah
  507. # [15:45] <annevk> hsivonen, that should also be changed I suppose
  508. # [15:45] <hsivonen> I start to suspect my test harness or impl is broken
  509. # [15:46] <hsivonen> brokenness with harness
  510. # [15:46] * hsivonen blushes
  511. # [15:47] <hsivonen> my impl is totally b0rked, too
  512. # [15:55] <hsivonen> my harness was so b0rked it isn't even funny
  513. # [15:57] <annevk> another advantage of multiple implementations
  514. # [16:05] <annevk> our test coverage is pretty good btw
  515. # [16:05] <annevk> each change I make triggers at least one error in the testsuite
  516. # [16:05] <annevk> I usually add some regression tests while I'm at it
  517. # [16:05] * Joins: BenWard (i=BenWard@nat/yahoo/x-5150249850ad4923)
  518. # [16:06] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  519. # [16:06] * Quits: MikeSmith (n=MikeSmit@tea12.w3.mag.keio.ac.jp) ("Less talk, more pimp walk.")
  520. # [16:08] * Quits: briansuda (n=briansud@82.221.34.106)
  521. # [16:12] <hsivonen> annevk: has the handling of <!--> in PCDATA changed since June 17th?
  522. # [16:12] <annevk> yes
  523. # [16:12] <annevk> there are two new comment states to handle <!--> and <!---> as near-empty incorrect comments
  524. # [16:12] <hsivonen> argh
  525. # [16:13] <hsivonen> I guess I have to go diffing the spec again
  526. # [16:13] <annevk> you misunderstand, this is a good thing :)
  527. # [16:13] <hsivonen> sure
  528. # [16:14] <hsivonen> annevk: thanks
  529. # [16:16] <annevk> I think I'll implement that now and see what breaks
  530. # [16:17] * Joins: briansuda (n=briansud@82.221.34.106)
  531. # [16:25] * Joins: SavageX (n=maikmert@L9a93.l.pppool.de)
  532. # [16:38] <annevk> hsivonen, I checked in basic <!--> and <!---> tokenizer tests
  533. # [16:42] <rubys> annevk: I'm seeing two failures w/python, is that what you are seeing?
  534. # [16:42] * Quits: maikmerten (n=maikmert@T634f.t.pppool.de) (Read error: 110 (Connection timed out))
  535. # [16:43] <annevk> I have three
  536. # [16:43] <annevk> I suspect one of them is just something on my side
  537. # [16:43] <annevk> There's one failure in escapeFlag, but that's because the testcase has to be fixed
  538. # [16:43] <rubys> do a svn up... you might not have t.broyer's fix
  539. # [16:43] <annevk> and there's a failure with respect to newlines
  540. # [16:43] <annevk> I've no idea how to fix that
  541. # [16:44] <annevk> I got his fixes
  542. # [16:44] <rubys> when the code stabilizes, I'll take a look at test_newlines
  543. # [16:48] <rubys> ... which I guess is now (down to one failure)
  544. # [16:48] * Joins: Jero (n=Jero@d207230.upc-d.chello.nl)
  545. # [16:49] <annevk> yeah, for the moment
  546. # [16:49] * Joins: billmason (n=billmaso@ip156.unival.com)
  547. # [16:55] <rubys> fixed
  548. # [16:57] * Joins: Ducki_ (n=Alex@dialin-145-254-187-119.pools.arcor-ip.net)
  549. # [17:00] <annevk> cool
  550. # [17:02] <rubys> planning to break more stuff? :-) Or is it safe to try to port these changes to Ruby now?
  551. # [17:04] <annevk> heh, I think I'll stop doing html5lib for the rest of the day
  552. # [17:08] <annevk> things we need to do at some point:
  553. # [17:08] <annevk> * fix the new innerHTML stuff (adding a newline for <pre> and <textarea>)
  554. # [17:08] <annevk> * fix <isindex>
  555. # [17:08] <annevk> * implement almost standards mode
  556. # [17:08] <annevk> * <p></body>
  557. # [17:09] <rubys> "almost standards mode" doesn't apply to fragments, does it?
  558. # [17:10] <annevk> currently quirks mode and almost standards mode don't affect parsing at all
  559. # [17:10] <annevk> they're just determined during tree construction
  560. # [17:10] <rubys> ah, gotcha
  561. # [17:12] <rubys> why did you comment out #import hotshot, hotshot.stats in mockParser?
  562. # [17:13] <annevk> oh, that happened on accident I think
  563. # [17:13] <annevk> I don't have hotshot here and wanted to play with the other parts
  564. # [17:13] <rubys> ok, I'll include that in my next commit.
  565. # [17:14] <rubys> I'll move the import down to where it is needed
  566. # [17:23] * Quits: Ducki (n=Alex@dialin-145-254-189-135.pools.arcor-ip.net) (Read error: 110 (Connection timed out))
  567. # [17:37] * Quits: briansuda (n=briansud@82.221.34.106)
  568. # [17:48] * Quits: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  569. # [17:54] * Joins: mitsuhiko (n=blackbir@ubuntu/member/mitsuhiko)
  570. # [18:13] * Quits: zcorpan_ (n=zcorpan@pat.se.opera.com) (Read error: 110 (Connection timed out))
  571. # [18:22] * Joins: tantek (n=tantek@137.164.255.50)
  572. # [18:26] * Joins: MikeSmith (n=MikeSmit@p62059-adsau18honb3-acca.tokyo.ocn.ne.jp)
  573. # [18:26] * Joins: h3h (n=w3rd@66-162-32-234.static.twtelecom.net)
  574. # [18:27] * Quits: hendry (i=hendry@conference/debconf/x-50485287dc1f604b) (Read error: 110 (Connection timed out))
  575. # [18:33] * Joins: weinigLap (i=weinig@nat/apple/x-b4de4f474b691035)
  576. # [18:36] <mitsuhiko> is there lxml support for html5lib around somewhere?
  577. # [18:36] <mitsuhiko> i want xpath ;)
  578. # [18:43] * Quits: BenWard (i=BenWard@nat/yahoo/x-5150249850ad4923) ("Fades out again…")
  579. # [18:43] * Quits: tantek (n=tantek@137.164.255.50)
  580. # [18:47] * Joins: aroben (n=adamrobe@17.255.98.199)
  581. # [18:48] * Quits: aroben (n=adamrobe@17.255.98.199) (Client Quit)
  582. # [18:48] * Joins: aroben (n=adamrobe@17.255.98.199)
  583. # [18:49] * Joins: aroben_ (n=adamrobe@17.203.15.248)
  584. # [18:51] <rubys> libxml2 is supported in python html5lib
  585. # [18:55] * Joins: tantek (n=tantek@corp.technorati.com)
  586. # [18:58] * Quits: Ducki_ (n=Alex@dialin-145-254-187-119.pools.arcor-ip.net) (Read error: 104 (Connection reset by peer))
  587. # [18:58] * Joins: Ducki (n=Alex@dialin-145-254-189-158.pools.arcor-ip.net)
  588. # [19:03] * Quits: gavin (n=gavin@firefox/developer/gavin) (Remote closed the connection)
  589. # [19:03] * Joins: gavin (n=gavin@people.mozilla.com)
  590. # [19:04] * Quits: aroben (n=adamrobe@17.255.98.199) (Read error: 110 (Connection timed out))
  591. # [19:05] <mitsuhiko> rubys: really?
  592. # [19:05] <mitsuhiko> i can't find it somehow
  593. # [19:06] * aroben_ is now known as aroben
  594. # [19:10] * Joins: aroben_ (n=adamrobe@17.255.98.199)
  595. # [19:11] * Quits: aroben_ (n=adamrobe@17.255.98.199) (Remote closed the connection)
  596. # [19:12] * Joins: aroben_ (n=adamrobe@17.255.98.199)
  597. # [19:12] <Philip`> mitsuhiko: Are you looking in the 0.9 release rather than the SVN version?
  598. # [19:13] <mitsuhiko> Philip`: no. svn version
  599. # [19:16] * Quits: Wolfman2000 (n=Wolfman2@wvh5348rn.rh.ncsu.edu) ("Leaving")
  600. # [19:18] * Quits: aroben (n=adamrobe@17.203.15.248) (Read error: 104 (Connection reset by peer))
  601. # [19:18] * Joins: aroben (n=adamrobe@17.203.15.248)
  602. # [19:19] <Philip`> mitsuhiko: http://html5lib.googlecode.com/svn/trunk/python/src/treebuilders/__init__.py - looks like it needs etree with implementation=lxml.etree
  603. # [19:19] <mitsuhiko> ah
  604. # [19:20] <Philip`> (I've not tried using it myself, though)
  605. # [19:24] * Quits: weinigLap (i=weinig@nat/apple/x-b4de4f474b691035) (Read error: 104 (Connection reset by peer))
  606. # [19:24] * Joins: weinigLap (i=weinig@nat/apple/x-b7eb7633542887e9)
  607. # [19:39] * Quits: aroben_ (n=adamrobe@17.255.98.199) (Read error: 110 (Connection timed out))
  608. # [19:51] * Quits: yod (n=ot@bas11-montreal02-1128535778.dsl.bell.ca) ("Leaving")
  609. # [20:04] * Joins: hasather (n=hasather@22.80-203-71.nextgentel.com)
  610. # [20:08] * om_sleep is now known as othermaciej
  611. # [20:11] <Jero> does the <dialog> element also apply to comments on a weblog?
  612. # [20:16] * Joins: dbaron (n=dbaron@corp-242.mountainview.mozilla.com)
  613. # [20:27] * Joins: aroben_ (n=adamrobe@17.255.98.199)
  614. # [20:29] * Joins: Philip`_ (n=philip@zaynar.demon.co.uk)
  615. # [20:40] * Quits: Philip` (n=philip@zaynar.demon.co.uk) (Read error: 110 (Connection timed out))
  616. # [20:41] * Quits: aroben (n=adamrobe@17.203.15.248) (Read error: 104 (Connection reset by peer))
  617. # [20:41] * Joins: aroben (n=adamrobe@17.203.15.248)
  618. # [20:41] * Joins: kingryan (n=kingryan@corp.technorati.com)
  619. # [20:42] <jgraham> mitsuhiko: Did you get it working?
  620. # [20:42] <mitsuhiko> jgraham: i haven't further tried because i found out that lxml is not exactly what i need
  621. # [20:43] <mitsuhiko> basically what i want is a simple tree i push to plugins which then manipulate it, i pickle it afterwards and render on request
  622. # [20:43] * Quits: MikeSmith (n=MikeSmit@p62059-adsau18honb3-acca.tokyo.ocn.ne.jp) (Read error: 110 (Connection timed out))
  623. # [20:44] <jgraham> Does lxml not fulfil that use case
  624. # [20:44] * jgraham wonders if picking wouldn't work
  625. # [20:44] <jgraham> pickling even
  626. # [20:44] <mitsuhiko> jgraham: it's out of the scope because it's not a python library
  627. # [20:44] <mitsuhiko> (unfortunately)
  628. # [20:45] <jgraham> Oh, you need to work with the python stdlib?
  629. # [20:45] <mitsuhiko> no, just not binary stuff
  630. # [20:45] <jgraham> Does that not rule out XPath?
  631. # [20:45] * Philip`_ is now known as Philip`
  632. # [20:45] <mitsuhiko> jgraham: indeed. that's why i found a different solution
  633. # [20:46] <jgraham> What are you using?
  634. # [20:46] * Quits: weinigLap (i=weinig@nat/apple/x-b7eb7633542887e9)
  635. # [20:47] * Quits: aroben (n=adamrobe@17.203.15.248)
  636. # [20:47] <mitsuhiko> i have a minimal Node class with a filter function that uses a very simple query "language" that is easily parsable
  637. # [20:47] <mitsuhiko> (in theory performance doesn't matter because i put the pickled stuff into the database but i want to keep it simple)
  638. # [20:48] <mitsuhiko> but the html5 library is really nice :D
  639. # [20:54] * Joins: Ducki_ (n=Alex@nrdh-d9b9837b.pool.mediaWays.net)
  640. # [20:56] * Quits: aroben_ (n=adamrobe@17.255.98.199) (Read error: 110 (Connection timed out))
  641. # [21:08] <annevk> Jero, I'd suggest e-mailing the list; that is either a good example for good usage or bad usage
  642. # [21:09] <annevk> Jero, personally I think it would be incorrect, <article> is for marking up comments iirc
  643. # [21:09] <annevk> Jero, personally I think it would be incorrect, <article> is for marking up comments iirc
  644. # [21:09] <Jero> annevk: yeah, I saw that too, but <dialog> also seemed like a good candidate. I'll email the list, thanks
  645. # [21:10] <annevk> krijnh, pointer?
  646. # [21:10] <annevk> hmm
  647. # [21:12] * Quits: Philip` (n=philip@zaynar.demon.co.uk) (Read error: 110 (Connection timed out))
  648. # [21:13] * Joins: briansuda (n=briansud@157-157-30-204.dsl.dynamic.simnet.is)
  649. # [21:15] * Joins: Philip` (n=philip@zaynar.demon.co.uk)
  650. # [21:19] * Quits: Ducki (n=Alex@dialin-145-254-189-158.pools.arcor-ip.net) (Read error: 110 (Connection timed out))
  651. # [21:21] * Joins: weinigLap (n=weinig@17.255.105.160)
  652. # [21:26] * Joins: weinigLap_ (i=weinig@nat/apple/x-54452f298e41532f)
  653. # [21:26] * Joins: aroben (n=adamrobe@17.203.15.248)
  654. # [21:29] <annevk> http://pkarl.com/notebook/if-you-dont-approve-of-html5-then-youre-a-communist/
  655. # [21:30] <Lfe> got to love how blogs has improved page titles :)
  656. # [21:30] <annevk> http://www.burningbird.net/technology/marathon-20/
  657. # [21:32] * Joins: briansuda_ (n=briansud@85-220-121-106.dsl.dynamic.simnet.is)
  658. # [21:41] * Quits: briansuda (n=briansud@157-157-30-204.dsl.dynamic.simnet.is) (Read error: 110 (Connection timed out))
  659. # [21:41] * Joins: psa (n=yomode@posom.com)
  660. # [21:41] * Quits: weinigLap (n=weinig@17.255.105.160) (Read error: 110 (Connection timed out))
  661. # [21:42] * Quits: gavin_ (n=gavin@firefox/developer/gavin) (Connection timed out)
  662. # [21:42] * weinigLap_ is now known as weinigLap
  663. # [21:48] <Jero> does anyone know anything about the http://php-html5lib.dashslot.net/trac project?
  664. # [21:56] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net) (Read error: 110 (Connection timed out))
  665. # [22:00] * Joins: aroben_ (n=adamrobe@17.255.98.199)
  666. # [22:00] * Quits: SavageX (n=maikmert@L9a93.l.pppool.de) ("Leaving")
  667. # [22:01] * Quits: aroben_ (n=adamrobe@17.255.98.199) (Remote closed the connection)
  668. # [22:02] * Parts: rubys (n=rubys@cpe-075-182-064-252.nc.res.rr.com)
  669. # [22:04] * Joins: Ducki (i=Alex@dialin-212-144-064-015.pools.arcor-ip.net)
  670. # [22:07] * Joins: aroben_ (n=adamrobe@17.255.98.199)
  671. # [22:15] * Quits: aroben (n=adamrobe@17.203.15.248) (Read error: 110 (Connection timed out))
  672. # [22:15] * aroben_ is now known as aroben
  673. # [22:18] * Quits: briansuda_ (n=briansud@85-220-121-106.dsl.dynamic.simnet.is)
  674. # [22:19] * Philip` wonders why he always ends up writing far more than he intends to
  675. # [22:20] <Hixie> just go back and remove sentences afterwards :-)
  676. # [22:20] <Hixie> i often write e-mails twice as long as the ones i eventually send out
  677. # [22:20] <Hixie> just have to apply a razor
  678. # [22:22] * Quits: Ducki_ (n=Alex@nrdh-d9b9837b.pool.mediaWays.net) (Read error: 113 (No route to host))
  679. # [22:30] * Joins: othermaciej (n=mjs@17.255.98.107)
  680. # [22:31] * Quits: othermaciej (n=mjs@17.255.98.107) (Client Quit)
  681. # [22:31] <Hixie> annevk: maybe try "Conformance requirements phrased as algorithms or specific steps may be implemented in any manner, so long as the end result is equivalent."
  682. # [22:33] <annevk> christ
  683. # [22:33] <annevk> got to love comments like that
  684. # [22:33] * Joins: othermaciej (n=mjs@17.255.98.107)
  685. # [22:34] <Hixie> yeah
  686. # [22:34] <Hixie> the text above is what html5 says
  687. # [22:34] <Hixie> fwiw
  688. # [22:34] <annevk> k
  689. # [22:34] <Dashiva> How about just combining them? "MUST follow either the algorithm below or an algorithm giving identical results"
  690. # [22:35] <gsnedders> I prefer the current text over that
  691. # [22:35] <othermaciej> I think instead of changing the conformance requirements for every algorithm, the text that says equivalent algorithms are ok could be made more explicit
  692. # [22:36] <annevk> I think that's what Hixie suggested above
  693. # [22:36] <Hixie> Dashiva: there's like a thousand occurences of the text "must follow these steps:" in html5, i'm not replacing every single one with weasle-wording
  694. # [22:37] <othermaciej> I did not see his text above
  695. # [22:37] <othermaciej> I guess I should check the logs
  696. # [22:37] <Hixie> 22:31 < Hixie>|annevk: maybe try "Conformance requirements phrased as algorithms or specific steps may be implemented in any manner, so long as the end result is equivalent."
  697. # [22:37] <Hixie> (it's what's in html5)
  698. # [22:38] <othermaciej> that sounds pretty good
  699. # [22:40] <Hixie> it wouldn't satisfy people who are looking for problems where there are none, sadly
  700. # [22:45] <othermaciej> if you wanted to be even more explicit you could say "Wherever this user agent says that a user agent must follow a particular algorithm or sequence of stops, user agents may use any algorithm that has the same results."
  701. # [22:45] <othermaciej> just so no one imagines a must / may conflict
  702. # [22:46] <Dashiva> That's a good one
  703. # [22:46] <othermaciej> s/this user agent/this specification/
  704. # [22:47] * Quits: Ducki (i=Alex@dialin-212-144-064-015.pools.arcor-ip.net) (Read error: 110 (Connection timed out))
  705. # [22:50] * Quits: jcgregorio (i=chatzill@nat/ibm/x-fefa83629c897eff) ("ChatZilla 0.9.78.1 [Firefox 2.0.0.4/2007060115]")
  706. # [22:58] * Quits: ROBOd (n=robod@86.34.246.154) ("http://www.robodesign.ro")
  707. # [23:00] <annevk> bjoern disagrees...
  708. # [23:00] <annevk> I think I'll call it a day
  709. # [23:00] <annevk> to boring to worry about now
  710. # [23:01] <Hixie> hear hear
  711. # [23:10] * Joins: kingryan_ (n=kingryan@corp.technorati.com)
  712. # [23:10] * Quits: kingryan_ (n=kingryan@corp.technorati.com) (Client Quit)
  713. # [23:12] * Joins: kingryan_ (n=kingryan@corp.technorati.com)
  714. # [23:12] * Joins: hendry (i=hendry@conference/debconf/x-eb9c458ed1743eda)
  715. # [23:12] <Hixie> hey, anyone have a link to that summary of why versioning is bad? i think it was either henri or lachy that wrote it
  716. # [23:12] <Hixie> can't find it anywhere
  717. # [23:15] <gavin> http://lists.w3.org/Archives/Public/public-html/2007Apr/0858.html , maybe?
  718. # [23:15] <gavin> I recall one from hsivonen that I can't find, either
  719. # [23:17] <Hixie> yeah that's all i could find too (arguments against IE's plan, rather than versioning in general)
  720. # [23:17] <gavin> this is going to bother me now
  721. # [23:18] <bewest> Hixie: some people interpret the versioning issue to imply that since html(5) will have no versioning in the doctype, that therefore every feature of html5 is perfect and won't need revising.
  722. # [23:19] <Hixie> yeah
  723. # [23:20] <bewest> at least, that is the complaint in #web
  724. # [23:20] <bewest> among others.
  725. # [23:22] * Quits: Jero (n=Jero@d207230.upc-d.chello.nl) ("ChatZilla 0.9.78.1 [Firefox 2.0.0.4/2007051502]")
  726. # [23:22] * Quits: kingryan (n=kingryan@corp.technorati.com) (Read error: 110 (Connection timed out))
  727. # [23:22] <hasather> Hixie: http://lists.w3.org/Archives/Public/public-html/2007JanMar/0433.html?
  728. # [23:23] <Hixie> hm yes
  729. # [23:23] <Hixie> i think that was it!
  730. # [23:23] <Hixie> thanks!
  731. # [23:24] <gavin> ah, good
  732. # [23:25] <hasather> Hixie: there's also http://lists.w3.org/Archives/Public/public-html/2007Apr/0279
  733. # [23:26] <Hixie> i think he sent one to www-tag at some point, too
  734. # [23:27] <hasather> found those via zcorpan's del.icio.us :)
  735. # [23:27] <Hixie> dbaron's is pretty good too, yeah
  736. # [23:30] * Quits: aroben (n=adamrobe@17.255.98.199)
  737. # [23:30] * Hixie sends his mail to www-archive
  738. # [23:33] <hendry> are there any specs for spreadsheet type support in html?
  739. # [23:33] <hendry> there's mathml, in know, but is that it?
  740. # [23:33] <Hixie> define "spreadsheet type support"?
  741. # [23:34] <Hixie> http://spreadsheet.google.com/ is all HTML
  742. # [23:34] <hendry> functions and stuff I guess
  743. # [23:34] <hendry> :)
  744. # [23:34] <bewest> and there's an API for the spreadsheets stuff
  745. # [23:34] <hendry> though that's a representation?
  746. # [23:35] * Joins: aroben (n=adamrobe@17.255.98.199)
  747. # [23:35] * Quits: aroben (n=adamrobe@17.255.98.199) (Read error: 104 (Connection reset by peer))
  748. # [23:36] * Joins: aroben (n=adamrobe@17.255.98.199)
  749. # [23:41] <othermaciej> annevk, Hixie: I think to be really and truly proper, it is a bit nicer to explicitly say "as if" at each site mentioning an algorithm, but a blanket clarification in the conformance section is also fine
  750. # [23:41] <othermaciej> bjoern's suggested alternative is just crazy
  751. # [23:45] * Quits: hendry (i=hendry@conference/debconf/x-eb9c458ed1743eda) ("leaving")
  752. # [23:48] <Hixie> the html5 spec is hard enough to read already without having pointless "as if"s all over the place
  753. # [23:48] <Hixie> everyone to whom it actually matters is completely aware that it's "as if" anyway
  754. # [23:49] * gsnedders just wants to say "as if it's hard to read!"
  755. # [23:55] <hsivonen> en-GB-x-hixie-x-valleygirl
  756. # [23:56] <gsnedders> as if.
  757. # Session Close: Wed Jun 20 00:00:00 2007

The end :)