/irc-logs / freenode / #whatwg / 2008-09-15 / end

Options:

  1. # Session Start: Mon Sep 15 00:00:00 2008
  2. # Session Ident: #whatwg
  3. # [00:01] * Joins: MacDome (n=eric@c-24-130-13-197.hsd1.ca.comcast.net)
  4. # [00:04] * Joins: tusho (n=tusho@91.105.85.60)
  5. # [00:04] <tusho> Why is it an error to explicitly close self-closing tags?
  6. # [00:05] <tusho> <link></link>, <input></input> etc
  7. # [00:05] <annevk> those are void elements and have a special syntax
  8. # [00:05] * Quits: roc (n=chatzill@202.0.36.64) (Remote closed the connection)
  9. # [00:05] <annevk> i.e., <link> or <link/>
  10. # [00:05] <tusho> annevk: yes, but I don't see why it should be an -error- to close them explicitly
  11. # [00:05] <tusho> just optional
  12. # [00:06] <annevk> because people would be confused and think they can put stuff between those two tags
  13. # [00:06] <annevk> and because <br></br> means <b><br> rather than <br>
  14. # [00:06] <annevk> means <br><br>, sorry
  15. # [00:06] <tusho> annevk: it's just that i programmatically generate html and it's a lot easier to treat all tags equally
  16. # [00:06] * Quits: MacDome (n=eric@c-24-130-13-197.hsd1.ca.comcast.net)
  17. # [00:07] <nessy> is that really the case? I don't seem to remember that being the general xml rule
  18. # [00:07] <annevk> nessy, it's the HTML rule :)
  19. # [00:08] <annevk> tusho, keeping a set around and doing a simple if x in set is not an option?
  20. # [00:08] <tusho> annevk: well, it is, but still :\
  21. # [00:08] * Joins: MacDome (n=eric@c-24-130-13-197.hsd1.ca.comcast.net)
  22. # [00:08] <nessy> http://www.w3.org/TR/REC-xml/#sec-starttags <- has the <br</br> example
  23. # [00:09] <nessy> I think in this case we should stick with the general xml rule - this is totally non-intuitive and confusing
  24. # [00:09] <annevk> nessy, tusho, http://software.hixie.ch/utilities/js/live-dom-viewer/?%3Cbr%3E%3C%2Fbr%3E
  25. # [00:09] <nessy> it's also not the way it works in HTML4
  26. # [00:10] <annevk> nessy, in HTML4 <link></link> is an error too
  27. # [00:10] <nessy> really?
  28. # [00:10] <annevk> yes
  29. # [00:10] <annevk> http://www.w3.org/TR/html4/struct/links.html#h-12.3 "Start tag: required, End tag: forbidden"
  30. # [00:11] <annevk> HTML4 does not even allow <link/>
  31. # [00:14] <nessy> glad browsers are not that anal :)
  32. # [00:14] * Joins: KevinMarks (n=KevinMar@94-116-110-181.dynamic.thecloud.net)
  33. # [00:14] <nessy> I guess then it's a tradition
  34. # [00:17] <annevk> Hixie, the methods are still on HTMLFormElement?
  35. # [00:40] * Joins: roc (n=chatzill@202.0.36.64)
  36. # [00:46] * Quits: MacDome (n=eric@c-24-130-13-197.hsd1.ca.comcast.net)
  37. # [00:55] * Quits: hasather_ (n=hasather@90-231-107-133-no62.tbcn.telia.com) (Read error: 110 (Connection timed out))
  38. # [01:20] * Quits: weinig (n=weinig@c-71-198-176-23.hsd1.ca.comcast.net)
  39. # [01:28] * Joins: weinig (n=weinig@c-71-198-176-23.hsd1.ca.comcast.net)
  40. # [01:53] * Quits: tusho (n=tusho@91.105.85.60)
  41. # [01:55] * Quits: roc_ (n=chatzill@121-72-162-122.dsl.telstraclear.net) (Read error: 110 (Connection timed out))
  42. # [02:17] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  43. # [02:17] * Quits: weinig (n=weinig@c-71-198-176-23.hsd1.ca.comcast.net)
  44. # [02:43] * Joins: weinig (n=weinig@nat/apple/x-cc8ff411bde69719)
  45. # [02:58] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  46. # [03:05] * Quits: kangax (n=kangax@ool-182f8118.dyn.optonline.net)
  47. # [03:17] * Quits: tndH (n=Rob@87.102.18.38) ("ChatZilla 0.9.83-rdmsoft [XULRunner 1.9.0.1/2008072406]")
  48. # [03:32] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  49. # [03:37] * Joins: roc_ (n=chatzill@121-72-162-122.dsl.telstraclear.net)
  50. # [03:55] * Joins: kangax (n=kangax@ool-182f8118.dyn.optonline.net)
  51. # [04:25] * Quits: roc (n=chatzill@202.0.36.64) (Remote closed the connection)
  52. # [04:26] * Joins: roc (n=chatzill@202.0.36.64)
  53. # [04:31] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  54. # [04:38] * Quits: weinig (n=weinig@nat/apple/x-cc8ff411bde69719) (Read error: 54 (Connection reset by peer))
  55. # [04:39] * Joins: weinig (n=weinig@nat/apple/x-20dd87cdeda6c0db)
  56. # [04:43] * Quits: roc_ (n=chatzill@121-72-162-122.dsl.telstraclear.net) (Read error: 110 (Connection timed out))
  57. # [04:49] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  58. # [04:58] * Quits: weinig (n=weinig@nat/apple/x-20dd87cdeda6c0db)
  59. # [05:52] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  60. # [06:02] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  61. # [06:08] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  62. # [06:09] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  63. # [06:19] * Joins: tantek (n=tantek@c-98-242-125-80.hsd1.ga.comcast.net)
  64. # [06:36] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  65. # [06:42] * Joins: weinig (n=weinig@nat/apple/x-fb2f34a92e5dc66d)
  66. # [06:48] <Hixie> annevk: the methods on HTMLFormElement are different, that's one reason i got rid of the others
  67. # [06:50] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  68. # [07:18] * Quits: weinig (n=weinig@nat/apple/x-fb2f34a92e5dc66d)
  69. # [07:24] * Joins: weinig (n=weinig@nat/apple/x-2f3e4a9cca220c31)
  70. # [07:45] * Joins: maikmerten (n=merten@ls5laptop14.cs.uni-dortmund.de)
  71. # [07:45] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  72. # [08:21] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  73. # [08:46] * Quits: weinig (n=weinig@nat/apple/x-2f3e4a9cca220c31)
  74. # [08:48] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  75. # [08:50] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  76. # [08:58] * Joins: tndH (n=Rob@87.102.18.38)
  77. # [09:05] * Joins: epeus (n=KevinMar@216.239.33.8)
  78. # [09:06] * Hixie does some cleanup in the comment section at the bottom of the spec
  79. # [09:06] <Hixie> it was getting out of hands
  80. # [09:06] <Hixie> there's 2000 lines of nots there
  81. # [09:06] <Hixie> notes, even
  82. # [09:09] * Joins: Maurice (n=ano@a80-100-71-209.adsl.xs4all.nl)
  83. # [09:12] * Quits: KevinMarks (n=KevinMar@94-116-110-181.dynamic.thecloud.net) (Read error: 110 (Connection timed out))
  84. # [09:20] * Joins: weinig (n=weinig@c-71-198-176-23.hsd1.ca.comcast.net)
  85. # [09:33] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  86. # [09:33] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  87. # [09:44] * Quits: sverrej (n=sverrej@89.10.27.245) (Read error: 110 (Connection timed out))
  88. # [09:44] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  89. # [09:48] * Joins: roc_ (n=chatzill@121-72-177-254.dsl.telstraclear.net)
  90. # [09:50] <hendry> what is the right content type for javascript? i've seen application/x-javascript (apache) application/javascript (somewhere) text/javascript (most common)
  91. # [09:52] <hsivonen> hendry: application/x-javascript on the HTTP layer and text/javascript on the HTML layer
  92. # [09:52] <Hixie> use text/javascript
  93. # [09:53] <Hixie> hsivonen: bjoern registered the types, so there are actual non x- types that one can use now
  94. # [09:53] <annevk> Hixie, oops, guess I should actually check WF2 first before making assumptions
  95. # [09:53] <hsivonen> Hixie: do they work without problems?
  96. # [09:53] <Hixie> text/javascript is the only type i know that reliably works without problems
  97. # [09:54] <annevk> except in SVG
  98. # [09:54] <annevk> (server side types are ignored for <script>, fwiw)
  99. # [09:55] <hsivonen> annevk: does SVG work without an explicit type
  100. # [09:56] <hsivonen> on the HTML side, the type is useless
  101. # [09:56] <annevk> I think it does on the SVG side, but I'm not completely sure
  102. # [09:57] <annevk> lol: http://twitter.com/diveintomark/statuses/921518773
  103. # [09:59] <annevk> just in: http://www.webfoundation.org/
  104. # [09:59] <annevk> (from the W3C)
  105. # [10:01] <hsivonen> does this mean the funding structure now yields different incentives?
  106. # [10:01] <hsivonen> what does this mean to WS-*?
  107. # [10:02] <hsivonen> the mobile webs?
  108. # [10:02] <hsivonen> the Web?
  109. # [10:02] <Hixie> christ, the mission is even vaguer than the w3c's
  110. # [10:07] * weinig is now known as weinig|zZz
  111. # [10:07] <Hixie> i'm amused that the wf's faq's answers are so vague and talking-point-y, given that they could pick the questions
  112. # [10:08] <hsivonen> so is the W3C transforming into this foundation or is this something that will be separate from the W3C?
  113. # [10:09] * hsivonen tries to continue to read the FAQ
  114. # [10:09] <annevk> I believe it is a separate entity
  115. # [10:10] <annevk> but the FAQ indeed doesn't say much
  116. # [10:10] <hsivonen> OK. I got the wrong idea from the personnel overlap then
  117. # [10:10] <othermaciej> it's unclear what the purpose is
  118. # [10:10] <othermaciej> besides to collect donations
  119. # [10:11] <othermaciej> http://www.webfoundation.org/about/concept2008
  120. # [10:11] <othermaciej> there used to be a WebFoundation.framework in the early days of WebKit development
  121. # [10:12] * Joins: aaronlev (n=chatzill@g227092026.adsl.alicedsl.de)
  122. # [10:12] * hsivonen finally finds "It was preferable not to disturb the W3C ecosystem for building consensus around Web standards. "
  123. # [10:13] <hsivonen> it might have been a good idea to put the question about the relationship with the W3C at the top...
  124. # [10:13] <hsivonen> I'm now less excited than I was 10 minutes ago
  125. # [10:15] <othermaciej> Tim is becoming quite the nonprofit entrepreneur
  126. # [10:19] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  127. # [10:24] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) (Read error: 110 (Connection timed out))
  128. # [10:24] * Quits: epeus (n=KevinMar@216.239.33.8) (Connection reset by peer)
  129. # [10:39] <hsivonen> Hixie: are you not annotating changes to WF2 compared to what Opera implemented?
  130. # [10:39] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  131. # [10:39] <Hixie> hsivonen: i haven't tested what opera does very carefully
  132. # [10:40] <Hixie> but mostly the only changes are cutting stuff out
  133. # [10:40] <hsivonen> ok
  134. # [10:40] <annevk> it would be nice if you kept a small file somewhere that lists the changes
  135. # [10:40] <annevk> I can figure them out for myself, but it would make things easier
  136. # [10:43] <Hixie> does anyone have a list of the changes so far?
  137. # [10:43] <annevk> no XML form submission, repetition templates, form="" takes a single ID
  138. # [10:43] <annevk> you might have dropped external files for <datalist> and <select>
  139. # [10:44] <Hixie> (i'm basically just treating wf2 as part of html4 and using the same approach i do normally, btw, which is why i haven't really considered "changes" from wf2)
  140. # [10:44] <hsivonen> are all html5lib users on this channel using lxml.etree as the tree impl?
  141. # [10:44] <annevk> (for a few features it's not really clear)
  142. # [10:45] * Joins: ROBOd (n=robod@89.122.216.38)
  143. # [10:45] <annevk> Hixie, I guess that's fair enough, WF2 was pretty big
  144. # [10:45] <annevk> (in terms of features)
  145. # [10:46] <jgraham> hsivonen: I do, usually
  146. # [10:47] <Hixie> annevk: http://www.whatwg.org/specs/web-apps/current-work/notes has a brief list
  147. # [10:48] <Hixie> annevk: i'll try to keep it updated, but remind me occasionally
  148. # [10:48] <annevk> thx
  149. # [10:48] <hsivonen> I'm wondering if I should distinguish methods by name and not only by signature
  150. # [10:48] <hsivonen> that would be ugly in Java
  151. # [10:48] <hsivonen> but it seems it would facilitate subclassing in Jython
  152. # [10:50] <Philip`> hsivonen: I am
  153. # [10:51] * Joins: tantek_ (n=tantek@c-98-242-125-80.hsd1.ga.comcast.net)
  154. # [10:51] * Quits: tantek_ (n=tantek@c-98-242-125-80.hsd1.ga.comcast.net) (Read error: 104 (Connection reset by peer))
  155. # [10:51] * Quits: tantek (n=tantek@c-98-242-125-80.hsd1.ga.comcast.net) (Connection reset by peer)
  156. # [10:52] * Joins: tantek (n=tantek@c-98-242-125-80.hsd1.ga.comcast.net)
  157. # [10:55] <hsivonen> Philip`: what did you do about tree builders under Jython? would you have wanted an elementtree tree builder/
  158. # [10:55] <hsivonen> ?
  159. # [10:57] <hsivonen> Re: 2022: Wine took 15 years to go to 1.0
  160. # [10:58] <Philip`> hsivonen: My Jython code has no chance of ever running under CPython, so I don't care about having compatible interfaces; but I haven't written very much at all, and have only used SAX so far
  161. # [10:59] <Philip`> (And I have no desire to run my CPython code under Jython)
  162. # [11:01] <hsivonen> annevk: re: your blog entry with comments disabled: I've been thinking about blogging about the new concept of a REC not being particularly useful
  163. # [11:02] <hsivonen> annevk: what's the point of getting the particular feature set of CSS 2.1 to REC as one document when by the time it is a REC, both authors and implementations will be doing CSS 2.1 plus some CSS3 bits
  164. # [11:02] <annevk> hsivonen, yeah, agreed, let me know when you post it and I'll add a link
  165. # [11:02] <hsivonen> it seems to me that maturity should be tracked per-feature or something
  166. # [11:03] <annevk> that's what the HTML5 annotation system does
  167. # [11:03] <hsivonen> (having a lot of tiny specs doesn't really work with the intertwingliness)
  168. # [11:03] <hsivonen> annevk: right
  169. # [11:14] * Quits: Lachy (n=Lachlan@85.196.122.246) ("This computer has gone to sleep")
  170. # [11:15] * Joins: hdh (n=hdh@118.71.121.223)
  171. # [11:18] <Hixie> haha:
  172. # [11:18] <Hixie> “I’m really looking forward to the work we’re starting to do to ramp up building a test suite in the HTML Working Group,” says Microsoft Internet Explorer platform architect and WHAT WG co-chair Chris Wilson in an e-mail.
  173. # [11:19] <Hixie> -- http://www.webmonkey.com/blog/How_HTML_5_Is_Already_Changing_the_Web
  174. # [11:19] <Hixie> (laughing at "WHAT WG co-chair")
  175. # [11:20] <roc_> be nice
  176. # [11:20] <Hixie> to whom?
  177. # [11:21] <Hixie> i wasn't laughing at chris, i was laughing at the confusion we've managed to cause around the html5 process
  178. # [11:21] <roc_> oh righg
  179. # [11:21] <roc_> that passed me by
  180. # [11:31] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  181. # [11:31] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  182. # [11:32] * Joins: sverrej (n=sverrej@pat-tdc.opera.com)
  183. # [11:35] * Quits: sverrej (n=sverrej@pat-tdc.opera.com) (Remote closed the connection)
  184. # [11:38] * Joins: Lachy (n=Lachlan@pat-tdc.opera.com)
  185. # [11:38] * Joins: sverrej (n=sverrej@pat-tdc.opera.com)
  186. # [11:39] <takkaria> that article is pretty impressively misleading :)
  187. # [11:40] * Quits: Lachy (n=Lachlan@pat-tdc.opera.com) (Client Quit)
  188. # [11:41] * Joins: Lachy (n=Lachlan@pat-tdc.opera.com)
  189. # [11:41] <Philip`> Their comment-truncating system is really very irritating
  190. # [11:47] * Quits: starjive (i=beos@213-66-217-32-no30.tbcn.telia.com)
  191. # [11:49] <takkaria> http://news.bbc.co.uk/1/hi/technology/7613201.stm -- hmm
  192. # [11:52] <hsivonen> so what kind of certificate will foxnews.com get?
  193. # [11:56] <roc_> yeah, that way is perilous
  194. # [12:07] * Quits: mpt (n=mpt@canonical/launchpad/mpt) (Remote closed the connection)
  195. # [12:07] <Philip`> It doesn't sound like you'd get a certificate in that way - '"I'm not a fan of giving a website a simple number like an IQ rating because like people they can vary in all kinds of different ways," he said. "So I'd be interested in different organisations labelling websites in different ways".'
  196. # [12:08] <roc_> isn't that PICS all over again?
  197. # [12:08] <Philip`> Maybe you would choose a friend's RDF feed of site-trustworthiness scores and it would transitively compute the trustworthiness of the whole web on your own computer, so you can choose whose prejudices to be exposed to
  198. # [12:09] <Philip`> roc_: Hmm, I assumed it meant organisations labelling other people's websites, not their own
  199. # [12:09] * Quits: kangax (n=kangax@ool-182f8118.dyn.optonline.net)
  200. # [12:09] <roc_> I thought PICS let organisations label other people's websites
  201. # [12:09] <Philip`> Oh, okay
  202. # [12:10] <othermaciej> I wish Tim could be proud of the beautiful chaos of the human-readable Web he created
  203. # [12:10] <othermaciej> and stop chasing pipe dreams of a non-useless machine-readable Web
  204. # [12:12] <Philip`> Hmph, HTML5 doesn't acknowledge the cabal any more :-(
  205. # [12:12] <Hixie> wow, you guys look at the diffs closely
  206. # [12:13] <Hixie> i was trying to smuggle that change in :-P
  207. # [12:13] <annevk> Hixie, "XXX * find object at (x,y)" is in http://dev.w3.org/csswg/cssom-view/
  208. # [12:13] <othermaciej> will any cabal members publicly reveal themselves enough to object?
  209. # [12:13] <annevk> Hixie, Pillar and Hedral are your cats?
  210. # [12:13] <Hixie> (the cabal it used to acknowledge wasn't the one that people thought it was, and has been disbanded for years, so i figured i should drop it)
  211. # [12:14] <Hixie> annevk: what's the status of cssom-view?
  212. # [12:14] * Quits: tantek (n=tantek@c-98-242-125-80.hsd1.ga.comcast.net) (Read error: 104 (Connection reset by peer))
  213. # [12:14] <annevk> Hixie, closer to REC than HTML5 :p
  214. # [12:14] <Hixie> (yes, Miss Cat Adorable Pillar and Sir Cat Hedral)
  215. # [12:14] * Joins: tantek (n=tantek@c-98-242-125-80.hsd1.ga.comcast.net)
  216. # [12:14] <Hixie> annevk: no new features? :-)
  217. # [12:14] <Hixie> i didn't realise this stuff was that interoperable
  218. # [12:15] <annevk> it has a few new features that are not shipping yet
  219. # [12:16] <othermaciej> you knighted your cat?
  220. # [12:16] <othermaciej> did you give him the accolate with a catnip chew toy?
  221. # [12:16] <othermaciej> *accolade
  222. # [12:16] <othermaciej> (dammit)
  223. # [12:20] <Hixie> othermaciej: q.v. ts elliot
  224. # [12:20] <Hixie> annevk: so what's your trick for being nearer to REC? :-)
  225. # [12:21] <annevk> less features ;)
  226. # [12:21] <annevk> we'll see I guess :)
  227. # [12:24] <Hixie> :-P
  228. # [12:26] * Philip` discovers that HTML5 allows <ul></ul>, whereas HTML4 didn't (and requires at least one <li>)
  229. # [12:26] <Philip`> which solves a problem I once had when doing templated HTML generation with possibly-zero-length lists, which is nice
  230. # [12:27] <virtuelv> Philip`: How do UA's apply default style to the empty ul?
  231. # [12:27] <virtuelv> s/'s/s/
  232. # [12:28] * Quits: tantek (n=tantek@c-98-242-125-80.hsd1.ga.comcast.net)
  233. # [12:30] <Philip`> virtuelv: No idea
  234. # [12:30] * Quits: annevk (n=annevk@77.163.243.203) (Read error: 104 (Connection reset by peer))
  235. # [12:31] * Joins: annevk (n=annevk@77.163.243.203)
  236. # [12:31] <Hixie> virtuelv: probably just 1em top-and-bottom collapsed margin
  237. # [12:32] <Hixie> i love how much press we've been getting just because of the 2022 date
  238. # [12:32] <Hixie> it's awesome
  239. # [12:33] <Hixie> i think this is only the second most amount of press we've gotten, after the checkin where i changed the requirement of ogg support for a note that said we needed a common codec
  240. # [12:33] * Joins: tusho (n=tusho@91.105.85.60)
  241. # [12:33] <othermaciej> HTML5 won't support Ogg until 2022!
  242. # [12:33] <Hixie> by 2022 it'll probably require h.264!
  243. # [12:34] <hsivonen> Hixie: not so awesome if it makes people want HTML4+foo validation instead of HTML5 validation
  244. # [12:34] <Hixie> why would it make people want foo?
  245. # [12:34] <othermaciej> I like the counter-article of "HTML5 is improving the Web already"
  246. # [12:35] <Hixie> the comments on most of these articles is pretty balanced
  247. # [12:35] <Hixie> and the body of most of them, despite the sensationalist titles, is pretty fair too
  248. # [12:35] <hsivonen> Hixie: assume foo has the value ARIA
  249. # [12:36] <hsivonen> Hixie: then assume you are WordPress with Transitional templates and lots of talk about standards compliance
  250. # [12:36] <annevk> Hixie, fwiw, the XHTML2 and Froms WGs consider XHTML2 + XForms to be suitable for Web applications
  251. # [12:36] <hsivonen> Hixie: then you want to add some ARIA stuff
  252. # [12:36] <hsivonen> Hixie: what do you do about validation
  253. # [12:36] <Hixie> annevk: i'm sure they do
  254. # [12:36] <annevk> Hixie, I'm not sure if the HTML 5 draft should make judgements about that
  255. # [12:36] <hsivonen> Hixie: should authors have to choose between either having ARIA and <video> or having border=0
  256. # [12:36] <othermaciej> "Valid XHTML 1.0!"
  257. # [12:36] <hsivonen> ?
  258. # [12:37] <othermaciej> is what WordPress seems to want
  259. # [12:37] <Hixie> annevk: how me a real time strategy game written in xhtml2+xforms whose author says that xhtml2+xforms was a language that was satisfactorily designed for that purpose and i'll change the text
  260. # [12:37] <hsivonen> othermaciej: well, XHTML 1.0 and HTML 4.01 are pretty much the same thing for my purposes
  261. # [12:38] <Hixie> annevk: (or, if the xhtml2 and xforms wgs are willing to provide alternative text for those sections that is still accurate, i'll change it to that -- we're still waiting for them to come back with text for the xhtml 1.1 section)
  262. # [12:38] <othermaciej> I am just saying, their idea of standards compliance is already broken
  263. # [12:38] <Hixie> hsivonen: is this hypothetical or has it happened?
  264. # [12:38] <Hixie> hsivonen: i haven't seen people asking for aria validation on any of these articles
  265. # [12:38] <Hixie> hsivonen: and wordpress doesn't seem complicated enough to warrant needing aria
  266. # [12:39] <hsivonen> Hixie: I have had a question about validating ARIA in the context of WP specifically
  267. # [12:39] <hsivonen> Hixie: I have had an inquiry about HTML4+ARIA validation
  268. # [12:40] <hsivonen> Hixie: I get bug reports about HTML4 support
  269. # [12:40] <hsivonen> Hixie: and I've gotten a non-ARIA inquiry about maintenance/development of the HTML 4 side
  270. # [12:41] <hsivonen> Hixie: I wish the practical answer I could give was "Use HTML5 validation"
  271. # [12:41] <Hixie> why isn't that a practical answer? i mean, other than the fact that html5 is still in flux
  272. # [12:42] <hsivonen> Hixie: border=0, cellspacing=0, headers=foo, language=JavaScript
  273. # [12:42] <Hixie> why isn't my proposal for those satifactory?
  274. # [12:42] <Hixie> satisfactory even
  275. # [12:43] <Hixie> (also, i thought headers=foo was resolved, what about it is a problem?)
  276. # [12:43] <othermaciej> hsivonen: that seems more about specific migration tax issues (possibly fixable) than about HTML5 not being done for a while
  277. # [12:43] <hsivonen> Hixie: do you mean saying that the document is non-conforming but collapsing unimportant errors?
  278. # [12:43] <Hixie> yes
  279. # [12:43] <hsivonen> If stuff is unimportant, why say anything?
  280. # [12:44] <hsivonen> why develop more UI for stuff that is less important?
  281. # [12:44] * Joins: mpt (n=mpt@canonical/launchpad/mpt)
  282. # [12:44] <annevk> because people editing the document later might think it is significant
  283. # [12:44] <Hixie> because it still wastes bytes, and because if you're not transitioning from a legacy, it's valuable to not have it as it eases maintenance
  284. # [12:44] <annevk> and might try tweaking it, etc.
  285. # [12:44] <Hixie> i.e. it _is_ important
  286. # [12:44] <Hixie> just not interesting in certain cases (namely, editing legacy documents)
  287. # [12:45] <othermaciej> might this be something that is better classed as a warning rather than a conformance failure?
  288. # [12:45] <othermaciej> what is the philosophy behind what kind of arguable errors make a document non-conforming?
  289. # [12:45] <Hixie> othermaciej: not sure what that would mean. html5 either allows things or doesn't.
  290. # [12:45] <Philip`> I don't know about RTSs, but HTML5 is not satisfactorily designed for writing FPSs :-(
  291. # [12:45] <hsivonen> othermaciej: perhaps. but in principle, I can't do that without forking the conformance definition
  292. # [12:46] <othermaciej> I mean you get a diagnostic without a conformance failure
  293. # [12:46] <Philip`> (Well, I know about RTSs, but not about ones written in HTML)
  294. # [12:46] <Hixie> othermaciej: i don't think it is a good idea to make effect-free attributes conforming.
  295. # [12:46] <othermaciej> in other words, if the primary reason to disallow "border=0" is wasted bytes in non-legacy documents but it makes validating legacy documents needlessly painful, then disallowing it seems on net unhelpful
  296. # [12:47] <Hixie> Philip`: yup, there are lots of things that html5 can't do yet :-)
  297. # [12:47] <othermaciej> I would point out that /> is effect-free in HTML
  298. # [12:47] <hsivonen> Hixie: you already make effect-free stuff conforming
  299. # [12:47] <othermaciej> as is the xhtml namespace talisman
  300. # [12:47] * Hixie doesn't like those either
  301. # [12:47] <hsivonen> type=text/css
  302. # [12:47] <Hixie> we need type=""
  303. # [12:48] <othermaciej> I would say effect-free things should be a conformance failure if they are more likely to be an error on the part of the author than to be legacy migration stuff or otherwise present for reasonable reasons
  304. # [12:48] <Hixie> making type="text/css" invalid would make maintenance more complicated
  305. # [12:48] <othermaciej> (granting arguendo that XML/HTML chameleon document is a reasonable reason)
  306. # [12:48] <Hixie> othermaciej: if i write a new document, i shouldn't be using border=0 and shouldn't be allowed to do so
  307. # [12:49] <Hixie> othermaciej: and thus it should be an error
  308. # [12:49] <hsivonen> Hixie: how realistic is it that there will ever be a style language other than CSS?
  309. # [12:49] <othermaciej> but if I have an existing HTML4 document that uses it, should I have to rewrite it if I want to move to HTML5?
  310. # [12:49] <Hixie> othermaciej: having all these attributes around is a net loss, because there are far more new documents than old
  311. # [12:49] <othermaciej> isn't that basically the same as the XHTML migration story, though not as severe?
  312. # [12:49] <othermaciej> a warning that doesn't break conformance would serve the purpose of discouragement just as well
  313. # [12:49] <hsivonen> Hixie: during the transition period, there are definitely more old documents
  314. # [12:49] <Hixie> othermaciej: if you have an HTML4 Transitional document, you should have Transitioned already
  315. # [12:50] <Hixie> othermaciej: after all, HTML4 Transitional has been known as Transitional for over 10 years
  316. # [12:50] <hsivonen> Hixie: it's not about 10 years
  317. # [12:50] <Hixie> hsivonen: we'll never get out of the transition period if we don't stop allowing it
  318. # [12:50] <othermaciej> perhaps it should have been called HTML4 Non-Fascist
  319. # [12:50] <hsivonen> Hixie: IE is still here
  320. # [12:51] <othermaciej> making things a conformance error to encourage authors to save a few bytes seems like attacking a flea with a nuclear warhead
  321. # [12:51] <Hixie> i don't understand why you think it should be an error if the user types <p asdls=""> but not if the u
  322. # [12:51] <othermaciej> I mean, yes, it is better to save a few bytes by avoiding things that have no effect
  323. # [12:51] <Hixie> er
  324. # [12:52] <hsivonen> I should point out that I also have a serious feature request for alerting people if they are saving bytes by omitting tags
  325. # [12:52] <othermaciej> but it's not the same as a syntax error
  326. # [12:52] <Hixie> i don't understand why you think it should be an error if the author types <p asdls=""> but not if the author types <img border=0>
  327. # [12:52] <hsivonen> Hixie: because asdls hasn't existed historically but border has
  328. # [12:52] <annevk> because asdis might mean something in the future, border=0 will always do the same due to legacy reasons
  329. # [12:52] <othermaciej> asdls="" is unlikely to exist in many existing documents, and certainly in none that care about validation
  330. # [12:52] <Hixie> border=0 has been deprecated for over a decade
  331. # [12:52] <hsivonen> Hixie: and border is still needed for IE and Gecko
  332. # [12:53] <Hixie> and isn't needed anywhere
  333. # [12:53] <othermaciej> and asdls="" is more likely to be a typo or other mistake than intentional
  334. # [12:53] <hsivonen> Hixie: the decade doesn't matter as long as IE and Gecko do what they do
  335. # [12:53] <othermaciej> while border=0 is far more likely to be legacy than error
  336. # [12:53] <annevk> img { border:none } solves that though
  337. # [12:53] <Hixie> img { border: none; } has been supported in IE since at least IE4
  338. # [12:53] <hsivonen> Hixie: you can start counting once both IE and Gecko have purged the default border
  339. # [12:53] <Hixie> and has been supported in Gecko since around M6 if not before
  340. # [12:53] <hsivonen> Hixie: not copy/paste friendly
  341. # [12:54] <Hixie> oh please
  342. # [12:54] <Philip`> <img style="border:none">
  343. # [12:54] <hsivonen> Hixie: copy/paste is a real use case
  344. # [12:54] <hsivonen> Hixie: c.f. random badges
  345. # [12:54] <hsivonen> Philip`: that's along the lines of what CC does
  346. # [12:54] <hsivonen> Philip`: not really an improvement
  347. # [12:54] <Hixie> as Philip` points out, if copy/paste is THAT important to these authors but they can't add one line to their CSS, they can use style=""
  348. # [12:55] <Hixie> but even that is dumb
  349. # [12:55] <hsivonen> Hixie: is that an improvement?
  350. # [12:55] <hsivonen> Hixie: of the order of magnitude that I should bother countless of people about it?
  351. # [12:55] <Hixie> what they SHOULD be doing is making the badges have whatever semantics they want and then style the markup using CSS to get whatever look they want
  352. # [12:56] <Philip`> <style> isn't reader-friendly either - you can see an <img> when reading the page source, but you have no idea what's causing it to have no border, and it's pretty hard to work backwards to find the relevant selector
  353. # [12:56] <othermaciej> is replacing border=0 with style="border:none" a useful way to spend one's time when upgrading to HTML5?
  354. # [12:56] <Hixie> html4 deprecated these misfeatures literally a decade ago, we're not doing anyone a favour by coddling them another 20 years
  355. # [12:57] * Joins: hasather_ (n=hasather@90-231-107-133-no62.tbcn.telia.com)
  356. # [12:57] * Philip` wonders when someone will tie 'view source' into a Firebug-like tool
  357. # [12:57] <Philip`> (assuming they haven't already)
  358. # [12:57] <Hixie> othermaciej: no, which is why i think that all these error messages should be collapsed into one message of the ilk of "well you aren't compliant, but the only problems you have left are with old deprecated markup. More details..."
  359. # [12:57] <othermaciej> your desire to make these conformance errors seems to be based on a moralistic impulse against them rather than practical benefit for authors or users
  360. # [12:58] <othermaciej> Hixie: you know as well as I that "you aren't compliant" is not a state that anyone who cares about validation in the first place will want to stop at
  361. # [12:58] <othermaciej> if that's the output, they will waste a bunch of time or stop caring about the validator
  362. # [12:58] <othermaciej> (or both)
  363. # [12:58] <Hixie> the practical benefits are improved maintainability, improved authoring skill and understanding, and cleaner markup going forward
  364. # [12:58] <hsivonen> othermaciej: right, which is why it's pointless to develop UI for that
  365. # [12:58] <othermaciej> Hixie: isn't that the same arguments used for removing <b> and <i>?
  366. # [12:58] <othermaciej> "cleaner markup going forward"
  367. # [12:59] <othermaciej> "we have to fix all this broken stuff on the Web"
  368. # [12:59] <annevk> othermaciej, <b> and <i> are needed because they don't have replacements
  369. # [12:59] <hsivonen> Hixie: is it the validator's job to tell people how they can make their stuff more maintainable before they know they want it?
  370. # [12:59] <Hixie> i have removed <b> and <i>, in the form they had in html4
  371. # [12:59] <hsivonen> annevk: <span style='font-style: italic;'>
  372. # [12:59] <othermaciej> annevk: <span style="font-weight: bold">
  373. # [12:59] <Philip`> annevk: <strong>, <em>
  374. # [13:00] <hsivonen> annevk: if <img style='border: 0'> is a replacement
  375. # [13:00] <annevk> Philip`, ouch
  376. # [13:00] <othermaciej> but of course, that cure is worse than the alleged disease
  377. # [13:00] <annevk> <i> can be used for ship names and things typically rendered italic
  378. # [13:00] <Hixie> hsivonen: sure
  379. # [13:00] <Hixie> hsivonen: that's pretty much all a validator does
  380. # [13:00] <Hixie> hsivonen: that, and point out errors the author did know about but missed when editing the document
  381. # [13:01] <hsivonen> Hixie: I thought the job of a validator was closer to a spell checker than to a prescriptive grammarian
  382. # [13:01] <Hixie> hsivonen: word processors have both
  383. # [13:02] <othermaciej> "(machine-checkably) nonconforming" should be a question of syntax, not style
  384. # [13:02] * Philip` would like it if the validator acted like a spell-checker and gave you a list of suggested replacements and you could click on them to apply that replacement
  385. # [13:02] <annevk> I think I agree that finally removing a bunch of these attributes is a good thing
  386. # [13:02] <othermaciej> style is a matter of taste and therefore many tools could have different approaches
  387. # [13:02] <annevk> hsivonen, did people complain about them?
  388. # [13:02] <annevk> hsivonen, or are you just worried by survey figures?
  389. # [13:03] <annevk> s/just//
  390. # [13:03] <hsivonen> annevk: people are asking me to put more effort into the HTML4 code so that authors wouldn't need to make the jump to validating as HTML5
  391. # [13:03] <Hixie> i'm all for helping with this transition period, but i won't help with the transition period at the cost of not transitioning at all
  392. # [13:04] <Hixie> this means we can't do what html4 did (we know it doesn't work)
  393. # [13:04] <annevk> hsivonen, do you have more detailed information than that?
  394. # [13:04] <hsivonen> Hixie: I'm OK with killing <font face>, axis='' and <basefont>
  395. # [13:04] <hsivonen> annevk: no
  396. # [13:05] <Hixie> hsivonen: what happens if you only support HTML4 Strict?
  397. # [13:05] <hsivonen> annevk: this is like the usual WHATWG requirement problem: people want stuff without specifying exactly why
  398. # [13:05] <Hixie> what would happen, even
  399. # [13:05] <hsivonen> Hixie: I don't know.
  400. # [13:06] <Hixie> might be worth trying to implement HTML4 Transitional as just saying "Your document is not valid HTML4 Strict, because it uses features only available in the deprecated Transitional syntax." or some such
  401. # [13:06] <Hixie> instead of "Valid HTML4 Transitional"
  402. # [13:07] <Hixie> anyway, i'm open to ideas other than making these things fully conforming
  403. # [13:07] <hsivonen> Hixie: the purpose of the HTML 4 features of Validator.nu is to act as a gateway drug for the service--not to tell people to go back to DTD-based validator
  404. # [13:08] <hsivonen> Hixie: one possibility is to make them conditionally non-conforming with the condition being non-machine-checkable :-)
  405. # [13:08] <hsivonen> Hixie: as with layout tables :-)
  406. # [13:09] <hsivonen> And no, I don't have a good suggestion.
  407. # [13:09] <hsivonen> but I don't like the way things are now drafted
  408. # [13:10] <Hixie> there are lots of things i don't like in html5
  409. # [13:10] <annevk> hsivonen, but maybe we can figure it out from the documents they want to use HTML4 validation for?
  410. # [13:10] <Hixie> the /> talisman for instance
  411. # [13:10] <hsivonen> annevk: do you mean logging everything and trying to guess stuff?
  412. # [13:10] <annevk> hsivonen, I was hoping they would give examples of things that don't work
  413. # [13:11] <annevk> hsivonen, and if that's the case, doing what Hixie suggested for HTML4 Transitional might not be so bad
  414. # [13:11] <annevk> (and XHTML1 Transitional for that matter)
  415. # [13:11] * Quits: Thezilch (n=fuz007@cpe-76-171-111-7.socal.res.rr.com) (Success)
  416. # [13:11] <hsivonen> annevk: one problem is that people stick to HTML 4 because HTML5 is not 'ready'
  417. # [13:11] <Hixie> to be honest i'm not convinced that most of the pages that use these attributes only use them in their default state
  418. # [13:11] <hsivonen> annevk: I'm myself telling people not to upgrade to HTML5 doctype just yet
  419. # [13:12] <annevk> hsivonen, right, that seems ok
  420. # [13:12] <Hixie> and if people use these attributes in non-default states, they'll have to do some edits anyway
  421. # [13:12] <Hixie> at which point, doing the rest isn't that much of a cost
  422. # [13:12] <annevk> hsivonen, I do encourage people to play with it and say that the HTML5 DOCTYPE just works, but overall waiting a little bit longer is safer
  423. # [13:12] <hsivonen> but once Firefox 3.1 ships with <video>, we need a better story than "don't validate because HTML5 is not ready"
  424. # [13:13] <hsivonen> and I don't know how to do that and avoid an Atom 0.3-like fiasco
  425. # [13:13] <Hixie> (and it's a cost i'd be willing to risk forcing people to take, given the benefits long-term)
  426. # [13:13] <hsivonen> Hixie: the whole point of border=0 is using it in a non-default state
  427. # [13:14] <annevk> hsivonen, Atom 0.3 fiasco won't happen given how we take into account implementations
  428. # [13:14] <hsivonen> Hixie: same for cellspacing and cellpadding
  429. # [13:14] <annevk> cellpading is not necessary
  430. # [13:14] <hsivonen> recommending HTML5 would be so much safer if there were two browsers out there with the parsing algorithm implemented
  431. # [13:15] * Joins: webben (n=benh@nat/yahoo/x-d69a4d73d74fad23)
  432. # [13:15] <annevk> only cellspacing lacks the CSS equivalent in IE, iirc
  433. # [13:15] <othermaciej> or even just one
  434. # [13:15] <Hixie> hsivonen: when would you ever want to specify cellspacing and cellpadding on a data table?
  435. # [13:15] * Quits: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  436. # [13:16] <annevk> hsivonen, the conforming syntax does not depend much on a conforming parser...
  437. # [13:16] <hsivonen> Hixie: you want the cell borders to touch each other but not text
  438. # [13:17] <hsivonen> Hixie: anyway, layout tables are a cowpath if there ever was one
  439. # [13:17] <Hixie> use border-collapse: collapse, you'll get much better control
  440. # [13:17] <Hixie> we don't want to pave cowpaths that go off a cliff
  441. # [13:17] <hsivonen> Hixie: does it work in IE?
  442. # [13:17] * Hixie loads wmware
  443. # [13:17] <Hixie> vmware
  444. # [13:17] <Hixie> my typing tonight sucks, i should go to bed soon :-)
  445. # [13:18] <hsivonen> Hixie: so far, evidence suggests that layout tables are further away from the cliff than e.g. CSS positioning
  446. # [13:18] <Hixie> yeah well the csswg needs to get its act together, but that's a separate story
  447. # [13:18] <Hixie> css layout tables are fine, and even work in IE now
  448. # [13:18] <hsivonen> Hixie: there's no point in poking authors about it until the CSS WG and IE have their "act together"
  449. # [13:19] <Hixie> IE8 will be out before html5 is ready for authors to use in any serious way
  450. # [13:19] <hsivonen> Hixie: do they work in the oldest IE that Gmail still supports?
  451. # [13:19] <Hixie> (and yes, IE supports border-collapse)
  452. # [13:20] * Quits: tusho (n=tusho@91.105.85.60)
  453. # [13:20] <Hixie> hsivonen: gmail only supported one version of IE until very recently where we added IE6 support, so gmail might not be the best example
  454. # [13:20] <hsivonen> Hixie: my point is that there's demand for ARIA validation today and for <video> validation RSN
  455. # [13:21] <hsivonen> Hixie: my point is that IE6 isn't properly dead if Gmail supports it
  456. # [13:22] <annevk> I have a hard time believing those features will be less successful because border=0 does not validate
  457. # [13:22] <annevk> <canvas> was successful and border=0 did not validate either
  458. # [13:22] <Hixie> if there really is demand, we shoudl leverage that demand to get people to move off border=0 and co
  459. # [13:22] <hsivonen> annevk: Validator.nu is at risk of being less successful
  460. # [13:23] <hsivonen> annevk: of course people will pick <video> over validation
  461. # [13:23] <Hixie> but frankly, i doubt <video> will be any more used than <canvas> in the near (12-18 months) term
  462. # [13:23] <hsivonen> annevk: but they shouldn't have to abandon QA tools in order to use <video> or <canvas> or ARIA
  463. # [13:23] <Hixie> if people are using the validator as a QA tool, then a collapsed set of error messages for deprecated attributes would be fine
  464. # [13:24] <Hixie> i thought we were assuming that people using the validator were people who wanted to be perfectly valid always
  465. # [13:24] <hsivonen> Hixie: no, I'm assuming they are people who want to find typos without the typos getting lost in noise
  466. # [13:25] <Hixie> collapsing all the messages into one removes all the noise and places it separately from the typos
  467. # [13:26] <annevk> Is it really hard to collapse the messages? It might at least be worth trying
  468. # [13:27] <hsivonen> annevk: it's not trivial. I'd rather do only non-trivial stuff I believe in
  469. # [13:27] <roc_> What are we doing wrong with table borders?
  470. # [13:28] <hsivonen> roc_: image borders
  471. # [13:28] <hsivonen> roc_: there's a default border on linked images
  472. # [13:28] <roc_> oh
  473. # [13:29] <roc_> there's a bug filed, I assume?
  474. # [13:29] <hsivonen> yes
  475. # [13:29] <hsivonen> looking up the # now
  476. # [13:29] <hsivonen> https://bugzilla.mozilla.org/show_bug.cgi?id=452915
  477. # [13:29] <annevk> hsivonen, wouldn't it be as simple as grouping all attribute error messages for when the attribute name is in legacy-set?
  478. # [13:30] <roc_> thanks
  479. # [13:30] <annevk> hsivonen, http://hsivonen.iki.fi/test/moz/alt.html should test image maps
  480. # [13:31] <hsivonen> annevk: UI is non-trivial
  481. # [13:31] <hsivonen> annevk: the current grouping feature is non-trivial
  482. # [13:33] <hsivonen> annevk: OTOH, if the user isn't expected to be albe to actually toggle stuff in the UI, I might as well send the errors to the bit bucket right away without UI
  483. # [13:34] <annevk> if I had a legacy page I would probably want to know that I have them and where they are located
  484. # [13:48] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  485. # [13:48] <aaronlev> what's the latest thinking about math in html5?
  486. # [13:49] <Hixie> the spec says the latest thinking
  487. # [13:49] <annevk> that is, MathML is supported as part of the HTML syntax and as part of the HTML parser
  488. # [13:49] <Hixie> basically, there is a syntax for mathml in text/html defined, and people are expected to use mathml
  489. # [13:49] <annevk> hah
  490. # [13:53] <Hixie> ok bed time
  491. # [13:53] <Hixie> nn
  492. # [14:01] <Philip`> The spec also includes <img>, which you can use for maths
  493. # [14:03] <annevk> very accessible
  494. # [14:04] <Philip`> The spec also includes <img alt>
  495. # [14:04] <annevk> yes, but no text syntax for math
  496. # [14:05] <Philip`> So use LaTeX :-)
  497. # [14:05] <Philip`> (inside the <img alt>)
  498. # [14:05] <Philip`> (since that's what you'll be generating the image from anyway)
  499. # [14:06] <hsivonen> Philip`: which LaTeX packages to assume?
  500. # [14:07] <Philip`> hsivonen: Whichever ones your LaTeX-subset to image converter provides
  501. # [14:09] <Philip`> s/LaTeX-subset/(La)TeX-inspired language like Itex/
  502. # [14:10] <Philip`> I don't know :-(
  503. # [14:11] <hsivonen> Philip`: so you don't expect a speech generator to grok LaTeX?
  504. # [14:12] * Joins: othermaciej (n=mjs@c-69-181-42-194.hsd1.ca.comcast.net)
  505. # [14:15] <Philip`> hsivonen: It could understand enough of the syntax to assist the user in making sense of the code, e.g. by understanding {} for grouping, and then the human can work out what the symbol and command names mean
  506. # [14:16] <Philip`> That's probably substantially easier than making a speech generator grok MathML
  507. # [14:16] <Philip`> and MathML has the disadvantage that sighted readers can't understand the textual source code either
  508. # [14:17] <hsivonen> Philip`: MathPlayer's speech rendering seems to work
  509. # [14:23] * Joins: kangax (n=kangax@ool-182f8118.dyn.optonline.net)
  510. # [14:41] * Joins: aboodman (n=aboodman@194.110.194.1)
  511. # [14:44] * aboodman is now known as aboodman_london_
  512. # [14:44] * aboodman_london_ is now known as aboodman_london
  513. # [14:48] <Lachy> for determining the encoding algorithm, it whitespace around the value of the charset attribute supposed to be ignored? e.g. charset=" ISO=8859=2 "
  514. # [14:49] <Lachy> the spec only says "If the attribute's name is "charset", let charset be the attribute's value, interpreted as a character encoding."
  515. # [14:49] <Lachy> Hixie, yt?
  516. # [14:50] <takkaria> http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#character1
  517. # [14:50] <takkaria> suggests that you ignore space characters
  518. # [14:51] * Quits: Maghnus (n=Maghnus@68-190-147-184.dhcp.eucl.wi.charter.com) (simmons.freenode.net irc.freenode.net)
  519. # [14:51] * Quits: hendry (n=hendry@nox.vm.bytemark.co.uk) (simmons.freenode.net irc.freenode.net)
  520. # [14:51] <takkaria> but maybe that's a sightly liberal interpretation of the spec
  521. # [14:51] <Lachy> thanks
  522. # [14:53] <annevk> it suggests to ignore more than just space characters, fwiw
  523. # [14:55] * Joins: Maghnus (n=Maghnus@68-190-147-184.dhcp.eucl.wi.charter.com)
  524. # [14:55] * Joins: hendry (n=hendry@nox.vm.bytemark.co.uk)
  525. # [14:59] * Quits: nessy (n=nessy@124-168-155-4.dyn.iinet.net.au) ("This computer has gone to sleep")
  526. # [15:03] * Quits: mpt (n=mpt@canonical/launchpad/mpt) (Remote closed the connection)
  527. # [15:09] * Joins: mpt (n=mpt@canonical/launchpad/mpt)
  528. # [15:16] * Quits: webben (n=benh@nat/yahoo/x-d69a4d73d74fad23)
  529. # [15:17] * Quits: kangax (n=kangax@ool-182f8118.dyn.optonline.net)
  530. # [15:17] * Joins: webben (n=benh@nat/yahoo/x-3defd27320381c98)
  531. # [15:19] * Quits: webben (n=benh@nat/yahoo/x-3defd27320381c98) (Client Quit)
  532. # [15:21] * Joins: BenMillard (i=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  533. # [15:24] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  534. # [15:27] * Joins: aaronlev_ (n=chatzill@g227092026.adsl.alicedsl.de)
  535. # [15:29] <hsivonen> Re: markp's "my precious" tweet: is the Chrome icon Free as in Freedom for use in non-Google builds of Chromium?
  536. # [15:31] * Quits: sverrej (n=sverrej@pat-tdc.opera.com) (Read error: 104 (Connection reset by peer))
  537. # [15:34] * Quits: maikmerten (n=merten@ls5laptop14.cs.uni-dortmund.de) (Remote closed the connection)
  538. # [15:37] * Joins: maikmerten (n=merten@ls5laptop14.cs.uni-dortmund.de)
  539. # [15:38] <Philip`> hsivonen: Their SVN repository only contains chrome/app/theme/chromium, which has the blue Chromium logo (instead of the multicoloured Chrome logo), and it doesn't have the chrome/app/theme/google_chrome directory which is used if you compile with GOOGLE_CHROME_BUILD
  540. # [15:38] * Quits: aaronlev (n=chatzill@g227092026.adsl.alicedsl.de) (Success)
  541. # [15:38] <annevk> did "this week in html5" die?
  542. # [15:38] <Philip`> so I assume the idea is that only Chrome should use the Chrome icon, and everyone else should use the Chromium icon
  543. # [15:39] <Lachy> Philip`, is it possible to browse the SVN online somewhere? I can't find it
  544. # [15:39] <annevk> sounds exactly the same as in Firefox
  545. # [15:39] <annevk> Lachy, http://src.chromium.org/
  546. # [15:48] * Joins: sverrej (n=sverrej@pat-tdc.opera.com)
  547. # [15:53] * Quits: aaronlev_ (n=chatzill@g227092026.adsl.alicedsl.de) (Read error: 110 (Connection timed out))
  548. # [15:56] * Parts: annevk (n=annevk@77.163.243.203)
  549. # [15:56] * Joins: annevk (n=annevk@77.163.243.203)
  550. # [15:58] * Joins: csarven (n=csarven@80.76.201.52)
  551. # [16:02] <hsivonen> Philip`: thanks
  552. # [16:04] * Quits: csarven (n=csarven@80.76.201.52) (Remote closed the connection)
  553. # [16:06] <hsivonen> one might argue that losing color and having to use "ium" is less drastic than losing the fox and calling it a weasel :-)
  554. # [16:08] <Philip`> I expect the people who might care about this don't currently care about this, since Chrom* is nowhere near being able to run on Linux
  555. # [16:09] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) ("Leaving")
  556. # [16:10] <gavin> there are non-weasel generic icons available to people who want to distribute non-branded firefox builds
  557. # [16:11] <hsivonen> gavin: that's what I meant by losing the fox [graphic] compared to merely losing color
  558. # [16:11] <gavin> oh
  559. # [16:12] <gavin> I haven't actually seen the chromium icon
  560. # [16:12] * Philip` wonders why Chrome/Chromium bother changing the 'client' string when making requests to pages like http://safebrowsing.clients.google.com/safebrowsing/diagnostic?site=http://www.google.com&client=googlechrome
  561. # [16:12] <gavin> is colour really the only difference?
  562. # [16:12] <hsivonen> gavin: http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/theme/chromium/product_logo.png?view=markup
  563. # [16:12] <gavin> that seems like it might be a bit risky from a TM protection point of view
  564. # [16:12] <hsivonen> gavin: seems to be only a color difference
  565. # [16:12] <gavin> but IANAL!
  566. # [16:13] <Philip`> (Compare to http://www.google.com/chrome/intl/en/images/logo_sm.jpg)
  567. # [16:14] * hsivonen notes that Safari and WebKit have a color difference
  568. # [16:15] <hsivonen> but I don't know if the WebKit version of the icon is Free
  569. # [16:16] * Joins: [1]Maghnus (n=Maghnus@68-190-147-184.dhcp.eucl.wi.charter.com)
  570. # [16:17] <hsivonen> what does it mean that according to Google, www.google.com has functioned "as an intermediary for the infection of 2 site(s)"?
  571. # [16:18] * Joins: smedero (n=smedero@mdp-nat251.mdp.com)
  572. # [16:20] <gavin> heh
  573. # [16:22] * Parts: BenMillard (i=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  574. # [16:23] * Joins: billmason (n=billmaso@ip75.unival.com)
  575. # [16:24] <Philip`> It's nice to see <blockquote> being used for indentation again
  576. # [16:25] <Philip`> Also nice is <img ... height=32width=78>
  577. # [16:26] * Joins: dotjay (n=dotjay@nov5th.plus.com)
  578. # [16:33] * Quits: Maghnus (n=Maghnus@68-190-147-184.dhcp.eucl.wi.charter.com) (Connection timed out)
  579. # [16:33] * [1]Maghnus is now known as Maghnus
  580. # [16:39] * Philip` sees that Chrome has unfair favouritism towards Google, by prefetching the DNS for www.google.com when you start the browser
  581. # [16:40] <hsivonen> Philip`: is that an explicit call or a side effect of something?
  582. # [16:40] <gavin> doesn't google chrome always ping google for something at startup?
  583. # [16:40] <gavin> update or omnibox or something like that
  584. # [16:40] * gavin doesn't remember the details
  585. # [16:41] <Philip`> hsivonen: It's at the bottom of http://src.chromium.org/svn/trunk/src/chrome/browser/net/dns_global.cc
  586. # [16:42] <Philip`> gavin: I suppose it does that too, though I think you can switch off the send-everything-you-type-in-the-address-bar-to-Google feature if you want
  587. # [16:42] <gavin> yeah,I remember hearing that there was something that wasn'y yet disableable
  588. # [16:42] <gavin> but that they were working on making disableable
  589. # [16:42] <gavin> I just don't remember what it is
  590. # [16:43] <Philip`> There's the Safe Browsing thing too
  591. # [16:44] <hsivonen> Philip`: at least it looks like it's a fallback if there is no overriding config file
  592. # [16:55] * Joins: webben (n=benh@nat/yahoo/x-2adb8c0f0f025ec1)
  593. # [16:57] * Joins: dglazkov (n=dglazkov@nat/google/x-3803faf24e38aabb)
  594. # [16:58] * Joins: aroben (n=aroben@unaffiliated/aroben)
  595. # [17:00] * Quits: maikmerten (n=merten@ls5laptop14.cs.uni-dortmund.de) (Remote closed the connection)
  596. # [17:10] * weinig|zZz is now known as weinig
  597. # [17:13] <hsivonen> Hixie: your exact examples in http://bugzilla.validator.nu/show_bug.cgi?id=258 are now WFM, but I can reproduce the problem with an unclosed <i>
  598. # [17:13] <hsivonen> Hixie: Do you have a suggestion how to fix?
  599. # [17:14] <Lachy> in python, if I have an list of strings like ["a", "b", "c"], is there a method that will concatenate them all into a single string?
  600. # [17:14] <Lachy> with a separator in between
  601. # [17:15] <hsivonen> Hixie: I don't know how to fix without either making it a fatal error to reconstruct formatting elements or to be non-conforming and violate the parsing algorithm
  602. # [17:15] <Philip`> Lachy: "separator".join(["a", "b", "c"])
  603. # [17:15] <Lachy> Philip`, thanks
  604. # [17:16] <hsivonen> Philip`: is http://bugzilla.validator.nu/show_bug.cgi?id=294 now fixed to your satisfaction, or should I vary the message somehow when the tokenizer is in an attribute that takes a URL?
  605. # [17:18] <hsivonen> I'd rather have a good catch-all message and not vary based on attribute identity
  606. # [17:22] <Philip`> hsivonen: It doesn't seem to be fixed at all - if I write e.g. <a href="foo.cgi?src=bar&copy=baz"> then it still says just "Error: Entity reference was not terminated by a semicolon." which isn't very friendly
  607. # [17:24] <hsivonen> hmm. I haven't fixed it all states
  608. # [17:29] * Joins: starjive (i=beos@213-66-217-32-no30.tbcn.telia.com)
  609. # [17:35] * Joins: weinig_ (n=weinig@c-71-198-176-23.hsd1.ca.comcast.net)
  610. # [17:46] * Joins: webben_ (n=benh@nat/yahoo/x-8c21c70413ce0c88)
  611. # [17:46] * Joins: aaronlev_ (n=chatzill@g228024180.adsl.alicedsl.de)
  612. # [17:47] * aaronlev_ is now known as aaronlev
  613. # [17:47] * Quits: webben (n=benh@nat/yahoo/x-2adb8c0f0f025ec1) (Read error: 104 (Connection reset by peer))
  614. # [17:47] * Quits: Lachy (n=Lachlan@pat-tdc.opera.com) ("This computer has gone to sleep")
  615. # [17:52] * Quits: weinig (n=weinig@c-71-198-176-23.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
  616. # [17:55] * Joins: segosa (i=a@client-82-26-17-22.winn.adsl.virgin.net)
  617. # [18:02] * Joins: Lachy (n=Lachlan@85.196.122.246)
  618. # [18:03] * Quits: webben_ (n=benh@nat/yahoo/x-8c21c70413ce0c88) (Connection timed out)
  619. # [18:05] * Quits: Maurice (n=ano@a80-100-71-209.adsl.xs4all.nl) ("Disconnected...")
  620. # [18:16] * Joins: webben (n=benh@nat/yahoo/x-71f04c72dbcaa2b1)
  621. # [18:16] <hsivonen> Philip`: is the bug *now* fixed to your satisfaction?
  622. # [18:19] * Joins: csarven (n=csarven@80.76.201.52)
  623. # [18:22] * Joins: aboodman_london2 (n=aboodman@ip-62-105-190-66.dsl.twang.net)
  624. # [18:23] <Philip`> hsivonen: No - for "<!DOCTYPE html>This page is &copy 2022" it should tell you to write &copy; not &amp;copy
  625. # [18:23] <Philip`> (though for <a href="...&copy=..."> it should suggest the other way around)
  626. # [18:24] * Quits: weinig_ (n=weinig@c-71-198-176-23.hsd1.ca.comcast.net)
  627. # [18:25] <Philip`> (Well, technically, the bug is only talking about URL attributes, so the brokenness of plain-text "... &copy ..." is not relevant, but I still think it's a brokenness :-p )
  628. # [18:29] <Philip`> Also it seems misleading for it to sound so sure about "Error: & should have been escaped as &amp;." (not saying anything vague like "Probable cause") when I write e.g. "... &lamba; ..." and the real error is not the failure to escape &
  629. # [18:29] * Quits: aboodman_london (n=aboodman@194.110.194.1) (Read error: 110 (Connection timed out))
  630. # [18:34] * Joins: wakaba_ (n=w@30.165.210.220.dy.bbexcite.jp)
  631. # [18:38] <hsivonen> Philip`: what about now?
  632. # [18:48] <Philip`> hsivonen: On &lamba;, "& did not start a character reference. (& should have been escaped as &amp;.)" should still probably say "probably should"
  633. # [18:50] <Philip`> The phrasing of "Named character reference was not terminated by a semicolon. (Or & should have been escaped as &amp;.)" sounds odd, but otherwise I think everything seems possibly reasonable :-)
  634. # [18:50] <hsivonen> Philip`: what would you suggest
  635. # [18:53] * Quits: wakaba (n=w@30.165.210.220.dy.bbexcite.jp) (Read error: 110 (Connection timed out))
  636. # [18:55] * Joins: kangax (n=kangax@74.201.136.194)
  637. # [18:57] <Philip`> hsivonen: Would it be hard to make it say something like "Character reference did not end with semicolon. (Should have been written as `&copy;` (©) or `&amp;copy`)"?
  638. # [18:57] <Philip`> (where it extracts the character reference name from the source)
  639. # [18:57] <hsivonen> extracting it from the source would suck
  640. # [18:58] <hsivonen> but extracting it from the name table might work
  641. # [18:58] <Philip`> This is only in cases where it's successfully parsed, so I suppose it can come from the parse representation rather than the source
  642. # [19:00] * Joins: moeffju (i=moeffju@ubermutant.net)
  643. # [19:01] * Joins: sbublava (n=stephan@77.117.153.128)
  644. # [19:01] * Parts: moeffju (i=moeffju@ubermutant.net)
  645. # [19:11] <Philip`> (Please feel free to ignore me if I'm trying to make this far too complicated :-) )
  646. # [19:19] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Connection timed out)
  647. # [19:19] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
  648. # [19:26] * Quits: aaronlev (n=chatzill@g228024180.adsl.alicedsl.de) (Connection timed out)
  649. # [19:29] * Joins: weinig (n=weinig@nat/apple/x-2fedadfd4fb1a880)
  650. # [19:33] * Joins: aaronlev_ (n=chatzill@g228024180.adsl.alicedsl.de)
  651. # [19:33] * aaronlev_ is now known as aaronlev
  652. # [19:43] * Joins: eseidel (n=eseidel@c-24-130-13-197.hsd1.ca.comcast.net)
  653. # [19:49] * Joins: Maurice (i=copyman@cc90688-a.emmen1.dr.home.nl)
  654. # [19:51] * Quits: kangax (n=kangax@74.201.136.194)
  655. # [19:51] * Joins: eseidel_ (n=eseidel@72.14.224.1)
  656. # [20:06] * Quits: eseidel (n=eseidel@c-24-130-13-197.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
  657. # [20:07] * eseidel_ is now known as eseidel
  658. # [20:29] * Quits: sverrej (n=sverrej@pat-tdc.opera.com) ("Ex-Chat")
  659. # [20:32] * Quits: sbublava (n=stephan@77.117.153.128)
  660. # [20:41] * Joins: kangax (n=kangax@74.201.136.194)
  661. # [20:48] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  662. # [20:49] * Quits: jruderman (n=jruderma@c-67-180-39-55.hsd1.ca.comcast.net)
  663. # [20:50] * dglazkov is now known as dglazkov|lunch
  664. # [20:56] * Joins: BenMillard (i=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  665. # [21:06] <BenMillard> Anyone feel like reviewing another follow-up from me about the headers+id thread?
  666. # [21:11] <BenMillard> I've e-mailed it to a bunch of you, now I'm off to watch Fifth Gear. :)
  667. # [21:12] * Parts: BenMillard (i=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  668. # [21:28] * dglazkov|lunch is now known as dglazkov
  669. # [22:03] * Joins: jruderman (n=jruderma@corp-241.mountainview.mozilla.com)
  670. # [22:16] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  671. # [22:27] * Quits: eseidel (n=eseidel@72.14.224.1)
  672. # [22:35] * Quits: roc_ (n=chatzill@121-72-177-254.dsl.telstraclear.net) ("ChatZilla 0.9.83 [Firefox 3.0.1/2008070206]")
  673. # [22:36] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  674. # [22:38] * Joins: malde_ (n=chatzill@d043209.adsl.hansenet.de)
  675. # [22:40] * Joins: ginger (n=nessy@124-168-155-4.dyn.iinet.net.au)
  676. # [22:44] * Joins: eseidel (n=eseidel@c-24-130-13-197.hsd1.ca.comcast.net)
  677. # [22:51] * Joins: eseidel_ (n=eseidel@72.14.224.1)
  678. # [22:55] * Quits: ROBOd (n=robod@89.122.216.38) ("http://www.robodesign.ro")
  679. # [22:56] * Quits: eseidel_ (n=eseidel@72.14.224.1)
  680. # [23:07] * Quits: eseidel (n=eseidel@c-24-130-13-197.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
  681. # [23:08] * Joins: eseidel (n=eseidel@adsl-76-216-8-172.dsl.pltn13.sbcglobal.net)
  682. # [23:13] * gsnedders yawns
  683. # [23:13] <gsnedders> I don't like writing a personal statement
  684. # [23:14] <gsnedders> I suck at sounding motivated to do physics
  685. # [23:15] * Quits: eseidel (n=eseidel@adsl-76-216-8-172.dsl.pltn13.sbcglobal.net)
  686. # [23:16] <Philip`> Are you motivated to do physics?
  687. # [23:18] <gsnedders> Yeah.
  688. # [23:18] <Philip`> Good - that should make it somewhat easier :-)
  689. # [23:18] <gsnedders> :)
  690. # [23:18] <gsnedders> I still suck at knowing what to write
  691. # [23:19] <gsnedders> I can write stuff that makes me look awesome at comp.sci., but when 1/5th of the places your applying to are comp.sci., that isn't overly relevant
  692. # [23:19] * Quits: aaronlev (n=chatzill@g228024180.adsl.alicedsl.de) (Connection timed out)
  693. # [23:19] <gsnedders> (the other 4/5th are phys.)
  694. # [23:20] <Hixie> hsivonen: yeah i realised a few weeks ago that making the parser rules normative for a validator might be counter-productive
  695. # [23:20] <Hixie> hsivonen: it might be that we should change the spec to allow validators to do whatever they like to recover once they hit one error in the parser
  696. # [23:21] * Joins: eseidel (n=eseidel@adsl-76-216-8-172.dsl.pltn13.sbcglobal.net)
  697. # [23:22] * Quits: Maurice (i=copyman@cc90688-a.emmen1.dr.home.nl) ("Disconnected...")
  698. # [23:34] <Philip`> http://www.codeweavers.com/services/ports/chromium/
  699. # [23:35] * Philip` sees that they're using the multicoloured Chrome logo
  700. # [23:39] <hendry> Philip`: i can't figure out what to run after installing it.
  701. # [23:40] <Philip`> hendry: I haven't even installed it, so I can't help :-(
  702. # [23:43] <Lachy> hendry, on which platform?
  703. # [23:45] <Lachy> woah, the icon they've used for the OSX icon is terrible. The resolution is far too low.
  704. # [23:46] <Lachy> looks like they've just stretched the 32px windows icon
  705. # [23:46] <hendry> Lachy: debian/linux
  706. # [23:47] <Lachy> there must be an executable somewhere. It's probably called "chromium" or something like that
  707. # [23:48] <Lachy> maybe you have to start it from the command line if there's nothing you can double click to launch
  708. # [23:49] <hendry> Lachy: there is http://www.flickr.com/photos/hendry/2860126641/ but I get "cannot execute binary file". I'll try in the morning after I've sobered up.
  709. # [23:50] * Quits: malde_ (n=chatzill@d043209.adsl.hansenet.de) (Read error: 110 (Connection timed out))
  710. # [23:50] <Lachy> hendry, what's the relevance of the flickr photo?
  711. # [23:51] * Quits: gsnedders (n=gsnedder@host81-156-236-33.range81-156.btcentralplus.com) ("Killin' teh intarwebs")
  712. # [23:51] * jgraham strongly suspects a msipaste
  713. # [23:51] * Quits: weinig (n=weinig@nat/apple/x-2fedadfd4fb1a880)
  714. # [23:52] <Lachy> the OSX version doesn't integrate well with the system
  715. # [23:52] <Hixie> oh dear, svg 1.2 tiny is back in last call
  716. # [23:53] <Lachy> Hixie, did it drop back from CR, or progress from WD?
  717. # [23:53] <Dashiva> So there's tiny and basic, who implements full?
  718. # [23:54] * Quits: csarven (n=csarven@80.76.201.52) (Remote closed the connection)
  719. # [23:54] <hendry> Lachy: oh crap, wrong link. i meant: /opt/cxchromium/support/chromium/drive_c/chromium/chrome.exe /me goes to sleep now
  720. # [23:56] <Lachy> well, that would be the windows executable. I'm guessing you need to use Wine to launch it somehow, though I've no idea how that works
  721. # [23:57] <Hixie> Lachy: progressed from LC, i think
  722. # [23:57] <jgraham> Running it under crossover seems like a bad way to get a fair first impression. I guess the animation and scrolling suck less on a native build
  723. # [23:59] <Lachy> it's definitely not good to run on the Mac. It's bad enough being like a windows up, but the integration problems make it largely unusable
  724. # Session Close: Tue Sep 16 00:00:00 2008

The end :)