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

Options:

  1. # Session Start: Tue Sep 15 00:00:00 2009
  2. # Session Ident: #whatwg
  3. # [01:49] * Disconnected
  4. # [01:50] * Attempting to rejoin channel #whatwg
  5. # [01:50] * Rejoined channel #whatwg
  6. # [01:50] * Topic is 'WHATWG (HTML5) -- http://www.whatwg.org/ -- Logs: http://krijnhoetmer.nl/irc-logs/ -- Please leave your sense of logic at the door, thanks!'
  7. # [01:50] * Set by annevk3 on Wed Sep 09 23:23:54
  8. # [01:50] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  9. # [01:52] * Joins: sicking (n=chatzill@adsl-76-228-82-245.dsl.pltn13.sbcglobal.net)
  10. # [01:52] <sicking> Hixie: ping
  11. # [01:53] * Quits: dglazkov (n=dglazkov@nat/google/x-cnxzourcpcbwwgqf)
  12. # [02:02] * Quits: cying (n=cying@70.90.171.153)
  13. # [02:03] * Joins: cying (n=cying@70.90.171.153)
  14. # [02:07] * Quits: ifette_GOOG (n=ifette@nat/google/x-unvdsguivzvphqft) (Read error: 110 (Connection timed out))
  15. # [02:07] <roc> annevk2: <hr> and <input> has never been done through XBL
  16. # [02:07] * Quits: cying (n=cying@70.90.171.153) (Client Quit)
  17. # [02:07] <roc> well, <input> was as an experiment that never shipped
  18. # [02:08] * Joins: jacobolus (n=jacobolu@dhcp-0014706724-55-9e.client.law.harvard.edu)
  19. # [02:08] * Joins: cying (n=cying@70.90.171.153)
  20. # [02:12] * Quits: cardona507 (n=cardona5@c-67-180-160-250.hsd1.ca.comcast.net)
  21. # [02:13] * Quits: tantek (n=tantek@dsl081-241-091.sfo1.dsl.speakeasy.net)
  22. # [02:19] * Joins: miketaylr (n=miketayl@user-0cdf5gs.cable.mindspring.com)
  23. # [02:28] * Quits: benward (n=benward@nat/yahoo/x-mjyuftkevnkaixzd) (Read error: 110 (Connection timed out))
  24. # [02:30] * Joins: webben_ (n=benh@91.85.72.193)
  25. # [02:34] * Quits: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net) (Read error: 113 (No route to host))
  26. # [02:36] * Joins: takoratta (n=takoratt@220.109.219.244)
  27. # [02:40] * Quits: webben (n=benh@dip5-fw.corp.ukl.yahoo.com) (Read error: 110 (Connection timed out))
  28. # [02:41] <othermaciej> Lachy: are you about?
  29. # [02:41] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  30. # [02:42] * Joins: nessy (n=nessy@203-214-137-48.perm.iinet.net.au)
  31. # [02:48] * Joins: murr4y` (n=murray@85.84-49-67.nextgentel.com)
  32. # [02:58] * Quits: weinig (n=weinig@17.246.16.129)
  33. # [02:59] * Quits: murr4y (n=murray@85.84-49-67.nextgentel.com) (Read error: 104 (Connection reset by peer))
  34. # [02:59] * Quits: JonathanNeal (n=Jonathan@rrcs-76-79-114-216.west.biz.rr.com) (No route to host)
  35. # [03:04] * Joins: tantek (n=tantek@70.36.139.108)
  36. # [03:05] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  37. # [03:06] * Quits: yael (i=d0309a43@gateway/web/freenode/x-jzmafqnesnnuijdn) ("Page closed")
  38. # [03:09] * Quits: Super-Dot (n=Super-Do@66-240-27-50.isp.comcastbusiness.net)
  39. # [03:11] * Quits: cying (n=cying@70.90.171.153) (Remote closed the connection)
  40. # [03:11] * Joins: cying (n=cying@70.90.171.153)
  41. # [03:11] * Joins: StationsPatient (n=kristall@c-base/crew/kristall)
  42. # [03:12] * Quits: ttepass- (n=ttepas--@p5B015C4E.dip.t-dialin.net) ("?Q")
  43. # [03:12] * Joins: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley)
  44. # [03:16] * Quits: ap (n=ap@17.203.14.219)
  45. # [03:16] * Joins: MikeSmithX (n=MikeSmit@EM114-48-85-114.pool.e-mobile.ne.jp)
  46. # [03:18] * Quits: fishd (n=darin@nat/google/x-fgbhxaskxqyvdbrk) (Read error: 60 (Operation timed out))
  47. # [03:20] * Quits: tantek (n=tantek@70.36.139.108)
  48. # [03:21] * Quits: heycam (n=cam@clm-laptop.infotech.monash.edu.au) ("bye")
  49. # [03:21] * Joins: heycam (n=cam@clm-laptop.infotech.monash.edu.au)
  50. # [03:23] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  51. # [03:25] * Joins: arun__ (n=arun@adsl-75-36-189-9.dsl.pltn13.sbcglobal.net)
  52. # [03:27] * Quits: GarethAdams (n=GarethAd@pdpc/supporter/active/GarethAdams)
  53. # [03:32] * Quits: MikeSmith (n=MikeSmit@EM114-48-25-153.pool.e-mobile.ne.jp) (Read error: 110 (Connection timed out))
  54. # [03:33] * Joins: tantek (n=tantek@70.36.139.108)
  55. # [03:33] * Quits: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley) (Read error: 110 (Connection timed out))
  56. # [03:34] * Joins: weinig (n=weinig@17.246.16.129)
  57. # [03:37] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  58. # [03:37] * Joins: dbaron (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net)
  59. # [03:38] * Quits: tantek (n=tantek@70.36.139.108) (Client Quit)
  60. # [03:38] * Joins: tantek (n=tantek@70.36.139.108)
  61. # [03:43] * Quits: KevinMarks (n=KevinMar@157.22.22.46) ("The computer fell asleep")
  62. # [03:47] * Quits: cying (n=cying@70.90.171.153)
  63. # [03:51] * Joins: lazni (n=lazni@118.71.169.163)
  64. # [03:52] * Joins: othermaciej_ (n=mjs@17.246.18.86)
  65. # [03:54] * Quits: jacobolus (n=jacobolu@dhcp-0014706724-55-9e.client.law.harvard.edu) (Remote closed the connection)
  66. # [04:06] * Quits: jamesr (n=jamesr@nat/google/x-wcbjicshblqmmsra)
  67. # [04:07] * Quits: othermaciej (n=mjs@nat/apple/x-legqrpmlyzqtnswd) (Read error: 110 (Connection timed out))
  68. # [04:07] * othermaciej_ is now known as othermaciej
  69. # [04:08] <boblet> does anyone know what the deal is with http-equiv="X-UA-Compatible" in HTML5? not allowed b/c versioning? jury is out? other?
  70. # [04:11] * Joins: Super-Dot (n=Super-Do@66-240-27-50.isp.comcastbusiness.net)
  71. # [04:16] * Joins: JonathanNeal (n=Jonathan@76-219-69-134.lightspeed.breaca.sbcglobal.net)
  72. # [04:20] * Quits: dbaron (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net) ("8403864 bytes have been tenured, next gc will be global.")
  73. # [04:21] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  74. # [04:31] * Joins: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com)
  75. # [04:32] <mpilgrim> if anyone had "2.5 hours" in the "how long will it take john foliot to lose his shit after we start discussing summary" pool, you're a winner!
  76. # [04:33] * Quits: othermaciej (n=mjs@17.246.18.86) (Remote closed the connection)
  77. # [04:33] * Joins: othermaciej (n=mjs@nat/apple/x-neazwitbfxyghplg)
  78. # [04:39] * Quits: JonathanNeal (n=Jonathan@76-219-69-134.lightspeed.breaca.sbcglobal.net) ("Leaving")
  79. # [04:44] * Quits: StationsPatient (n=kristall@c-base/crew/kristall) ("Wünsche weiterhin guten Flug")
  80. # [04:49] <othermaciej> I have reminded John that he signed off on the current draft text and encouraged him to dial down his rhetoric accordingly
  81. # [04:49] * Quits: jwalden (n=waldo@nat/mozilla/x-ixbqqidwzqnlslwj) ("ChatZilla 0.9.85 [Firefox 3.5.4pre/20090910030819]")
  82. # [04:55] * Joins: cying (n=cying@adsl-75-18-225-53.dsl.pltn13.sbcglobal.net)
  83. # [04:57] * Quits: sicking (n=chatzill@adsl-76-228-82-245.dsl.pltn13.sbcglobal.net) (Read error: 60 (Operation timed out))
  84. # [04:58] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  85. # [04:58] * Quits: jorlow (n=jorlow@nat/google/x-fahmmyadbjloufcj)
  86. # [05:00] * Joins: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley)
  87. # [05:05] * Joins: slightlyoff_ (n=slightly@67.218.106.174)
  88. # [05:08] * Quits: fearphage (n=fearphag@xbmc/user/fearphage) (farmer.freenode.net irc.freenode.net)
  89. # [05:08] * Quits: Lachy (n=Lachlan@85.196.122.246) (farmer.freenode.net irc.freenode.net)
  90. # [05:08] * Quits: othermaciej (n=mjs@nat/apple/x-neazwitbfxyghplg) (farmer.freenode.net irc.freenode.net)
  91. # [05:08] * Quits: ifette (n=ifette@nat/google/x-bltkwlrbdzhyrour) (farmer.freenode.net irc.freenode.net)
  92. # [05:08] * Quits: dpranke (n=Adium@nat/google/x-yazuswgcxywarcdf) (farmer.freenode.net irc.freenode.net)
  93. # [05:08] * Quits: paul_irish (n=paul_iri@12.33.239.250) (farmer.freenode.net irc.freenode.net)
  94. # [05:08] * Quits: vvv (n=vvv@mediawiki/VasilievVV) (farmer.freenode.net irc.freenode.net)
  95. # [05:08] * Quits: tyoshino (n=tyoshino@220.109.219.244) (farmer.freenode.net irc.freenode.net)
  96. # [05:08] * Quits: karlushi (n=karlushi@fw.vdl2.ca) (farmer.freenode.net irc.freenode.net)
  97. # [05:08] * Quits: aboodman2 (n=aboodman@72.14.229.81) (farmer.freenode.net irc.freenode.net)
  98. # [05:08] * Quits: hendry (n=hendry@webvm.net) (farmer.freenode.net irc.freenode.net)
  99. # [05:08] * Quits: cying (n=cying@adsl-75-18-225-53.dsl.pltn13.sbcglobal.net) (farmer.freenode.net irc.freenode.net)
  100. # [05:08] * Quits: slightlyoff (n=slightly@nat/google/x-wqrlxgfmxcloqeke) (farmer.freenode.net irc.freenode.net)
  101. # [05:08] * Quits: pablof (n=palbo@pat-tdc.opera.com) (farmer.freenode.net irc.freenode.net)
  102. # [05:08] * slightlyoff_ is now known as slightlyoff
  103. # [05:08] * Joins: Lachy (n=Lachlan@85.196.122.246)
  104. # [05:08] * Joins: fearphage (n=fearphag@xbmc/user/fearphage)
  105. # [05:08] * Joins: othermaciej (n=mjs@nat/apple/x-neazwitbfxyghplg)
  106. # [05:08] * Joins: ifette (n=ifette@nat/google/x-bltkwlrbdzhyrour)
  107. # [05:08] * Joins: dpranke (n=Adium@nat/google/x-yazuswgcxywarcdf)
  108. # [05:08] * Joins: paul_irish (n=paul_iri@12.33.239.250)
  109. # [05:08] * Joins: vvv (n=vvv@mediawiki/VasilievVV)
  110. # [05:08] * Joins: tyoshino (n=tyoshino@220.109.219.244)
  111. # [05:08] * Joins: karlushi (n=karlushi@fw.vdl2.ca)
  112. # [05:08] * Joins: aboodman2 (n=aboodman@72.14.229.81)
  113. # [05:08] * Joins: hendry (n=hendry@webvm.net)
  114. # [05:12] * Joins: pablof (n=palbo@213.236.208.22)
  115. # [05:14] * Joins: cying (n=cying@adsl-75-18-225-53.dsl.pltn13.sbcglobal.net)
  116. # [05:14] * Quits: wakaba_0 (n=wakaba_@13.136.148.210.dy.bbexcite.jp) ("Leaving...")
  117. # [05:14] <Hixie> boblet: it's redundant, since all versions of browsers are required to act the same way. :-)
  118. # [05:15] <boblet> Hixie: heh, nice. Thanks for the answer
  119. # [05:18] * Quits: miketaylr (n=miketayl@user-0cdf5gs.cable.mindspring.com)
  120. # [05:20] * Quits: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley) (Read error: 110 (Connection timed out))
  121. # [05:22] * Hixie blinks at jf's e-mail
  122. # [05:22] <Hixie> i thought what the spec said today was in fact jf's idea
  123. # [05:22] <Hixie> it's certainly not what i want the spec to say
  124. # [05:27] * Joins: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley)
  125. # [05:28] * Joins: JonathanNeal (n=Jonathan@76-219-69-134.lightspeed.breaca.sbcglobal.net)
  126. # [05:31] * Quits: slightlyoff (n=slightly@67.218.106.174)
  127. # [05:38] <MikeSmithX> Hixie: about r3852, if <span title=&> is now not a parse error, then title=&&> and ...title=&&&>, etc., are not either, right?
  128. # [05:40] <Hixie> title=&& never was, as far as i know, and title=&&> was only because of the >, which is now no longer an error case (never was, according to the syntax section)
  129. # [05:42] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  130. # [05:42] <MikeSmithX> OK
  131. # [05:43] * Joins: othermaciej_ (n=mjs@17.246.18.86)
  132. # [05:44] * Joins: cohitre_ (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  133. # [05:51] * Quits: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley) (Read error: 110 (Connection timed out))
  134. # [05:52] * Joins: nattokirai_ (n=nattokir@wave.mozilla.or.jp)
  135. # [05:54] * Quits: nattokirai (n=nattokir@gw0.mozilla.or.jp) (Read error: 60 (Operation timed out))
  136. # [05:54] * nattokirai_ is now known as nattokirai
  137. # [05:54] * Joins: cohitre__ (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  138. # [05:55] * Quits: cohitre_ (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Read error: 104 (Connection reset by peer))
  139. # [05:58] * Quits: arun__ (n=arun@adsl-75-36-189-9.dsl.pltn13.sbcglobal.net)
  140. # [06:00] * Quits: othermaciej (n=mjs@nat/apple/x-neazwitbfxyghplg) (Read error: 110 (Connection timed out))
  141. # [06:00] * Quits: virtuelv (n=virtuelv@125.175.251.212.customer.cdi.no) ("Ex-Chat")
  142. # [06:00] * Quits: othermaciej_ (n=mjs@17.246.18.86) (Read error: 110 (Connection timed out))
  143. # [06:01] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Read error: 110 (Connection timed out))
  144. # [06:10] * Quits: tantek (n=tantek@70.36.139.108)
  145. # [06:14] * Quits: cohitre__ (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Connection reset by peer)
  146. # [06:14] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  147. # [06:17] * Quits: lazni (n=lazni@118.71.169.163) ("Leaving.")
  148. # [06:19] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Read error: 104 (Connection reset by peer))
  149. # [06:20] * Joins: lazni (n=lazni@123.24.144.172)
  150. # [06:24] * Quits: paul_irish (n=paul_iri@12.33.239.250)
  151. # [06:41] * Joins: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley)
  152. # [06:49] * Quits: Super-Dot (n=Super-Do@66-240-27-50.isp.comcastbusiness.net)
  153. # [06:57] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  154. # [06:57] * Quits: dave_levin (n=dave_lev@74.125.59.73)
  155. # [07:00] * Joins: arun__ (n=arun@adsl-75-36-189-9.dsl.pltn13.sbcglobal.net)
  156. # [07:06] * Joins: nattokirai_ (n=nattokir@gw0.mozilla.or.jp)
  157. # [07:06] * Joins: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  158. # [07:10] * Joins: sicking (n=chatzill@c-69-181-197-163.hsd1.ca.comcast.net)
  159. # [07:12] * Quits: sicking (n=chatzill@c-69-181-197-163.hsd1.ca.comcast.net) (Remote closed the connection)
  160. # [07:13] * Joins: cardona507 (n=cardona5@c-67-180-160-250.hsd1.ca.comcast.net)
  161. # [07:24] * Quits: nattokirai (n=nattokir@wave.mozilla.or.jp) (Read error: 110 (Connection timed out))
  162. # [07:24] * nattokirai_ is now known as nattokirai
  163. # [07:28] * Quits: weinig (n=weinig@17.246.16.129)
  164. # [07:31] * Joins: gavin__ (n=gavin@99.226.207.11)
  165. # [07:33] * Joins: zalan (n=zalan@catv-89-135-144-193.catv.broadband.hu)
  166. # [07:35] * Quits: gavin_ (n=gavin@firefox/developer/gavin) (Read error: 60 (Operation timed out))
  167. # [07:38] * Joins: takoratt_ (n=takoratt@220.109.219.244)
  168. # [07:38] * dimich is now known as dimich_away
  169. # [07:38] * Joins: jamesr (n=jamesr@72.14.224.1)
  170. # [07:44] <hsivonen> Philip`: regarding your email to rdf-in-xhtml-tf, I find it more disappointing that parties other than Google claimed that Google implements RDFa
  171. # [07:49] * Joins: lazni1 (n=lazni@118.71.169.163)
  172. # [07:49] * Parts: jamesr (n=jamesr@72.14.224.1)
  173. # [07:56] * Quits: lazni (n=lazni@123.24.144.172) (Read error: 60 (Operation timed out))
  174. # [07:57] * Quits: takoratta (n=takoratt@220.109.219.244) (Read error: 110 (Connection timed out))
  175. # [07:59] * Quits: roc (n=roc@203-97-204-82.dsl.clear.net.nz)
  176. # [08:06] * Quits: arun__ (n=arun@adsl-75-36-189-9.dsl.pltn13.sbcglobal.net)
  177. # [08:07] * Joins: webben (n=benh@dip5-fw.corp.ukl.yahoo.com)
  178. # [08:08] * Quits: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley) ("This computer has gone to sleep")
  179. # [08:13] * Joins: tantek (n=tantek@98.210.152.244)
  180. # [08:23] * Quits: doublec (n=doublec@203-97-204-82.dsl.clear.net.nz) ("Leaving")
  181. # [08:23] * Quits: webben_ (n=benh@91.85.72.193) (Read error: 110 (Connection timed out))
  182. # [08:24] * Joins: fishd (n=darin@67.180.164.209)
  183. # [08:24] * Quits: fishd (n=darin@67.180.164.209) (Client Quit)
  184. # [08:29] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  185. # [08:30] <MikeSmithX> hsivonen: patch - http://bugzilla.validator.nu/attachment.cgi?id=115
  186. # [08:31] <MikeSmithX> for http://bugzilla.validator.nu/show_bug.cgi?id=653
  187. # [08:32] <MikeSmithX> seems like a dead-simple change, but just want to make sure I didn't miss anything elsewhere
  188. # [08:32] * MikeSmithX is now known as MikeSmith
  189. # [08:36] * Joins: Mrmil (n=ut_ollie@host-77-236-204-8.blue4.cz)
  190. # [08:36] * Quits: tantek (n=tantek@98.210.152.244) (Read error: 104 (Connection reset by peer))
  191. # [08:38] * Quits: heycam (n=cam@clm-laptop.infotech.monash.edu.au) ("bye")
  192. # [08:38] * Joins: tantek (n=tantek@98.210.152.244)
  193. # [08:39] * Quits: tantek (n=tantek@98.210.152.244) (Client Quit)
  194. # [08:39] * Joins: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl)
  195. # [08:43] * Quits: cardona507 (n=cardona5@c-67-180-160-250.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  196. # [08:45] * Joins: cardona507 (n=cardona5@c-67-180-160-250.hsd1.ca.comcast.net)
  197. # [08:50] * Joins: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  198. # [08:53] <hsivonen> MikeSmith: looks good
  199. # [08:54] <othermaciej> hsivonen: what do you think of the PFWG idea of issuing a validator warning every time a <table> element is used (effectively)?
  200. # [08:55] * Joins: GarethAdams (n=GarethAd@pdpc/supporter/active/GarethAdams)
  201. # [08:56] <hsivonen> othermaciej: I think it doesn't make sense to issue a warning on every table especially if the PFWG position is along the lines that summary isn't always necessary but the feature must remain for use when the table is confusing enough to need it
  202. # [08:57] <hsivonen> othermaciej: as an aside, I haven't fully reviewed the proposed text yet, but I noticed that one of the sample summaries contains data that any screen reader that doesn't suck should be able to voice from the table model given headers marked up as <th>
  203. # [08:58] <hsivonen> suggesting that authors include such text because AT vendors don't get their act together seems to get Priority of Constituencies the wrong way
  204. # [08:58] <othermaciej> hsivonen: Cynthia's comments about autogenerated summary seem to be related
  205. # [08:59] <Philip`> hsivonen: Those people didn't have any way to verify Google's claims (until now), so it doesn't seem unreasonable for them to have assumed Google did something sane
  206. # [09:00] <hsivonen> Philip`: maybe my default assumption in the absence of evidence to contrary was correct but more cynical than other people's
  207. # [09:01] <othermaciej> it seems to me that if we want to consider autogenerated summary, it's much better for the UA/AT side to generate it, than the authoring tool side
  208. # [09:01] <hsivonen> othermaciej: indeed
  209. # [09:01] <othermaciej> hsivonen: anyway - would be good to have some level-headed mailing list feedback on this once you have reviewed the proposal enough
  210. # [09:02] <hsivonen> othermaciej: ok
  211. # [09:02] <hsivonen> Philip`: note that I don't mean to disparage Google in any way. That's just my default assumption about *any* even vaguely Namespace-related software--that I assume it's not correct until shown correct
  212. # [09:03] * Joins: pesla (n=retep@procurios.xs4all.nl)
  213. # [09:04] <Philip`> hsivonen: It seems reasonable to assume they'll have a few bugs, but it also seems reasonable to assume they'll have at least attempted to do something basically correct and not just totally ignored the whole specification
  214. # [09:04] <hsivonen> Philip`: fair enough
  215. # [09:05] <hsivonen> Philip`: indeed, I didn't expect the deviation from the spec to be as great as you have shown
  216. # [09:05] <Philip`> It seems kind of like whoever designed Google's RDFa support just read the RDFa Primer and didn't bother with the proper spec or with understanding RDF or namespaces at all
  217. # [09:05] <othermaciej> so they implemented RegexpDFa?
  218. # [09:06] <hsivonen> Philip`: it's also possible that whoever designed it understood it and deemed the specced approach too complex
  219. # [09:06] * Philip` doesn't mean to be personally offensive to whoever designed or implemented it, but maybe he does because it seems pretty rubbish :-p
  220. # [09:09] <Philip`> hsivonen: Too complex to implement, or too complex to author?
  221. # [09:09] <othermaciej> the nested types bug is surprising
  222. # [09:09] <othermaciej> er, nested properties
  223. # [09:10] <hsivonen> Philip`: to author, because I'd assume Google can get software implemented
  224. # [09:11] <Philip`> othermaciej: Doesn't seem too surprising giving that they seemingly don't support @datatype, and in the absence of @datatype RDFa says you shouldn't recurse into property elements (they should just be treated as XMLLiterals instead)
  225. # [09:12] <othermaciej> Philip`: I see
  226. # [09:12] <hsivonen> Philip`: whoa! does RDFa default to XMLLiterals as opposed to plain strings for property values?
  227. # [09:12] <Philip`> (You have to use datatype="" to stop that XMLLiteral behaviour)
  228. # [09:12] <hsivonen> interesting!
  229. # [09:12] <Philip`> hsivonen: Yes, though I think they're thinking of changing that in RDFa 1.1
  230. # [09:13] <Philip`> (Well, it defaults to XMLLiterals if there are any element children - if it's just text then it's an untyped string literal)
  231. # [09:13] * Joins: heycam (n=cam@210-84-56-211.dyn.iinet.net.au)
  232. # [09:13] <hsivonen> (I guess this reveals that I've never taken the time to be exhaustive in review of RDFa)
  233. # [09:13] <hsivonen> (I've stopped at earlier issues)
  234. # [09:14] <hsivonen> Philip`: ok. that's reasonable in a way
  235. # [09:14] * Joins: fishd (n=darin@72.14.224.1)
  236. # [09:14] <Philip`> hsivonen: If they wanted to make it easier to author, it seems there would be far better ways of doing that in a way that's still largely compatible with RDFa, e.g. do all the proper CURIE processing but then have a special hack for values with an undeclared prefix "v" or something
  237. # [09:14] * Quits: fishd (n=darin@72.14.224.1) (Read error: 104 (Connection reset by peer))
  238. # [09:14] * Quits: MikeSmith (n=MikeSmit@EM114-48-85-114.pool.e-mobile.ne.jp) (Read error: 104 (Connection reset by peer))
  239. # [09:15] * Joins: fishd (n=darin@72.14.224.1)
  240. # [09:15] <hsivonen> Philip`: good point
  241. # [09:16] <Philip`> What's the longest it should take for a message to reach a W3C list (if the author's never posted before and it does the slow authorisation stuff)?
  242. # [09:16] * Joins: KevinMarks (n=KevinMar@c-67-164-14-96.hsd1.ca.comcast.net)
  243. # [09:20] <hsivonen> why does the spec suggest a weird Mood–Grade table?
  244. # [09:20] <hsivonen> wouldn't the best way of making it accessible be making it non-weird?
  245. # [09:20] * hsivonen is rather surprised to find the Mood–Grade in the main spec
  246. # [09:22] * Quits: cardona507 (n=cardona5@c-67-180-160-250.hsd1.ca.comcast.net)
  247. # [09:23] * Joins: MikeSmith (n=MikeSmit@EM114-48-205-177.pool.e-mobile.ne.jp)
  248. # [09:24] <othermaciej> what's Mood-Grade?
  249. # [09:24] <hsivonen> othermaciej: see http://www.whatwg.org/specs/web-apps/current-work/#the-table-element
  250. # [09:24] <hsivonen> othermaciej: search string "For instance, the following table:"
  251. # [09:25] <jgraham_> hsivonen: I think Hixie wanted a short but odd table
  252. # [09:25] <jgraham_> I agree it sucks though
  253. # [09:26] <othermaciej> that is a weird table
  254. # [09:26] * hsivonen has trouble locating validator-sensitive text in the draft Cynthia posted
  255. # [09:27] * jgraham_ is disappointed but not too surprised that PFWG have retreated away from the compromise in the spec to something rather close to their originl position
  256. # [09:28] <Hixie> hsivonen: i needed a table that had table headers in the middle or that was otherwise not something that a brief scan of the table would show to be a simple table to understand
  257. # [09:28] <othermaciej> hsivonen: http://dev.w3.org/html5/pf-summary/Overview.html#guidance-for-conformance-checkers-0
  258. # [09:29] <Hixie> hsivonen: if you have any better suggestions for a table that really needs summary, let me know
  259. # [09:30] <hsivonen> othermaciej: ooh. Thanks.
  260. # [09:36] * Joins: lazni (n=lazni@123.16.249.115)
  261. # [09:38] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) ("Ex-Chat")
  262. # [09:44] * Quits: lazni1 (n=lazni@118.71.169.163) (Read error: 60 (Operation timed out))
  263. # [09:55] * Quits: GarethAdams (n=GarethAd@pdpc/supporter/active/GarethAdams)
  264. # [10:16] * Quits: takoratt_ (n=takoratt@220.109.219.244) ("Leaving...")
  265. # [10:19] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  266. # [10:19] * Joins: weinig_ (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  267. # [10:20] * weinig_ is now known as weinig
  268. # [10:24] * Joins: mat_t (n=mattomas@91.189.88.12)
  269. # [10:27] <othermaciej> what are the existing extensibility mechanisms in HTML5? ones I can think of: class, rel, meta, XML namespaces in XML syntax, data- attributes, "other applicable specifications" clause
  270. # [10:27] <othermaciej> did I miss any?
  271. # [10:27] <jgraham_> microdata?
  272. # [10:28] <Hixie> othermaciej: the faq has a whole bunch of them
  273. # [10:28] <Hixie> http://wiki.whatwg.org/wiki/FAQ#HTML5_should_support_a_way_for_anyone_to_invent_new_elements.21
  274. # [10:28] <othermaciej> jgraham_: duh!
  275. # [10:28] * Joins: fishd_ (n=darin@c-67-180-164-209.hsd1.ca.comcast.net)
  276. # [10:28] <othermaciej> Hixie: thanks
  277. # [10:30] * othermaciej mulls over <script type="">, plugins, and extending APIs via JavaScript
  278. # [10:30] * jgraham_ thought that script libraries altering prototypes was considered bad form
  279. # [10:31] <othermaciej> I think I will stick to markup-level extensibility in what I'm writing for the most part
  280. # [10:32] <annevk2> roc, I meant the <hr> and <input> that are displayed when you use <isindex>
  281. # [10:32] <othermaciej> wasn't there a third registry besides meta and rel extensions?
  282. # [10:32] <hsivonen> othermaciej: do you have an opinion on the idea of allowing reverse-DNS identifiers in element name as an extension mechanism?
  283. # [10:33] <Hixie> othermaciej: http-equiv
  284. # [10:33] <othermaciej> hsivonen: mixed feelings
  285. # [10:34] <othermaciej> hsivonen: on the plus side... something that's clearly a prefix-based convention is likely be better than using XML-style namespaces
  286. # [10:36] <othermaciej> hsivonen: on the minus side... (a) reverse-DNS might be needlessly verbose compared to a registry system for prefixes; and (b) any system that decorates the name would be tempting to use for proprietary UA extensions but is totally unsuitable for such
  287. # [10:37] <othermaciej> (I say (b) because if a UA extension with a prefixey name becomes popular, then the spec may have to enshrine it with the funny name, thus violating the sanctity of the namespacing mechanism)
  288. # [10:37] <hsivonen> <com.netscape.blink>, <com.microsoft.marquee>
  289. # [10:37] <hsivonen> othermaciej: true, <com.apple.canvas> would have sucked big time
  290. # [10:37] <Hixie> com.netscape.table
  291. # [10:37] <Hixie> com.netscape.img
  292. # [10:38] <Hixie> actually com.mcom.img
  293. # [10:38] <othermaciej> that's different from CSS properties or APIs with a prefix, where it's somewhat practical to consider the possibility of multiple names
  294. # [10:38] <othermaciej> that might even be true for markup attributes
  295. # [10:38] <hsivonen> Hixie: were those purely unilateral or were there drafts for those under discussion at the time?
  296. # [10:38] <othermaciej> but not really for tag names
  297. # [10:38] <Hixie> hsivonen: img was unilateral, pretty sure table was too
  298. # [10:39] <hsivonen> Hixie: I thought <table> had a I-D going for it
  299. # [10:39] * Quits: mat_t (n=mattomas@91.189.88.12) ("This computer has gone to sleep")
  300. # [10:39] <Hixie> maybe
  301. # [10:39] <Hixie> <com.netscape.embed>
  302. # [10:40] <Hixie> <com.netscape.keygen>
  303. # [10:40] <hsivonen> Hixie: microdata and Namespaces have the same problem
  304. # [10:40] <hsivonen> anything that bakes a domain name in the identifier does
  305. # [10:40] * Joins: mat_t (n=mattomas@91.189.88.12)
  306. # [10:40] <Hixie> microdata's naming problem isn't set in stone yet and i doubt we'll use what's in the spec now
  307. # [10:40] <Hixie> not sure what we'll use
  308. # [10:41] <Hixie> btw, using reverse dns tag names for extending the vocabulary for small-scale use (the usual reason people want this) is even worse than the browser unilateral extensions
  309. # [10:41] <Hixie> because it means you have no fallback for non-supporting UAs
  310. # [10:41] <Hixie> which is why class="" and data-*="" are the right solution
  311. # [10:42] <Hixie> but i've said this lots of times already
  312. # [10:43] <hsivonen> maybe we should have an ext attribute that is like class except it's new so it's better
  313. # [10:43] <Hixie> we could call it role=""!
  314. # [10:43] * jgraham_ doesn't see how fallback is related to the use of reverse dns
  315. # [10:44] <Hixie> it's not
  316. # [10:44] <Hixie> any mechanism that affects the tag name part is equally bad
  317. # [10:45] <Hixie> the point is that <cite class="book"> is better than <ext:book> or <com.example.book> (or <book> before being in a spec)
  318. # [10:46] <jgraham_> Oh, I thought you were saying it was bad in microdata for some reason
  319. # [10:46] * Quits: fishd (n=darin@72.14.224.1) (Read error: 110 (Connection timed out))
  320. # [10:46] <Hixie> oh no the fallback issue is unrelated to the microdata issue
  321. # [10:47] <Hixie> the microdata issue is that we want to have property names that are short, but want to allow vocabulary mixing
  322. # [10:47] <hsivonen> Hixie: btw, what's happing with the viewport meta state? If both iPhone and Fennec support it, it's a bit pointless to pretend it's not conforming
  323. # [10:47] <Hixie> which basically means requiring a registry for each vocabulary
  324. # [10:47] * Joins: ROBOd (n=robod@89.122.216.38)
  325. # [10:47] <Hixie> hsivonen: i guess someone should add it to the registry
  326. # [10:48] <othermaciej> does Fennec do the same thing with it that iPhone does?
  327. # [10:48] <othermaciej> (I'm not actually sure offhand what MobileSafari does with it)
  328. # [10:49] <hsivonen> othermaciej: I'm not sure. I just assumed the idea is to do the right thing with content that's already authored with awareness of MobileSafari
  329. # [10:49] <Hixie> i think safari uses it to define the dimensions of the ICB or something like that
  330. # [10:49] <Philip`> The fallback thing indicates a need to lets documents declare subclass relationships between elements
  331. # [10:49] <Hixie> or to define the dimensions of the viewport, and then it uses something that isn't the viewport to render the page or something like that
  332. # [10:49] <hsivonen> Philip`: we could use RDF for that
  333. # [10:49] <Hixie> Philip`: we could use an attribute called "class" to indicate that
  334. # [10:49] <jgraham_> Philip`: Using RDF boondoggles perhaps?
  335. # [10:49] <Philip`> e.g. use @profile to point to a thing that says com.example.book is a subclass of cite
  336. # [10:50] <Hixie> ok, i was being serious, i dunno about you three
  337. # [10:50] <Hixie> :-P
  338. # [10:50] <Philip`> and once that extensibility mechanism is deployed, it'll be much easier to extend the language
  339. # [10:50] * Philip` is always serious
  340. # [10:50] <othermaciej> right, MobileSafari's zooming/panning is modeled as something other than scrolling, and thus it does not affect the CSS viewport
  341. # [10:51] * Joins: takoratta (n=takoratt@220.109.219.244)
  342. # [10:52] * Quits: webben (n=benh@dip5-fw.corp.ukl.yahoo.com) (Read error: 104 (Connection reset by peer))
  343. # [10:55] <Hixie> huh
  344. # [10:56] * annevk2 notices lots of emails with the word "summary" in his inbox
  345. # [10:56] <Hixie> Jeremy suggsts using <details> <dt> ... <dd> ... </details> instead of <details> <legend> ... </legend> ... </details>
  346. # [10:56] <Hixie> that's not a bad idea
  347. # [10:57] <othermaciej> it's an intriguing idea
  348. # [10:58] <othermaciej> big plus: avoids the <legend> parsing issue without adding elements
  349. # [10:58] <Hixie> yeah
  350. # [10:59] <annevk2> and gives you a separate container for the contents of <details> making styling easier
  351. # [11:00] <othermaciej> I was thinking the <dd> seems unnecessary, but that's a good point about styling
  352. # [11:00] <hsivonen> what about applying the pattern to <figure>, too?
  353. # [11:00] <othermaciej> then we'd have to rename <figure> to start with "d"
  354. # [11:00] <othermaciej> <diagram>?
  355. # [11:00] <annevk2> digure
  356. # [11:01] <hsivonen> <figure><dd><img ...></dd><dt>caption here</dt></figure>
  357. # [11:01] <Hixie> i really don't see why y'all are so worried about either <details> or <figure>, to be honest
  358. # [11:01] <hsivonen> othermaciej: I don't think it follows that figure needs renaming
  359. # [11:02] <annevk2> Hixie, I was somewhat convinced with the argument that if authors cannot use it for the next decade because of IE it's not really better than XHTML 2.0
  360. # [11:02] <annevk2> though not entirely
  361. # [11:02] <othermaciej> Hixie: I don't think waiting a decade for them to be usable is a good tradeoff for avoiding creation of new elements
  362. # [11:02] <hsivonen> Hixie: I think you should take the worry as demand data just like popular class names.
  363. # [11:02] <hsivonen> Hixie: also, what annevk2 said about XHTML2 applies
  364. # [11:03] <othermaciej> Hixie: it's even more not a good tradeoff for using one existing element with a somewhat semantically appropriate name vs. another with a slightly less on-point name
  365. # [11:03] <Hixie> i guess i don't understand the demand
  366. # [11:03] <Hixie> i mean, sure, they're neat and all
  367. # [11:03] <Hixie> but they don't add much
  368. # [11:04] <Philip`> Presumably the features exist in the spec because people want to use them, and so it's not surprising that people are unhappy when they find they can't use them
  369. # [11:04] <othermaciej> especially since <caption> and <label> are arguably both more semantically appropriate than <legend> but can't be used due to technical difficulties
  370. # [11:04] <hsivonen> Hixie: everyone who has had to develop containers for a floating img+caption pair wants a <figure> they can use yesterday
  371. # [11:05] <othermaciej> the Cocoa equivalent of <details> is used all over Mac OS X UI
  372. # [11:05] <othermaciej> it's a great component for a UI toolbox
  373. # [11:06] <Lachy> I liked the idea of using <details> with <dt> and <dd>, though I'm also concerned about the compatibility issues that would be caused if authors started using it now before browser implementations are ready
  374. # [11:06] <othermaciej> it would be hard for script to make one as polished as a native implementation
  375. # [11:06] <othermaciej> if <details> didn't use <legend> it would get some native browser implementations a lot sooner
  376. # [11:06] <Hixie> othermaciej: why?
  377. # [11:06] <Hixie> Lachy: yeah, that's actually an argument for keeping <legend>, as far as i can tell
  378. # [11:07] <othermaciej> Hixie: is the "why?" regarding my last statement?
  379. # [11:07] <Hixie> yeah
  380. # [11:07] <Hixie> seems like fixing the <legend> bugs is easy
  381. # [11:07] <Hixie> at least compared to the magic involved in <details>
  382. # [11:07] <Hixie> maybe not for <figure>
  383. # [11:07] <othermaciej> for Safari/WebKit development, we prioritize implementing features that Web developers can actually use, preferably before IE6 disappears from the market
  384. # [11:07] <Lachy> the functionality provided though, such as the hiding/showing, and the rendering of +/- expander controls could interfere with sites using it before implementations ship
  385. # [11:08] <Hixie> othermaciej: they won't be able to use <details> before then anyway
  386. # [11:08] <hsivonen> maybe making V.nu whine about <details> would be better than using <legend>
  387. # [11:08] <othermaciej> so it's basically not on our roadmap right now until the <legend> landscape changes (though we do intend to do something about <legend> parsing soonish)
  388. # [11:09] <othermaciej> Hixie: unless they do some script-based fallback for non-supporting UAs
  389. # [11:10] <othermaciej> it seems easier to fake <details> with script than <canvas>, and the latter has been done to some rough degree of quality
  390. # [11:11] <othermaciej> hsivonen: the <dt>/<dd> pattern even for containers that don't start with "d" is growing on me
  391. # [11:11] <othermaciej> it kind of makes sense to generalize them as a label/item pair for different contexts
  392. # [11:11] * and is now known as Guest31664
  393. # [11:12] <Hixie> i think i might add other <dx> elements to the parser even before we define such an element, btw
  394. # [11:12] <Hixie> to make future introduction of such an element easier
  395. # [11:12] <Hixie> especially if we start using <dt> everywhere
  396. # [11:12] <othermaciej> that seems wise
  397. # [11:13] <jgraham_> Faking <details> really isn't that hard, so there seems no reason not to use it now if it isn't broken at the parser level
  398. # [11:13] <Lachy> Hixie, what would <dx> mean?
  399. # [11:13] * Philip` finds the problem with dt/dd is remembering which order they go in
  400. # [11:13] <Hixie> Lachy: <ds> has been suggested for stage directions in <dialog>
  401. # [11:13] <Philip`> (At least I can understand it as term/definition for <dl>, but that wouldn't help in any other contexts)
  402. # [11:13] <Hixie> Lachy: dunno what other elements we might introduce, off-hand
  403. # [11:13] <hsivonen> Hixie: Instead of adding more stuff for <dialog>, <dialog> should go the way of <bb> and <datagrid>
  404. # [11:14] <jgraham_> I am more worried about the effect othermaciej mentioned (where implementors continually consider something low priority becuase IE doesn't support it) than the "authors might accidentially poison the well" argument
  405. # [11:14] <Hixie> hsivonen: yeah that's possible too
  406. # [11:14] <Hixie> hsivonen: but might still be useful to have some elements we can introduce later that already parse well
  407. # [11:15] <Lachy> Hixie, it makes no sense to try and maintain the fiction that <dl> can't be used for dialogues
  408. # [11:15] <Lachy> and thus keeping <dialog> is pointless
  409. # [11:15] <Hixie> <dl> definitely can't be used for dialogs
  410. # [11:15] <othermaciej> jgraham_: it's not just "IE doesn't support it" but "no obvious way to patch around old (or slow-to-implement) browsers"
  411. # [11:15] <Hixie> it makes absolutely no sense to use <dl> for dialogs
  412. # [11:16] <jgraham_> othermaciej: Yes, I was imprecise
  413. # [11:16] <Lachy> Hixie, why?
  414. # [11:16] <othermaciej> IE doesn't support <video> but it's still totally valuable given the fallback capabilities
  415. # [11:16] <othermaciej> Lachy: does anyone actually use <dl> for marking up conversations?
  416. # [11:17] <othermaciej> I am not aware of examples
  417. # [11:17] <Hixie> Lachy: it'd be like using <ol> for a postal address
  418. # [11:17] <Lachy> off hand, I can only think of the example in the HTML4 spec that used it
  419. # [11:17] <Hixie> Lachy: it superficially has a similar structure, but the semantic is no match at all
  420. # [11:17] <jgraham_> (it doesn't seem such a stretch to say that a conversation is a set of name-value groups where each name is the name and each value is the spoken text)
  421. # [11:18] <othermaciej> Lachy: if the HTML4 spec example is the only use, then it sounds like it would be a fiction to say it *can* be used for dialogs
  422. # [11:18] <Hixie> "doesn't seem such a stretch" is how we know it's not the right solution
  423. # [11:18] <Lachy> Hixie, dl is nothing but a general purpose assoication list. Pretending it has more semantics than that isn't helpful
  424. # [11:18] <Hixie> you wouldn't need to say that if it wasn't a stretch
  425. # [11:18] <Hixie> Lachy: a conversation is not an association list.
  426. # [11:18] * hsivonen wonders if semantics are a problem or a solution here
  427. # [11:18] <Lachy> othermaciej, in that case, I'd argue that basing the design of <dialog> on <dl> is bad design
  428. # [11:18] <jgraham_> Hixie: Not really. It is a "group of name-value data"
  429. # [11:19] <Lachy> Hixie, it associates a speaker with what they said
  430. # [11:19] <Philip`> Maybe someone should try to get actual data on how <dl> is used, rather than guessing
  431. # [11:19] <Hixie> jgraham_, Lachy: i really couldn't disagree more
  432. # [11:19] <othermaciej> I wouldn't use an association list to represent a conversation in the languages that support them
  433. # [11:20] <othermaciej> or any other form of map
  434. # [11:20] <Hixie> exactly
  435. # [11:20] <Philip`> othermaciej: In programming languages they're unordered and usually have unique keys, which is completely unlike <dl>
  436. # [11:20] <jgraham_> Hixie: I'm not arguing that I like it being used that way or anything. I'm just arguing that it is impossible to rule out from the current spec text
  437. # [11:20] <othermaciej> my understanding of <dl> is that as with <ul>, order is not important; only the name/value mapping is important
  438. # [11:20] <othermaciej> but in a conversation, the order is primary, and labels are secondary
  439. # [11:21] <Hixie> jgraham_: if you think a conversation is an "association list" or a "group of name-value data", then you need to get out more :-P
  440. # [11:21] <Lachy> Many people use cite and blockquote for conversations anyway
  441. # [11:21] <othermaciej> it would be easier to make sense of a conversation with only statements in order and no speaker labels, than to make sense of it with randomly ordered statements listed per speaker
  442. # [11:21] <Lachy> maybe we should just allow that
  443. # [11:22] <jgraham_> othermaciej: The spec says that order may be significant
  444. # [11:22] <Hixie> othermaciej: actually, <dl>'s order can be important -- e.g. some of the <dl>s in the spec are like switch statements
  445. # [11:22] <Philip`> othermaciej: That's just a matter of how you interpret the markup, which seems fundamentally different to association lists in programming languages where it's generally impossible to represent a meaningful order
  446. # [11:22] <othermaciej> but the opposite is true for an actual list of definitions
  447. # [11:22] <annevk2> othermaciej, note that Hixie often uses <dl>'s where the order is important
  448. # [11:22] <othermaciej> Philip`: Lisp has association lists which are in fact ordered (but where relying on the order is considered poor form)
  449. # [11:22] <Lachy> whether or not the order is relevant is entirely dependent on context. It can't be determined based on markup alone for a <dl>
  450. # [11:23] <othermaciej> I guess I am wrong about the philosophy of <dl> then
  451. # [11:23] <Philip`> (By "generally" what I mean is "in Perl and Python, because I don't know how they work in other languages" :-) )
  452. # [11:23] <jgraham_> Hixie: specifically I think of the transcription of a conversation as an ordered set of key-value pairs where each key is the speaker (and possibly the timestamp) and each value is waht they said at that point
  453. # [11:23] <othermaciej> I believe the term "association list" comes from Lisp
  454. # [11:24] <Philip`> I thought everything in Computer Science came from Lisp
  455. # [11:24] <othermaciej> Java also has an ordered hashtable type
  456. # [11:24] <jgraham_> javascript has ordered Objects (although the spec doesn't quite endorse this)
  457. # [11:24] <othermaciej> but name lookup is considered primary, and indexing secondary
  458. # [11:24] <Philip`> I presume all these things still require keys to be unique
  459. # [11:24] <Philip`> unlike <dl>
  460. # [11:24] <Hixie> jgraham_: i don't think that even describes an irc log, let along any conversation
  461. # [11:24] <othermaciej> C++ has multimap with non-unique keys
  462. # [11:24] <Hixie> jgraham_: actions, joins, parts, netsplits, etc.
  463. # [11:25] <othermaciej> but it doesn't have ordering
  464. # [11:25] <jgraham_> Hixie: Those aren't strictly part of the conversation
  465. # [11:25] * Quits: Lachy (n=Lachlan@85.196.122.246) ("This computer has gone to sleep")
  466. # [11:25] <othermaciej> in C++ STL data structures, you would represent a conversation as a vector<> of pair<>s of strings, not any associative type
  467. # [11:25] <Hixie> jgraham_: someone leaving the conversation is a pretty critical part of a conversation
  468. # [11:25] <othermaciej> likely also for any other programming language
  469. # [11:25] * Hixie thinks that this is part of the conversation too
  470. # [11:26] <jgraham_> Hixie: Arguably it is part of the context not part of the actual conversation.
  471. # [11:26] <Hixie> it's part of whatever we're marking up
  472. # [11:26] <othermaciej> the speaker's name is not a key, it's a label
  473. # [11:26] <othermaciej> that is an important difference in data structure terms
  474. # [11:26] <jgraham_> It is possible that there is no demand for marking up context-free conversations but <dialog> doesn't work any better here than <dl>
  475. # [11:26] <othermaciej> a key is something by which you index
  476. # [11:26] <othermaciej> but you'd never index a conversation by speaker
  477. # [11:26] <Philip`> othermaciej: Seems like you'd have to use a vector<> of pair<>s of strings to represent the content of any <dl> too
  478. # [11:27] <hsivonen> http://adactio.com/journal/1607/ is disturbing
  479. # [11:27] <Philip`> so you'd be treating conversations the same as <dl>s
  480. # [11:27] * jgraham_ notes that the spec uses "name" not "key"
  481. # [11:27] <othermaciej> are <dl> terms intended to be unique?
  482. # [11:27] <Hixie> jgraham_: <dialog> probably needs to go, yes
  483. # [11:27] <Hixie> othermaciej: the spec doesn't say so yet, but it probably should
  484. # [11:28] <jgraham_> Hixie: I think that is for the best
  485. # [11:28] <hsivonen> Hixie: so now empirical data shows that the definitions for section, article and details suck
  486. # [11:28] <Philip`> "I realise that it’s too small to be considered scientifically accurate" - not sure why he says that, since tens of data points are usually enough to be statistically significant
  487. # [11:29] * Joins: webben (n=benh@nat/yahoo/x-drazzxtcsvidxosa)
  488. # [11:29] <hsivonen> and curiously, hgroup seems to be the clearest of the lot
  489. # [11:29] <othermaciej> hsivonen: I would interpret the study as saying that the section, article and footer element names and/or definitions suck
  490. # [11:29] <hsivonen> othermaciej: fair enough
  491. # [11:29] <Hixie> i don't think the bits he quoted are necessarily the best bits to quote, but yeah, section vs article needs help, certainly
  492. # [11:29] <Hixie> someone mail me that url :-)
  493. # [11:30] <Philip`> Clearly the definitions should define themselves in terms of the name of the element, e.g. "<section> represents a section", and then people will find it harder to mix them up
  494. # [11:30] <annevk2> Hixie, at the end he says he'll post to the list
  495. # [11:30] <hsivonen> Hixie: mailed
  496. # [11:31] <othermaciej> given those quoted excerpts, I can see how people got <article> and <section> backwards
  497. # [11:31] <Hixie> thanks
  498. # [11:31] <Hixie> Philip`: yeah, that's kinda my point
  499. # [11:31] <jgraham_> The confusion between <article> and <section> seems to be the big takeaway from that
  500. # [11:31] * annevk2 wouldn't be opposed against merging them
  501. # [11:32] <hsivonen> the biggest takeaway is to avoid the word "section" in the definition of <article>
  502. # [11:32] <othermaciej> good point - I wonder if the reversal would have been as common if it said "a part of a page"
  503. # [11:32] <othermaciej> instead of "a section of a page"
  504. # [11:32] <jgraham_> I think maybe it would be OK to postpone <article> to HTML6 once we have an idea of how people are using <section>
  505. # [11:33] * Quits: boblet (n=boblet@p1254-ipbf304osakakita.osaka.ocn.ne.jp)
  506. # [11:33] <othermaciej> I bet it still would be though
  507. # [11:33] <jgraham_> since generally an <article> is-a <section>
  508. # [11:33] <Hixie> see, i think <article> is far more important than either <figure> or <details> :-)
  509. # [11:33] <webben> Maybe there needs to be a paragraph defining the difference between them.
  510. # [11:33] <webben> and the definition for each needs to refer back to that
  511. # [11:34] <hsivonen> Hixie: I think you have the importance of article and figure backwards
  512. # [11:35] <Hixie> i think you do :-)
  513. # [11:35] <othermaciej> I think the importance evaluation has to consider author desire to use the relevant element, and likelihood of using it correctly
  514. # [11:35] * jgraham_ wonders why Hixie thinks <article> is so important
  515. # [11:35] <othermaciej> it seems like both are higher for <figure> than <article>, regardless of their importance in the world of Platonic ideals
  516. # [11:35] * Hixie is changing <figure> and <details> to use <dt>/<dd>, and dropping <dialog>
  517. # [11:35] <hsivonen> woohoo!
  518. # [11:36] * othermaciej wonders whether Tantek will be delighted or infuriated by that change
  519. # [11:36] <Philip`> The way I see it is that <details> does something useful, and <article> is just a semantic way of saying <div class=article>, and it's fun to be anti-semantic
  520. # [11:36] <Hixie> also, i hate you all. this is far more work than it's worth. :-P
  521. # [11:36] * Joins: Lachy (n=Lachlan@pat-tdc.opera.com)
  522. # [11:36] <othermaciej> hi Lachy!
  523. # [11:36] * Joins: roc (n=roc@121-72-179-27.dsl.telstraclear.net)
  524. # [11:36] <Lachy> hi
  525. # [11:36] <jgraham_> :)
  526. # [11:37] <othermaciej> Lachy: may I prod you for an update on about: registration? any progress to report? should I push out the deadline?
  527. # [11:37] <Hixie> i think <article>/<section> are important because there's a key difference between a blog post and a section of a blog post, or a blog comment and a section on a web page
  528. # [11:37] <jgraham_> (as an aside the sparklines on that post work rather nicely)
  529. # [11:37] <Hixie> it's the difference between a chapter, and something that gets syndicated
  530. # [11:37] <othermaciej> jgraham_: I was also charmed by the sparklines
  531. # [11:37] <Lachy> othermaciej, the deadline was this thursday, wasn't it?
  532. # [11:38] <Philip`> jgraham_: I don't like how the sparklines ascribe significance to the arbitrary ordering of elements
  533. # [11:38] <othermaciej> Lachy: yes, it's this Thursday - just asking early
  534. # [11:38] <Lachy> I actually planned to look at that stuff today. I have a lot of feedback I need to send to Joseph about the latest draft
  535. # [11:39] <Philip`> It'd be less arbitrary if e.g. it ordered the values from highest to lowest in each sparkline
  536. # [11:39] <hsivonen> registering about: is more complex than I thought
  537. # [11:39] <othermaciej> Lachy: if you want to send an update by email, that's ok too, or I can ping you tomorrow, I was just assuming you probably wouldn't be at the telecon, so I wanted to make sure I'd have the data
  538. # [11:39] <Lachy> I'll make sure you have some info before the telcon
  539. # [11:39] * annevk2 finds a page that uses about:legacy-compat: http://xopus.com/
  540. # [11:39] * Joins: Kalms (n=rasmuska@81.161.185.108)
  541. # [11:40] <othermaciej> the potential flaw in the sparklines is that one could be really sharp and spikey while indicating 100% wrongness
  542. # [11:40] <Philip`> Hixie: That difference already seems clear enough in practice, because the something that gets syndicated is the something in the RSS feed
  543. # [11:41] * Quits: Kalms (n=rasmuska@81.161.185.108) (Client Quit)
  544. # [11:41] <othermaciej> <article>/<section> make sense in the case of a blog but get kind of confusing (with respect to each other and possibly with respect to <div>) in other contexts
  545. # [11:41] <Hixie> othermaciej: yeah the right sparkline type for that data would be a series of red/black blocks (red for good answers, black for bad ones), or something like that
  546. # [11:42] <jgraham_> I guess dropping <article> makes the syndication-from-the-html thing harder
  547. # [11:42] <Hixie> <article>/<section> also make clear sense in a forum, on a site like iGoogle, on anything with a clear body of content like an eBay page, etc.
  548. # [11:43] <jgraham_> Hixie: I agree that there is a difference and to me it is clear. I am concerned that it is not clear enough to everyone else
  549. # [11:43] <webben> Hixie: I think recognizing messages as articles may be confusing for people actually.
  550. # [11:43] <othermaciej> I don't know how to use <article>/<section> in the context of apps, even though the spec says they can be used for that
  551. # [11:44] <Lachy> jgraham_, from the uses of <article> that I've seen, people seem to be getting it right. The only issue has been the misuse of <section> as a wrapper within articles
  552. # [11:44] <othermaciej> I admit I am a bit puzzled by the apparent confusing over <article>/<section> in the context of documents
  553. # [11:45] <othermaciej> eBay is appy enough that I wouldn't be sure how to apply article/section
  554. # [11:45] <webben> you can't use section to wrap sections inside articles?
  555. # [11:46] <jgraham_> webben: You can
  556. # [11:46] <jgraham_> If they are true subsections of the article
  557. # [11:46] <webben> Okay. (Good.)
  558. # [11:47] <Lachy> webben, yes, but people have been doing <article><header/><section/><footer/></article> where the section is nothing but a wrapper around the content
  559. # [11:47] <webben> ah I see.
  560. # [11:49] <Hixie> there are an UNGODLY number of <figure> examples in the spec
  561. # [11:49] <Hixie> not surprising everyone wants to use it
  562. # [11:49] <Hixie> i should put this many <menu> examples in
  563. # [11:49] * jgraham_ wonders in which religions god has an opinion on the HTML5 spec
  564. # [11:52] <Lachy> jgraham_, that would be the god in Bible5
  565. # [11:53] <jgraham_> I'm pretty sure Bible5 has no God on the basis of lack of scientific evidince for His existance
  566. # [11:54] * annevk2 isn't really sure about <menu> 'cause of hyatt's multiple "rants" about it
  567. # [11:54] <Philip`> Shouldn't it equally have a God on the basis of lack of scientific evidence for His non-existence?
  568. # [11:54] <Philip`> Pave the cowpaths, and all that
  569. # [11:55] <Hixie> that doesn't scale
  570. # [11:55] <Lachy> Philip`, no
  571. # [11:55] <Hixie> and the cowpaths are contradictory
  572. # [11:55] <Hixie> also, specs should be written based on reality, not on previous specs (like the christian bible, in this case)
  573. # [11:55] <othermaciej> whether or not there is evidence for God, a lot of people are using him
  574. # [11:55] <Philip`> God is like xmlns
  575. # [11:55] <Philip`> Better to just accept him and carry on
  576. # [11:57] <annevk2> and make it a useless talisman in the process?
  577. # [11:57] <othermaciej> God is like violence. If he doesn't solve your problem, you're not using enough of him.
  578. # [11:57] <Lachy> haha
  579. # [11:57] <Philip`> annevk2: Sure, if it's enough to keep people happy
  580. # [11:58] * Joins: erlehmann (n=erlehman@tmo-109-179.customers.d1-online.com)
  581. # [11:59] <Lachy> the problems only start when people try to force their talismans upon others and attack others for rejecting it.
  582. # [12:00] * Quits: lazni (n=lazni@123.16.249.115) ("Leaving.")
  583. # [12:03] <othermaciej> if only all you Tagsoupists converted to the true path of Slashianity, we wouldn't have this problem
  584. # [12:04] <Philip`> I'm sure we'd find something else to fight over instead
  585. # [12:04] * Joins: takoratt_ (n=takoratt@220.109.219.244)
  586. # [12:04] * Joins: Perceptes (n=Percepte@cpe-76-88-38-155.san.res.rr.com)
  587. # [12:04] <Perceptes> anyone around?
  588. # [12:05] <Philip`> Perceptes: Maybe
  589. # [12:05] * Perceptes laughs.
  590. # [12:06] <Philip`> (It depends on whether you ask something that anyone feels like responding to)
  591. # [12:06] <Perceptes> I was hoping for some info on HTML 5 in IE. I ran into an issue I can't find any reference to on the web though it seems like it would be common.
  592. # [12:06] <Philip`> What issue is that?
  593. # [12:07] <Perceptes> I'm using Remy Sharp's html5shiv script, but when I insert HTML5 elements into the page later with jQuery, the elements are not styled. If I look at the newly inserted HTML in IE 8's built in developer toolbar, I can see that it's not correctly nesting the elements - it sees the opening and closing tags of each HTML5 element as two separate tags.
  594. # [12:08] <Philip`> I assume that's the http://code.google.com/p/html5shiv/source/browse/trunk/html5.js script?
  595. # [12:09] <Perceptes> that's the one.
  596. # [12:09] <Philip`> What elements are you using it with?
  597. # [12:09] <Perceptes> The ones that are being inserted and not styled are article, header, section, and time.
  598. # [12:09] <Perceptes> the latter three being children of a single article element.
  599. # [12:09] <jgraham_> Do you make sure the script runs before loading jQuery?
  600. # [12:10] <Perceptes> Yes, it's loaded before all other JS and CSS files.
  601. # [12:10] <Philip`> (That probably shouldn't matter, as long as the script runs before the parser reaches the new elements)
  602. # [12:11] <Perceptes> It only happens when injecting HTML5 elements with JS though, everything is styled correctly on initial page load, so I know the shiv script is working.
  603. # [12:11] <jgraham_> (Right but jQuery could be doing some clever caching or something so it seems worth checking)
  604. # [12:12] <Philip`> Oh, okay, I missed that you said they were inserted later
  605. # [12:12] <annevk2> might help if you show the page
  606. # [12:13] <Philip`> I expect inserting elements with createElement/appendChild should work, and inserting with innerHTML probably ought to work too (though I'm not sure), but I have no idea how jQuery tries to insert elements
  607. # [12:13] <Perceptes> it's not on a live server
  608. # [12:13] <jgraham_> Perceptes: If you take jQuery out of the loop, does it work if you do something like <script>document.body.innerHTML = "<section style='background-color:green;'>I should be a child of the section</section>"</script>
  609. # [12:14] <Perceptes> lemme try
  610. # [12:15] <Perceptes> yeah, that works
  611. # [12:16] <Perceptes> so either jQuery is the culprit or just the way I'm doing it isn't right.
  612. # [12:16] <jgraham_> Perceptes: can you make a minimal testcase that fails?
  613. # [12:17] <Perceptes> I'll see what I can come up with
  614. # [12:18] * Quits: zalan (n=zalan@catv-89-135-144-193.catv.broadband.hu) (Read error: 110 (Connection timed out))
  615. # [12:19] * Philip` has had problems with things like jQuery selectors on new elements (<time> etc) in Opera
  616. # [12:20] <jgraham_> Philip`: Did you file a bug?
  617. # [12:20] <Philip`> Actually, maybe the problem was with doing node.is('time')
  618. # [12:20] <Philip`> so I replaced it with node[0].localName.toLowerCase() == 'time'
  619. # [12:21] <Philip`> jgraham_: No, I just hacked around the problem so I could get on with what I wanted to be working on
  620. # [12:21] <jgraham_> Philip`: Do you mind filing a bug?
  621. # [12:21] <Philip`> Oh, actually, node.is is jQuery selectors, I think
  622. # [12:21] <Philip`> jgraham_: Filing a bug on whom?
  623. # [12:22] <Philip`> Anyway, the answer is that I do mind a bit and probably wouldn't get around to doing it today
  624. # [12:22] <jgraham_> Opera I guess, if it works in other browsers. We can always file a bug on jQuery if they are doing something strage
  625. # [12:22] <jgraham_> Philip`: OK
  626. # [12:22] * Joins: zalan (n=zalan@catv-89-135-144-193.catv.broadband.hu)
  627. # [12:23] * Joins: Creap (n=Creap@vemod.brg.sgsnet.se)
  628. # [12:23] <Philip`> Filing bugs takes far more effort than just complaining on IRC
  629. # [12:23] * Quits: takoratta (n=takoratt@220.109.219.244) (Read error: 110 (Connection timed out))
  630. # [12:23] <annevk2> Opera does casing different between unknown and known elements
  631. # [12:23] * Philip` isn't sure if the last Opera bug he filed was even CC'd to anyone who will actually be interested in looking at it and getting it fixed
  632. # [12:24] * Quits: takoratt_ (n=takoratt@220.109.219.244) (Read error: 110 (Connection timed out))
  633. # [12:24] <annevk2> what's your account? i can take a loop
  634. # [12:25] <Philip`> Hmm, I think the bug I'm thinking of was DSK-256463
  635. # [12:25] <Philip`> but I don't know if it's still a bug in the latest version, and I can't test it since I don't have KDE3 any more
  636. # [12:29] <annevk2> oh, I cannot be of much help with that I'm afraid
  637. # [12:41] * Joins: boblet (n=boblet@p1254-ipbf304osakakita.osaka.ocn.ne.jp)
  638. # [12:42] * Quits: erlehmann (n=erlehman@tmo-109-179.customers.d1-online.com) (Read error: 113 (No route to host))
  639. # [12:51] <Hixie> i now have a 3000 line diff
  640. # [12:51] <Hixie> that:
  641. # [12:51] <Hixie> drops <dialog>
  642. # [12:52] <Hixie> makes <figure> amd <details> use <dt>/<dd> instead of <legend>
  643. # [12:52] <Hixie> moves the stuff about tag clouds and footnotes into a section that also has something about conversations
  644. # [12:52] <Hixie> adds <dc> and <ds> to the parser speculatively for future expansion
  645. # [12:54] <Lachy> Hixie, what is <dc> reserved for?
  646. # [12:54] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  647. # [12:54] <Hixie> credits in <figure>
  648. # [12:55] <Hixie> i'll do a separate patch to move <legend> and <div> into other sections, since this is big enough alreayd
  649. # [12:55] <annevk42> sounds pretty good
  650. # [12:56] <annevk42> Hixie, you should add Jeremy Keith to the ack section too
  651. # [12:56] <Hixie> i recommend <p><b>speaker</b>: text</p> for conversations
  652. # [12:57] <Hixie> annevk42: thanks
  653. # [12:57] <Hixie> done
  654. # [12:58] <Perceptes> alright, I have a test case on the net if anyone I was talking to a few minutes ago is still on.
  655. # [13:00] * Joins: erlehmann (n=erlehman@tmo-109-179.customers.d1-online.com)
  656. # [13:00] <Philip`> Perceptes: It's probably best to just post the link in any case, because someone else might look at it or one of the people you were originally talking to might come back in a few hours and read the logs and see it :-)
  657. # [13:00] <othermaciej> this is interesting: http://www.techcrunch.com/2009/09/14/tc50-fluidhtml-wants-to-rewrite-the-web-with-flash-like-html/
  658. # [13:00] * Philip` is currently not here
  659. # [13:01] <annevk42> Hixie, in <details>' content model dd is not marked up with <code>
  660. # [13:01] <Hixie> fixed, thanks
  661. # [13:01] <Perceptes> well ok then! http://www.jimmycuadra.com/ie8/ is the link. I stubbed out the ajax, so just click the add comment button and it will insert a canned comment. try it in non-IE first so you see what it's supposed to do. the script it runs is at http://www.jimmycuadra.com/ie8/javascripts/comments.js and I added a comment in it that shows specifics on where it's breaking.
  662. # [13:05] <Perceptes> hmm, is time not supposed to be a block level element?
  663. # [13:05] <Hixie> nah it's phrasing-level
  664. # [13:05] <Perceptes> ok, that's something I need to fix then
  665. # [13:06] <Perceptes> not related to the issue above though
  666. # [13:06] <jgraham_> Perceptes: I don't really understand what your demo is supposed to do. I was really hoping for something like 5-10 lines long that printed "PASS" or "FAIL" as appropriate
  667. # [13:08] <Perceptes> jgraham_: it does three things: 1) adds a "1 comment" link to the bottom left corner of the blog entry 2) adds a section called "comments" above the comment form 3) adds the canned comment (in the real situation it's the comment you enter, obviously) to that new comments section
  668. # [13:09] * jgraham_ will spend a few moments trying to reduce it further
  669. # [13:09] <jgraham_> (but not very many)
  670. # [13:09] <Perceptes> the part that's failing is that in step 2, it's inserting a section element which IE doesn't seem to parse correctly, so when the script tries to insert the comment into it, it throws an error
  671. # [13:10] <Perceptes> if I use a div instead of a section, then it inserts fine
  672. # [13:10] <jgraham_> Yeah, I see the failing code
  673. # [13:10] <Perceptes> but the comment itself (which uses article, header, and section) doesn't style
  674. # [13:10] <Perceptes> ok
  675. # [13:10] <Perceptes> I'll work on a version with all the stuff not specific to the failure stripped out
  676. # [13:12] * Joins: zcorpan (n=zcorpan@pat.se.opera.com)
  677. # [13:12] <Hixie> oh i also made <dl> say that <dt> should be unique
  678. # [13:13] <Hixie> forgot to mention that in the checkin comment
  679. # [13:13] <Hixie> (it's just a "should")
  680. # [13:13] <zcorpan> Philip`: personally, i'd like related things to be on the same page in the multipage version. in particular i'd like video, audio and media elements to be in one page
  681. # [13:14] <annevk42> Hixie, for <dd> in contexts where it can be used you are specific for <dl> but not for the other two; i.e. for <figure> it can appear only once and for <details> it can appear only once, but only after a <dt>
  682. # [13:15] <zcorpan> Philip`: since e.g. things that invoke the resource selection algorithm is all over the place, it's nice to be able to search within the page
  683. # [13:15] <Hixie> annevk42: good point
  684. # [13:15] <hsivonen> Philip`: it would be great to have a static copy of the parser section stored somewhere immediately before you split the tokenization and tree building sections again
  685. # [13:15] <Perceptes> jgraham_: refresh for a super simplified HTML page
  686. # [13:15] <hsivonen> Philip`: if lynx --dump rewraps the lines, I'm in the world of hurt again
  687. # [13:16] <hsivonen> otherwise, I like having tokenization and tree building on separate pages in the multipage version
  688. # [13:16] * hsivonen depends on lynx --dump for diffing those sections
  689. # [13:19] * Joins: adactio (n=adactio@host86-138-101-27.range86-138.btcentralplus.com)
  690. # [13:23] * Joins: jrib (n=jrib@upstream/dev/jrib)
  691. # [13:24] <Lachy> Hixie, in the footnotes example, why don't you use <sup> to make the footnote references superscripts, as they usually are in printed typography
  692. # [13:24] <Hixie> i was doing what wikipedia does
  693. # [13:24] <Hixie> but yeah, we could do that
  694. # [13:24] <Hixie> still with square brackets?
  695. # [13:24] <Lachy> wikipedia also uses <sup>
  696. # [13:24] <jrib> Hey, is there a reason html5lib/treebuilders/__init__.py and _base.py contain print statements? Is this just for debugging purposes during development?
  697. # [13:24] <Hixie> oh, i didn't notice
  698. # [13:24] <Hixie> ok cool, will do
  699. # [13:25] <jrib> (this is in python3)
  700. # [13:25] <Hixie> Lachy: reload in 25 seconds; is that better?
  701. # [13:26] <Lachy> the square brackets are just a wikipedia convention. i'm not sure of the reason behind it. It may be just to make the links slightly larger and easier to click. I've never seen them used in printed typography.
  702. # [13:27] <Hixie> i guess we're a new medium, we get to make our own conventions
  703. # [13:27] * Joins: remysharp (n=remyshar@remysharp.plus.com)
  704. # [13:28] <zcorpan> Hixie: ugh. why change the parser before actually adding new elements?
  705. # [13:28] <Hixie> so that we can add them with significantly less pain in the future
  706. # [13:28] <Hixie> consider how easier our life would be if <legend> was parsed correctly today
  707. # [13:29] <zcorpan> if <legend> was treated as an unknown element, it would be fine
  708. # [13:29] <Lachy> Hixie, put the <a> within the <sup>, rather than the other way around
  709. # [13:29] <Hixie> Lachy: oh, yeah, underlining, oops
  710. # [13:29] <Lachy> see http://software.hixie.ch/utilities/js/live-dom-viewer/saved/231 for why
  711. # [13:29] <Lachy> yeah
  712. # [13:29] <jgraham_> Perceptes: http://hoppipolla.co.uk/410/IE_jQuery.html
  713. # [13:30] <remysharp> On the legend note Hixie - can you clarify the "use dt/dd" comment here: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7374 - is that in place of figure/details or in place of using legend?
  714. # [13:30] <Creap> http://html5.org/tools/web-apps-tracker?from=3858&to=3859 are dc/ds short for something, a typo or something I've never heard about
  715. # [13:30] <Hixie> zcorpan: ok, consider how much easier our life would be if <figure> had been a block-level element in the past
  716. # [13:30] <annevk42> Creap, they're speculative future extensions
  717. # [13:30] <Hixie> remysharp: <dt> replaces <legend> in <figure> and <details>; see the updated examples in the spec
  718. # [13:30] <remysharp> Hixie: ta.
  719. # [13:30] <Creap> ok
  720. # [13:31] <Hixie> Creap: <dc> for credits, probably, <ds> maybe for stage directions. Both are not really elements yet.
  721. # [13:31] <Hixie> Creap: (not sure how much of a good idea it is to add them before we know if we need them)
  722. # [13:31] <Hixie> Creap: (so they might not stay)
  723. # [13:31] <Perceptes> jgraham_: wow, even more stripped down then what I'm doing. D: Thank you!
  724. # [13:31] * hsivonen is uneasy about <ds> and <dc> without an articulated reason
  725. # [13:31] <jgraham_> jrib: Sounds like debugging
  726. # [13:32] <annevk42> Hixie, shouldn't the <details> binding only work with <dd>?
  727. # [13:32] <Hixie> hsivonen: the articulated reason is that in the future, we will probably want <figure> <dt>legend <dc>credit <dd><img ...> </figure>
  728. # [13:32] <zcorpan> Hixie: it would make things harder if we found out that the use cases for <figure> demand it to be an inline element in the parser
  729. # [13:32] <jrib> jgraham_: yeah, I'll just comment them out I guess...
  730. # [13:32] <annevk42> Hixie, would be nice to be able to implement it as just a display switch
  731. # [13:33] <jrib> jgraham_: thanks
  732. # [13:33] <annevk42> Hixie, also a lot easier for script implementations
  733. # [13:33] <Hixie> annevk42: not sure what you mean
  734. # [13:33] <annevk42> Hixie, currently everything besides <dt> has to be hidden and displayed, rather than just the last child <dd>
  735. # [13:33] <Hixie> zcorpan: yeah, dunno
  736. # [13:33] <annevk42> (the concern is mostly about invalid docs)
  737. # [13:34] <annevk42> s/mostly//
  738. # [13:34] <Hixie> annevk42: oh, you want the rendering aspect changed more. i see.
  739. # [13:34] <Hixie> annevk42: yeah, i guess we could do that.
  740. # [13:34] <jgraham_> jrib: You are the only person known to be using the Python3 html5lib treebuilder
  741. # [13:34] <jrib> jgraham_: heh :)
  742. # [13:34] * annevk42 wonders when Python3 will be more mainstream
  743. # [13:35] <jrib> I write my personal scripts in python3
  744. # [13:35] <jgraham_> So you are basically welcome to do what you want with it. If you end up with patches you want to commit we can sort something out
  745. # [13:36] <jgraham_> (like you can have access to the Google code project or I can poull from your repo or whatever)
  746. # [13:36] * Joins: da3d (n=opera@h11n1fls34o986.telia.com)
  747. # [13:37] * jgraham_ remembers he was going to the shop some time ago
  748. # [13:38] <jgraham_> Perceptes: It looks like jQuery does something rather complex for DOM operations so it's not trivially obvious where the issue lies
  749. # [13:38] <zcorpan> hmm, writing tests for the resource selection algorithm is no fun
  750. # [13:38] <zcorpan> all my tests pass
  751. # [13:38] <Perceptes> jgraham_: I was afraid of that :|
  752. # [13:39] <zcorpan> darn philipj being so pedantic in following the spec
  753. # [13:39] <hsivonen> Perceptes: are you setting display: block; on the new structural elements?
  754. # [13:39] <Perceptes> yes, I'm using the html5 reset css from here: http://code.google.com/p/html5resetcss/downloads/list
  755. # [13:40] <Perceptes> ^ hsivonen
  756. # [13:41] <hsivonen> Perceptes: ok. that's not the problem then
  757. # [13:42] <Perceptes> I updated http://www.jimmycuadra.com/ie8/ with a full description of what's happening and a link to a copy of jgraham_'s page
  758. # [13:43] <Perceptes> anyway, it seems like this might be an issue for the jquery devs
  759. # [13:44] <annevk42> what's up with "HTMLWG WG"?
  760. # [13:48] * Quits: remysharp (n=remyshar@remysharp.plus.com) ("Gotta shoot - "peeyaow"")
  761. # [14:00] * Quits: nessy (n=nessy@203-214-137-48.perm.iinet.net.au) (Read error: 60 (Operation timed out))
  762. # [14:02] * Joins: nessy (n=nessy@124-170-13-58.dyn.iinet.net.au)
  763. # [14:02] <Lachy> annevk42, that's the working group that is working on the working group
  764. # [14:03] <Lachy> :-)
  765. # [14:03] <Hixie> is that another name for the html4all group? :-)
  766. # [14:03] <Lachy> maybe it's another name for the HTML-CG
  767. # [14:07] <annevk42> it's what everyone seems to be using when cc'ing the HTML WG list
  768. # [14:07] <annevk42> or at least a few people
  769. # [14:08] <Lachy> I haven't noticed it
  770. # [14:11] <annevk42> see e.g. http://lists.w3.org/Archives/Public/public-html/2009Sep/0567.html
  771. # [14:11] <annevk42> or http://lists.w3.org/Archives/Public/public-html/2009Sep/0550.html
  772. # [14:12] <annevk42> or http://lists.w3.org/Archives/Public/public-html/2009Sep/0537.html
  773. # [14:12] <annevk42> etc.
  774. # [14:14] <Lachy> oh, interesting. My mail client just displays "public-html" because that's what I have in my address book.
  775. # [14:14] <beowulf> it's for those working on HTML5 5
  776. # [14:16] <Philip`> zcorpan: Hmm, the video page is pretty small so I suppose it could be merged with media-elements without causing extreme pain to people who asked for small pages
  777. # [14:16] * Philip` updates his script; will upload some time later
  778. # [14:17] * Quits: erikvvold (n=erikvvol@96.49.192.204)
  779. # [14:17] <zcorpan> Philip`: thanks
  780. # [14:18] <Philip`> hsivonen: I don't trivially have a copy of the parser section - I don't extract that section and then split it up further, I just split the original source document into a series of chunks
  781. # [14:18] <hsivonen> Philip`: is there a pre-splitter change and post-splitter change archive of the entire multipage spec
  782. # [14:18] <hsivonen> ?
  783. # [14:20] <annevk42> there might be one on dev.w3.org
  784. # [14:20] <annevk42> see http://dev.w3.org/cvsweb/html5/spec/
  785. # [14:21] <Philip`> hsivonen: (so it's probably just as easy to extract that section using a simple regexp script, like perl -lne'print if /<h3 id=parsing>/../<h3 id=(?!parsing)/' index)
  786. # [14:21] <hsivonen> Philip`: oh so the splitting of the parsing section isn't changing?
  787. # [14:22] <Philip`> hsivonen: Hmm, I may be misunderstanding what you want
  788. # [14:23] <hsivonen> Philip`: if/when the lynx line wrapping of the parsing section is at risk of changing, I'd like to have reference files before and after the line wrap change
  789. # [14:23] <hsivonen> if there's no wrapping change happening this time, no problem
  790. # [14:24] <Philip`> hsivonen: The split pages that contain the parsing stuff will be different to what they were a few days ago - originally the tokeniser/tree-constructor/etc were separate pages, then <div class=impl> was added and they all became a single page, and recently the spec-splitter was updated so it will split them into separate pages again
  791. # [14:24] <Philip`> hsivonen: I don't think the splitter will change any wrapping ever - it's just copied from the source document (and parsed and serialised but not otherwise altered)
  792. # [14:24] <hsivonen> Philip`: ok.
  793. # [14:24] <Philip`> s/it's/the content of each page is/
  794. # [14:25] <hsivonen> Philip`: at least once Hixie has done something that changed nesting depth of the paragraphs or somethnig
  795. # [14:25] <Philip`> It sounds like he must have edited the source document
  796. # [14:25] <Philip`> so I think I'm innocent of any involvement in that
  797. # [14:27] <Philip`> "why change the parser before actually adding new elements?" - it provides a way to avoid naming debates - there's no need to debate now because we're not actually adding any new elements with new names, and later we'll be forced to use the only names that are parsed correctly so there's no point debating then either
  798. # [14:28] <hsivonen> Philip`: excellent point!
  799. # [14:29] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Remote closed the connection)
  800. # [14:30] <Hixie> that's a pretty awesome reason
  801. # [14:30] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  802. # [14:30] <Hixie> ok, it's about 4 hours past my bed time
  803. # [14:30] <Hixie> and about 2 hours past my backup bed time
  804. # [14:30] <Hixie> so nn!
  805. # [14:31] <Philip`> hsivonen: (By the way, if you did want the old splitter output then the script is in SVN and should be relatively easily executable if you've got html5lib and lxml installed)
  806. # [14:31] <hsivonen> Philip`: ok. (I have neither)
  807. # [14:31] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Remote closed the connection)
  808. # [14:31] <Philip`> hsivonen: (but I'll assume for now that you don't need it, since hopefully nothing changed except the divisions between pages)
  809. # [14:31] <hsivonen> ok
  810. # [14:31] * Joins: pmuellr (n=pmuellr@nat/ibm/x-opunbrvlxwioqslx)
  811. # [14:31] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  812. # [14:32] * annevk42 sort of suspects someone to make an issue about this now
  813. # [14:32] <Philip`> Also by the way, I don't suppose anyone knows why suspend-to-RAM on my laptop only successfully resumes if I have active disk activity (e.g. md5summing a large file) before I run the suspend command?
  814. # [14:33] <takkaria> what are ds and dc meant to be for?
  815. # [14:33] * Joins: BlurstOfTimes (n=blurstof@168.203.117.59)
  816. # [14:33] * Philip` wants a <psp> element
  817. # [14:34] * jgraham_ wants a <wii> element
  818. # [14:34] * Joins: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley)
  819. # [14:34] <takkaria> <ny>?
  820. # [14:35] * Quits: Perceptes (n=Percepte@cpe-76-88-38-155.san.res.rr.com) ("Leaving.")
  821. # [14:37] * Philip` wants a <360> element too, but is scuppered by XML's NCName requirements
  822. # [14:37] <Lachy> Philip`, what's what with <xbox> ?
  823. # [14:37] <Lachy> <xbox type="360"> should work for you
  824. # [14:38] <Lachy> takkaria, what's <ny>?
  825. # [14:38] <Lachy> New York?
  826. # [14:38] * murr4y` is now known as murr4y
  827. # [14:39] <Philip`> Lachy: That suggests much more similarity between the types than there really is
  828. # [14:39] <takkaria> yeah, I was going off DC being Washington, District of Colombia
  829. # [14:39] <Lachy> oh
  830. # [14:39] <takkaria> screw all these, we need <gamesconsole type="xbox" model="360">
  831. # [14:39] <takkaria> that's more extensible anyway
  832. # [14:40] <annevk42> might as well use <object> then
  833. # [14:40] <takkaria> + RDFa
  834. # [14:40] <annevk42> now you have two problems
  835. # [14:40] <takkaria> let's use Perl and regexes, then we have four
  836. # [14:41] <Philip`> takkaria: That's nowhere near enough attributes
  837. # [14:41] <Lachy> Philip`, wasn't the XBox 360 just the 2nd generation of XBox, much like the PS2 was the second generation PlayStation?
  838. # [14:41] <Philip`> Got to specify the type (Pro/Elite/etc), and disk size, and the code-name of the internal electronics
  839. # [14:42] <Lachy> oh. that's complicated.
  840. # [14:42] * Lachy goes back to playing with his <gameboy>
  841. # [14:43] <Philip`> Lachy: It's totally new hardware with completely different CPU (Intel vs IBM) and completely different GPU (NVIDIA vs ATI)
  842. # [14:43] <Philip`> It's only backward-compatible through software emulation, I think
  843. # [14:44] <Philip`> I guess the OS and development tools are similar but greatly updated
  844. # [14:45] <Philip`> It's the second use of the brand name, but that's not really interesting - in most ways it's just an independent new thing
  845. # [14:45] <Lachy> right. So it's much more like the change from the Nintendo Control Deck to Super Nintendo (although they weren't compatible at all)
  846. # [14:46] <Philip`> (I expect PS->PS2 and PS2->PS3 are similar, in that they're totally new devices designed from scratch, rather than being updates of a previous version)
  847. # [14:47] <Philip`> (whereas GameCube->Wii is a much more basic hardware upgrade, just adding faster CPU and more RAM etc)
  848. # [14:47] <da3d> Philip`: We need to specify region too. A european 60GB PS3 is different from a north american 60GB PS3...
  849. # [14:48] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Read error: 110 (Connection timed out))
  850. # [14:48] <Lachy> Was the GameCube the one that came after the N64?
  851. # [14:48] <da3d> yes
  852. # [14:48] <Lachy> did the GameCube use CDs or cartridges for the games?
  853. # [14:49] <da3d> It used 1.5GB 8cm sorta-DVDs...
  854. # [14:49] <annevk42> small CDs
  855. # [14:49] <Lachy> oh
  856. # [14:51] <Philip`> da3d: I suppose that matters when someone queries the air-speed velocity of an unladen PS3
  857. # [14:52] * Lachy is so out of date when it comes to game consoles
  858. # [14:52] <takkaria> Philip`: it also matters for NTSC vs PAL, I imagine
  859. # [14:54] <Philip`> Wouldn't the hardware just support both?
  860. # [14:54] <Philip`> (as well as VGA and HDMI and whatever else)
  861. # [14:54] * Philip` presumes it matters more for region-locking of games
  862. # [14:55] * jgraham_ makles the rather obvious point that the change in input hardware from gamecube to wii is much more significant to the end user than the change in the internals
  863. # [14:56] <annevk42> the only problem with the Wii is the lack of non-casual-gamer games
  864. # [14:57] <Philip`> jgraham_: Indeed, but in terms of 'generations' it's just an incremental feature addition rather than a fundamental redesign
  865. # [14:57] <annevk42> stuff like GTA, Gears of War, etc.
  866. # [14:57] <annevk42> well, I guess there's Zelda and Mario Galaxy, but still
  867. # [14:57] <da3d> Old consoles actually had slightly different hardware in different regions, eg SNES had slightly different cpu clock rates for europe...
  868. # [14:58] * jgraham_ should play more Zelda and Mario Galaxy
  869. # [14:58] <Philip`> GTA/GoW vs Zelda/Mario is quite a difference in tone
  870. # [14:58] <Philip`> da3d: Was that for NTSC vs PAL synchronisation?
  871. # [14:58] * Parts: zcorpan (n=zcorpan@pat.se.opera.com)
  872. # [14:59] <annevk42> Philip`, they're similar in depth
  873. # [14:59] <da3d> Philip`: Not sure, probably. PAL consoles were horribly gimped back then anyway.
  874. # [14:59] <Philip`> (which seems less of an issue now there's so much variation in resolutions that you can't get precise synchronisation guarantees anyway, I guess)
  875. # [15:00] <da3d> I suppose it's mostly firmware differences these days, with a few exceptions (like certain PS3 models).
  876. # [15:01] <Philip`> annevk42: Depth similarities don't really help when you're in a mood for driving large trucks over grannies but you're not allowed to do anything but jump on mushrooms
  877. # [15:01] * Joins: ttepasse (n=ttepas--@p5B0159FC.dip.t-dialin.net)
  878. # [15:03] <beowulf> the links in Smylers lastest email don't work for me
  879. # [15:03] <beowulf> http://www.whatwg.org/html5#the-blockquote-element
  880. # [15:03] <beowulf> just goes to the multipage doc
  881. # [15:04] <Philip`> beowulf: Works for me
  882. # [15:04] <Philip`> beowulf: You don't have scripting disabled or anything?
  883. # [15:04] <beowulf> Philip`: no, JS is enabled, Smylers suggested that too
  884. # [15:04] <beowulf> I'm using Safari 4.0.3
  885. # [15:05] * beowulf investigates what else he may be doing that's stupid
  886. # [15:05] * Philip` is unable to test in that
  887. # [15:05] <Philip`> (link-fixup.js ought to be redirecting you)
  888. # [15:06] <beowulf> no errors in the console...
  889. # [15:06] <jgraham_> Philip`: Are there any jumping-on-mushrooms games for the Xbox/PS3?
  890. # [15:06] <jgraham_> (that are comparable in quality to Mario)
  891. # [15:07] <da3d> The whole "Wii = casual" thing is way overblown...
  892. # [15:08] <Philip`> jgraham_: Seems unlikely
  893. # [15:08] <Philip`> At least there's Braid (on 360), which borrows some elements from Mario
  894. # [15:08] <da3d> Little Big Planet maybe?
  895. # [15:09] * Philip` has never actually owned any console other than a DS, so he's not speaking from much experience here
  896. # [15:09] * da3d hasn't played LBP though...
  897. # [15:12] * Joins: jacobolus (n=jacobolu@dhcp-0019888332-61-67.client.student.harvard.edu)
  898. # [15:12] <Philip`> ((Braid is also on PC, for ~£10, and is certainly worth it, unless you hate games))
  899. # [15:15] <beowulf> LBp is fun
  900. # [15:18] * da3d just noticed <dialog> has been dropped :(
  901. # [15:23] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) (Read error: 110 (Connection timed out))
  902. # [15:23] * Joins: miketaylr (n=mtaylor@38.117.156.163)
  903. # [15:26] * Quits: jacobolus (n=jacobolu@dhcp-0019888332-61-67.client.student.harvard.edu) (Remote closed the connection)
  904. # [15:30] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  905. # [15:30] * Joins: lazni (n=lazni@118.71.59.135)
  906. # [15:30] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  907. # [15:30] * Quits: MikeSmith (n=MikeSmit@EM114-48-205-177.pool.e-mobile.ne.jp) (Read error: 104 (Connection reset by peer))
  908. # [15:31] <Lachy> in the about: URI spec, would it be sensible for it to define how to handle the query string for about:blank?
  909. # [15:31] <Lachy> It currently says nothing about it, but browsers don't seem to be interoperable on this at all
  910. # [15:32] <Lachy> some just ignore the query string and return a blank page. IE8 complains with a Navigation cancelled message
  911. # [15:32] <Lachy> da3d, that was dropped earlier today because it was useless.
  912. # [15:33] <Lachy> and badly designed
  913. # [15:35] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Client Quit)
  914. # [15:36] <othermaciej> Lachy: if other random about: URIs are undefined, and it's not needed for interop, then you can probably leave it undefined
  915. # [15:39] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  916. # [15:41] <Lachy> othermaciej, fair enough
  917. # [15:41] <da3d> Lachy: Yeah, I saw that while reading the irc logs. I kinda liked it, but I can't really argue against the issues it had so dropping it is probably for the best.
  918. # [15:41] * Joins: MikeSmith (n=MikeSmit@EM114-48-127-198.pool.e-mobile.ne.jp)
  919. # [15:41] * Quits: MikeSmith (n=MikeSmit@EM114-48-127-198.pool.e-mobile.ne.jp) (Read error: 104 (Connection reset by peer))
  920. # [15:42] <othermaciej> I'm kind of motivated to implement the new <figure> and/or <details> now
  921. # [15:42] <Lachy> cool
  922. # [15:42] * Joins: webben_ (n=benh@nat/yahoo/x-kpzuhyciumlwykcu)
  923. # [15:42] <Lachy> I'm curious what UI you intend to give to details
  924. # [15:43] <Lachy> will it just be an expander triangle (or +/- icon) next to the dt?
  925. # [15:43] * Joins: MikeSmith (n=MikeSmit@EM114-48-127-198.pool.e-mobile.ne.jp)
  926. # [15:47] <annevk42> Lachy, I'd rather have it defined
  927. # [15:47] <annevk42> Lachy, probably as not having an effect
  928. # [15:49] <Philip`> The internet uses <dl> much more than I anticipated
  929. # [15:51] <Philip`> Also, computers are far too slow
  930. # [15:51] <Philip`> 1400 seconds and it's still not finished :-(
  931. # [15:51] <Lachy> annevk42, do you mean to define it such that about:blank and about:blank?foo are always effectively equivalent, as far as determining what resource to return is concenred?
  932. # [15:52] <jgraham_> Lachy: That seems sensible
  933. # [15:53] <annevk42> yeah
  934. # [15:54] * Quits: webben (n=benh@nat/yahoo/x-drazzxtcsvidxosa) (Read error: 110 (Connection timed out))
  935. # [15:54] <Lachy> ok
  936. # [15:54] * Joins: aroben (n=aroben@unaffiliated/aroben)
  937. # [15:56] <annevk42> as for fragids btw
  938. # [15:56] <annevk42> you can leave those out
  939. # [15:56] <othermaciej> Lachy: I would do it like Mac OS X disclosure triangles, but the tricky bit will be getting a nice animation
  940. # [15:56] <Lachy> annevk42, yeah, I know. They were already dropped from a previous draft
  941. # [15:56] <Philip`> (1600 seconds, a million lines of output, still not nearly finished...)
  942. # [15:57] <Lachy> othermaciej, do it with CSS transitions.
  943. # [15:57] <erlehmann> othermaciej, GTK has them too. so are they gonna implemented as native widgets?
  944. # [15:57] <Philip`> othermaciej, do it with <video>
  945. # [15:57] <Lachy> transition the height of the <dd> from 0 to auto over a 1s period
  946. # [15:57] <othermaciej> Lachy: that's what I was thinking - but I need to at least add pseudo-classes for the closed and open states in that case
  947. # [15:57] <Lachy> not sure how that would work with multiple <dd>s though
  948. # [15:58] <othermaciej> erlehmann: nothing in WebKit is implemented with native widgets
  949. # [15:58] <Philip`> Pre-render an MPEG of the animated triangle
  950. # [15:58] <othermaciej> erlehmann: I *could* make it themable but I am not sure it's worth it
  951. # [15:58] <erlehmann> Philip`, or, if MNG support is still in … wasn't that interactive?
  952. # [15:58] <hsivonen> WebKit has MNG support?
  953. # [15:58] <erlehmann> othermaciej, how does webkit-gtk work then? is it „fake“ widgets like with gtk-themed qt?
  954. # [16:00] <othermaciej> erlehmann: it uses the Gtk theme API to draw the native appearance
  955. # [16:01] <othermaciej> erlehmann: WebKit on Mac does it using Cocoa theme APIs
  956. # [16:01] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Read error: 110 (Connection timed out))
  957. # [16:01] <othermaciej> but all controls are drawn using CSS rendering
  958. # [16:01] <othermaciej> which allows you to fully style them if you choose
  959. # [16:02] <erlehmann> nice :) so the CSS transition approach is even flexible
  960. # [16:02] <annevk42> hmm yeah, we should have :open and :close or some such
  961. # [16:03] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
  962. # [16:04] * jgraham_ wonders how the need to introduce one CSS feature per HTML5 feature affects the idea that they are independant
  963. # [16:05] <annevk42> Selectors are not really independent
  964. # [16:05] <annevk42> and maybe CSS in general isn't either, dunno
  965. # [16:07] <annevk42> maybe this is something we should tackle for HTML6; how to introduce markup features that also need their visual/UI-side covered to succeed
  966. # [16:07] <erlehmann> jgraham_, i am envisioning a science-fiction short story where after a global crisis the world is ruled by the WHATWG, only by exploiting through several loopholes in existing web standards that ultimately tie into state law through use of accessability hoops.
  967. # [16:07] <othermaciej> it's hard to make pseudo-classes and psuedo-elements fully independent of the markup language
  968. # [16:07] <erlehmann> oopn, strike the "through"
  969. # [16:08] <hsivonen> It's bit sad that Google Maps views on various Web pages aren't resolution-independent
  970. # [16:08] <hsivonen> at least not in Firefox
  971. # [16:09] * hsivonen wants Google Maps to use SVG
  972. # [16:09] <erlehmann> hsivonen, what other web map widgets are there? any using SVG?
  973. # [16:10] <hsivonen> I don't know
  974. # [16:10] <hsivonen> but I've browsed the Web lately with device pixel not equaling a CSS pixel
  975. # [16:10] <hsivonen> and my conclusion is that the Web needs a lot more vector graphics
  976. # [16:11] <Philip`> Could you come to a different conclusion that doesn't involve redesigning every web page in the world?
  977. # [16:11] <Lachy> othermaciej, here's a simple demo of how it could work http://software.hixie.ch/utilities/js/live-dom-viewer/saved/232
  978. # [16:12] <Lachy> though that CSS isn't perfect
  979. # [16:12] <Rik|work> :expanded and the opposite can be useful for <details> and tree views in general
  980. # [16:13] <othermaciej> Lachy: now that's neat
  981. # [16:14] <Lachy> othermaciej, the only problem is that using height: auto; wouldn't work for the transition is going to the open state. So I had to hard code in a value for that
  982. # [16:14] <annevk42> doesn't work in Opera
  983. # [16:14] <Lachy> annevk42, that's cause I didn't use the -o- properly.
  984. # [16:14] <Lachy> *property
  985. # [16:15] <othermaciej> excepting I'd add a disclosure triangle and adjust the margins and such
  986. # [16:15] <othermaciej> also I think only the label should react to clicks
  987. # [16:15] * Joins: zdobersek (n=zan@cpe-92-37-65-68.dynamic.amis.net)
  988. # [16:15] <Lachy> and also cause we don't have transitions in 10, but it should work in core
  989. # [16:15] <othermaciej> does the spec require otherwise? if so it should be fixed IMO
  990. # [16:15] <Lachy> othermaciej, I don't think the spec requires any specific UI
  991. # [16:16] <othermaciej> basically because details needs to be able to hold interactive controls and it would be frustrating if a misclick collapsed it
  992. # [16:16] <Lachy> I just made the whole details clickable for simplicity. Making only the <dt> clickable would have reqired and extra line or two of code
  993. # [16:17] <annevk42> Lachy, it should at least hide/display without transitions, no?
  994. # [16:17] <jgraham_> Yeah only the label shopuld be clickable for sure
  995. # [16:17] <Rik|work> I want a slower transition if I hold Shift :)
  996. # [16:17] <Lachy> actually, it would just require this change: <details><dt onclick="toggle(this.parentNode);">Click This
  997. # [16:17] <annevk42> also doesn't work in Chrome
  998. # [16:18] <Lachy> does chrome support transitions?
  999. # [16:18] <Philip`> I hope it animates nicely with no jumping if you try to close it in the middle of the opening animation
  1000. # [16:18] <othermaciej> would it be overly gross to reuse :checked instead of making a new pseudo?
  1001. # [16:20] <annevk42> othermaciej, that sounds fine to me
  1002. # [16:20] <jgraham_> that sounds somewhat dubious to me, but then I know nothing about CSS
  1003. # [16:21] <jgraham_> (I would worry a bit about people finding their scripts that assumed only form controls could be :checked breaking)
  1004. # [16:21] <othermaciej> if I make up a new pseudo it has to be a -webkit-prefixed one at least for now
  1005. # [16:21] <Lachy> annevk42, it works in gogi if you move the onclick attribute to the <dt> like I showed above and change the -webkit- to -o-
  1006. # [16:21] <annevk42> it's a boolean state and :checked matches that
  1007. # [16:21] <Lachy> apparently we don't support event attributes on unknown elements, like webkit does
  1008. # [16:21] <annevk42> the name might not match exactly, but still...
  1009. # [16:22] <annevk42> Lachy, hmm, we should have a bug on that
  1010. # [16:22] <Lachy> do you want to file ti?
  1011. # [16:22] <Lachy> it?
  1012. # [16:22] * Joins: arun__ (n=arun@adsl-75-36-189-9.dsl.pltn13.sbcglobal.net)
  1013. # [16:23] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  1014. # [16:23] <Lachy> othermaciej, why do we need the new pseudo?
  1015. # [16:24] <Lachy> what's wrong with just basing it on the open attribute like details[open] and details:not([open])
  1016. # [16:24] * Joins: zcorpan (n=zcorpan@pat.se.opera.com)
  1017. # [16:24] <othermaciej> Lachy: does the attribute have to reflect the current open state?
  1018. # [16:24] <Lachy> yes
  1019. # [16:25] <othermaciej> that would work then
  1020. # [16:25] <zcorpan> <video src=data:application/octect-stream,broken onemptied=this.appendChild(document.createElement('source'))></video>
  1021. # [16:26] * Joins: sbublava (n=stephan@77.117.33.177.wireless.dyn.drei.com)
  1022. # [16:26] <zcorpan> networkState is NETWORK_EMPTY, so inserting a <source> will start the resource selection algorithm
  1023. # [16:26] <zcorpan> the resource selection algorithm will see that a src attribute is present
  1024. # [16:27] <zcorpan> and use src
  1025. # [16:27] <annevk42> ah yeah, I forgot that about <details>
  1026. # [16:27] <annevk42> still not sure whether such a design makes sense, but I suppose it does not matter
  1027. # [16:30] * Quits: KevinMarks (n=KevinMar@c-67-164-14-96.hsd1.ca.comcast.net) ("The computer fell asleep")
  1028. # [16:31] <Lachy> annevk42, what doesn't make sense about the design?
  1029. # [16:31] <annevk42> it's different from all other form controls
  1030. # [16:32] <Lachy> it's not a form control though
  1031. # [16:32] <annevk42> form control, ui control, all the same imo
  1032. # [16:33] <othermaciej> the way form control value works is terrible though
  1033. # [16:34] * Quits: webben_ (n=benh@nat/yahoo/x-kpzuhyciumlwykcu) (Client Quit)
  1034. # [16:34] * Joins: webben (n=benh@nat/yahoo/x-crqxqiozeejfktlv)
  1035. # [16:35] <annevk42> yeah, that was Hixie's argument for keeping it this way
  1036. # [16:35] <Lachy> ok, I guess I'm missing something. I don't see how it could possibly work any other way
  1037. # [16:37] <othermaciej> it could work in a way where the markup attribute sets the default initial value but the dynamic state is decoupled from it thereafter
  1038. # [16:38] <jgraham_> Of course that would be weird and confusing
  1039. # [16:38] <Lachy> ah, ok. Yeah, that would be silly.
  1040. # [16:39] <Lachy> it's confusing enough for <input> and <textarea>
  1041. # [16:39] <othermaciej> I'
  1042. # [16:40] <othermaciej> I'm not saying that it would be good to do that, just that it's possible, and probably what annevk42 had in mind
  1043. # [16:44] <Philip`> http://philip.html5.org/data/dl.html
  1044. # [16:44] <Philip`> Feel free to look for people using it for dialog etc
  1045. # [16:44] <Philip`> if you're incredibly bored
  1046. # [16:50] * Joins: myakura (n=myakura@p2046-ipbf4007marunouchi.tokyo.ocn.ne.jp)
  1047. # [16:53] <jgraham_> There are a few uses for lists of comments in bug trackers and forums which are a bit like dialog
  1048. # [16:53] * jgraham_ has looked at the top third or so
  1049. # [16:54] * Quits: myakura (n=myakura@p2046-ipbf4007marunouchi.tokyo.ocn.ne.jp) (Client Quit)
  1050. # [16:55] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  1051. # [16:55] * Joins: weinig_ (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  1052. # [16:56] * weinig_ is now known as weinig
  1053. # [16:56] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  1054. # [16:56] * Joins: weinig_ (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  1055. # [16:57] * weinig_ is now known as weinig
  1056. # [17:03] * Parts: Mrmil (n=ut_ollie@host-77-236-204-8.blue4.cz)
  1057. # [17:06] <beowulf> what's the point of <dl>?
  1058. # [17:07] <Philip`> Backward compatibility with content that uses <dl>
  1059. # [17:08] <beowulf> :)
  1060. # [17:08] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  1061. # [17:08] * Quits: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl) ("Disconnected...")
  1062. # [17:08] <hsivonen> beowulf: getting a mix of bolded text and indented text
  1063. # [17:08] * Quits: Lachy (n=Lachlan@pat-tdc.opera.com) ("This computer has gone to sleep")
  1064. # [17:09] <zcorpan> it seems like the "If the media data is corrupted" condition is dead code if your media framework is non-draconian in its error handling
  1065. # [17:09] * Quits: nessy (n=nessy@124-170-13-58.dyn.iinet.net.au) ("This computer has gone to sleep")
  1066. # [17:10] <jgraham_> hsivonen: Having just looked through the big list from Philip` it seems like there are quite a few basically conforming uses
  1067. # [17:10] <jgraham_> ANd a few basically non-conforming uses
  1068. # [17:10] <jgraham_> (no conversation in English that I spotted)
  1069. # [17:10] <zcorpan> i would appreciate if someone could produce a file that gstreamer can play but then aborts with a fatal error
  1070. # [17:11] <Philip`> hsivonen: You don't get bold automatically, only indentation
  1071. # [17:12] <Philip`> jgraham_: If you want, I can give you a list that's 50 times bigger
  1072. # [17:18] <jgraham_> Philip`: No
  1073. # [17:20] <Philip`> jgraham_: I can give you one that is approximately n times bigger, for 0 <= n <= 50
  1074. # [17:21] * Quits: mat_t (n=mattomas@91.189.88.12) ("This computer has gone to sleep")
  1075. # [17:22] <jgraham_> Philip`: Can I have n=0 please?
  1076. # [17:23] * Joins: dglazkov (n=dglazkov@nat/google/x-nvocopikstpuwuwa)
  1077. # [17:25] * Joins: Lachy (n=Lachlan@85.196.122.246)
  1078. # [17:25] <Philip`> jgraham_: Sure
  1079. # [17:25] <Philip`> jgraham_: I've uploaded it to about:blank
  1080. # [17:26] <Philip`> (Sorry for using a non-standard URL)
  1081. # [17:27] <Dashiva> Philip`: Wikipedia gives you bold :P
  1082. # [17:28] * hsivonen wonders how ActiveX integrates with the event loop considering that sync XHR started out as an ActiveX thingy
  1083. # [17:30] * Joins: mat_t (n=mattomas@91.189.88.12)
  1084. # [17:31] <hsivonen> cool. it seems the W3C is doing several right things: http://omocha.w3.org/wiki/
  1085. # [17:31] <hsivonen> Reftest, Mochitest and hg
  1086. # [17:33] <annevk42> I was just about to post that :)
  1087. # [17:34] <jgraham_> Hmm, so I'm not sure about Mochitest
  1088. # [17:35] <hsivonen> jgraham_: what's wrong with Mochitest?
  1089. # [17:35] <jgraham_> Since according to the mochitest page the main advantage (for Mozilla) is that it can be run in chrome
  1090. # [17:36] <jgraham_> On a technical level a) using == rather than === for assertions is wrong
  1091. # [17:37] * jgraham_ forgets what b) and c) were
  1092. # [17:39] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  1093. # [17:39] * Philip` uses mochitests for his (mostly non-chrome) canvas tests, because it seemed the easiest way to do script-based assertions
  1094. # [17:39] <jgraham_> I guess if it depends on Mochikit that is overkill for most testing needs. You don't want a bug in the test harness to cause all the tests to fail
  1095. # [17:39] <Philip`> (This is for the version of the tests that's in Mozilla's test suite)
  1096. # [17:39] <jgraham_> (that's why jsUnit is evil, for example)
  1097. # [17:43] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  1098. # [17:43] * Joins: lazni1 (n=lazni@118.71.115.2)
  1099. # [17:43] <hsivonen> we should collect a list of troublesome Web features so that proposed features can be compared to the list for early detection of badness
  1100. # [17:43] <hsivonen> stuff like sync XHR, Namespaces, alert() and document.write()
  1101. # [17:43] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Client Quit)
  1102. # [17:44] * Quits: jrib (n=jrib@upstream/dev/jrib) (Read error: 110 (Connection timed out))
  1103. # [17:44] <annevk42> localStorage o_O
  1104. # [17:44] <jgraham_> I guess another problem about MochiTest is that the number of assertions is wrong. There should either be lots (to deal with exceptions, e.g.) or just a way of recording pass/fail
  1105. # [17:47] * Quits: fishd_ (n=darin@c-67-180-164-209.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
  1106. # [17:49] * Joins: Pure (n=Pure@cpc1-warr5-0-0-cust372.bagu.cable.ntl.com)
  1107. # [17:49] <Pure> Hey!
  1108. # [17:50] <jgraham_> Hej
  1109. # [17:50] <Pure> How extensive is Offline Applications?
  1110. # [17:50] <Pure> In HTML5
  1111. # [17:50] <annevk42> did that guy who was going to explain us how HTML5 is silly and bloated come back with his blogpost btw?
  1112. # [17:50] <annevk42> Pure, ?
  1113. # [17:51] <Pure> *Looks up nme*
  1114. # [17:51] <Pure> The caching of pages for offline using
  1115. # [17:51] <annevk42> what do you mean with extensive?
  1116. # [17:52] <boblet> Any Opera ppl here with @font-face experience?
  1117. # [17:52] * zcorpan has some experience
  1118. # [17:53] * Quits: pesla (n=retep@procurios.xs4all.nl) ("( www.nnscript.com :: NoNameScript 4.21 :: www.esnation.com )")
  1119. # [17:53] * annevk42 has some too
  1120. # [17:53] <boblet> Daniel Davis’ nice Japanese example page using M+ font isn’t actually using M+ font http://devfiles.myopera.com/articles/751/japanese-newspaper.html
  1121. # [17:54] * aroben is now known as aroben|afk
  1122. # [17:54] <Pure> I mean, can I have an offline version of the page and an online version?
  1123. # [17:54] <Pure> And can the manifest be in php?
  1124. # [17:55] <boblet> The other Japanese @font-face font (in the main title) works fine, but I can’t get M+ fonts to work (M+ is used in article titles—cf Safari/FF where it’s much bolder/different glyphs)
  1125. # [17:56] <boblet> brokenforeveryoneorjustme.com?
  1126. # [17:56] * Parts: lazni1 (n=lazni@118.71.115.2)
  1127. # [17:57] <beowulf> Pure: I think there's a bug with a version of ff related to offline web pages
  1128. # [17:59] <annevk42> Pure, not really
  1129. # [17:59] <annevk42> Pure, actually, yes, you can
  1130. # [17:59] <Pure> Huh?
  1131. # [17:59] <annevk42> Pure, though from what I heard Firefox does not support FALLBACK or something
  1132. # [17:59] * beowulf is answering Pure's first q
  1133. # [17:59] <Pure> And they can be in php?
  1134. # [17:59] <zcorpan> beowulf: i don't see any difference between opera and firefox for the article titles
  1135. # [18:00] <beowulf> zcorpan: ?
  1136. # [18:00] <zcorpan> beowulf: sorry
  1137. # [18:00] <zcorpan> boblet: i don't see any difference between opera and firefox for the article titles
  1138. # [18:01] <annevk42> Pure, what do you mean PHP?
  1139. # [18:01] <annevk42> Pure, the client never gets PHP
  1140. # [18:01] <boblet> zcorpan: are you using MacOSX?
  1141. # [18:01] * Quits: lazni (n=lazni@118.71.59.135) (Read error: 110 (Connection timed out))
  1142. # [18:02] <Pure> Does the client not request the manifest file, then the server parses it for php?
  1143. # [18:02] <annevk42> Pure, sure
  1144. # [18:02] * Joins: Maurice (i=copyman@5ED548D4.cable.ziggo.nl)
  1145. # [18:03] <annevk42> Pure, you need to set the correct media type though
  1146. # [18:03] <annevk42> Pure, maybe you're not doing that?
  1147. # [18:03] <zcorpan> boblet: no, windows
  1148. # [18:03] <GPHemsley> I assume there was an extensive discussion about dropping the 'cite' and 'pubdate' attributes from <article>?
  1149. # [18:03] <Pure> I haven't tried yet, I'm just wondering
  1150. # [18:03] <GPHemsley> (Aww, man, my logic is prohibited again? ...)
  1151. # [18:04] <annevk42> Pure, in the end it's just bytes going over the wire, PHP has nothing to do with it
  1152. # [18:04] <annevk42> GPHemsley, it was before too, just in Japenese
  1153. # [18:04] <boblet> zcorpan: I don’t know if the version numbers are cross-platform, but what build? I’m on v6652 (newest for Mac)
  1154. # [18:04] <zcorpan> Pure: php can generate any stream of bytes and set arbitrary headers
  1155. # [18:04] <GPHemsley> annevk42: Oh, last I heard it had been turned into literal question marks.
  1156. # [18:04] <zcorpan> Pure: so you can set the content-type header to whatever is needed for the manifest file and then generate it with php if you want
  1157. # [18:04] <annevk42> GPHemsley, that was very temporary
  1158. # [18:04] * GPHemsley shrugs
  1159. # [18:05] <GPHemsley> but anyway, back to my main question
  1160. # [18:05] <zcorpan> boblet: 1733
  1161. # [18:05] <annevk42> pubdate moved to <time>
  1162. # [18:05] <annevk42> cite was not found useful enough
  1163. # [18:05] * Joins: dbaron (n=dbaron@nat/mozilla/x-njrtwhraoojiwfmx)
  1164. # [18:05] <Pure> What happens if the user tries to view a php page while offline?
  1165. # [18:06] <Lachy> cite="" should also be dropped from blockquote
  1166. # [18:07] <Lachy> since browsers don't offer a way to follow it and authors duplicate it with <a href> and <cite> anyway
  1167. # [18:07] * Joins: fishd_ (n=darin@nat/google/x-dcvyvxhpfxczqzwb)
  1168. # [18:07] <zcorpan> Pure: there's no difference between "a php page" or "an html page"
  1169. # [18:07] <Pure> Ah, the last generated page will be shown
  1170. # [18:07] <annevk42> #httpistough
  1171. # [18:08] <Pure> Can I detect if the user is offline with javascript
  1172. # [18:08] <annevk42> yes
  1173. # [18:08] <annevk42> see navigator.onLine
  1174. # [18:08] <zcorpan> isn't there a tutorial for this?
  1175. # [18:08] <annevk42> on devmo
  1176. # [18:09] <boblet> zcorpan: ok thanks. will file a bug with a screenshot
  1177. # [18:10] <zcorpan> boblet: cool thanks
  1178. # [18:11] <GPHemsley> I think I agree with Erik's commentary on <cite>, FWIW. It should be able to contain one full line of a works cited page. Either allow for embedded <cite>s with different 'type' attributes (e.g. full, title, author, etc.), or just leave that job for <span> and CSS.
  1179. # [18:11] <GPHemsley> (referencing the recent mailing list post)
  1180. # [18:16] * Philip` thinks "we will [...] deviate from the standard" is a great quote
  1181. # [18:17] <GPHemsley> heh
  1182. # [18:17] <Philip`> At least they're not consistently pretending to support it when they don't
  1183. # [18:18] * aroben|afk is now known as aroben
  1184. # [18:19] * Joins: cohitre (n=cohitre@dhcp-0061496037-dc-9f.client.fas.harvard.edu)
  1185. # [18:21] * Joins: cardona507 (n=cardona5@c-67-180-160-250.hsd1.ca.comcast.net)
  1186. # [18:35] * Quits: Lachy (n=Lachlan@85.196.122.246) ("This computer has gone to sleep")
  1187. # [18:35] * Joins: Lachy (n=Lachlan@85.196.122.246)
  1188. # [18:36] <takkaria> Shelley is so vitriolic I can feel the acid burn from thousands of miles away
  1189. # [18:36] <Dashiva> Again?
  1190. # [18:37] <adactio> takkaria: Yeah, this kind of made me wince a little: http://twitter.com/shelleypowers/status/4006648345
  1191. # [18:38] <takkaria> for some reason <dt> being used for stuff other than <dl> makes it "virtually useless", and now it's part of a "so-called 'details'" element
  1192. # [18:38] <takkaria> apparently it means nothing anymore
  1193. # [18:38] <Philip`> Her recent email doesn't appear to ask any questions or suggest any changes
  1194. # [18:38] <Philip`> so it's hard to do anything productive with it
  1195. # [18:39] <takkaria> I wish that her leaving the working group meant she posted to public-html less, but that doesn't seem to be happening so much
  1196. # [18:40] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  1197. # [18:40] * Joins: cying_ (n=cying@70.90.171.153)
  1198. # [18:42] <jgraham_> I wish her being a chronic attention seeker didn't actually result in her getting a disproportionate amount of attention
  1199. # [18:42] <zcorpan> Philip`: it asks a question in the Subject:
  1200. # [18:44] <boblet> zcorpan: bug DSK-265703 (I guess)
  1201. # [18:44] <Philip`> zcorpan: Ah, yes
  1202. # [18:44] <Philip`> zcorpan: I assumed that was a rhetorical question :-)
  1203. # [18:44] <zcorpan> boblet: thanks
  1204. # [18:45] <boblet> also interesting to note Daniel’s sample page is misusing <section> (another example of confusion on how to use section)
  1205. # [18:46] <Philip`> Are there existing examples of elements that have very different meaning depending on the context they're used in?
  1206. # [18:47] <Philip`> (assuming they're used conformingly in their context)
  1207. # [18:47] <annevk42> <h1>
  1208. # [18:47] <hober> adactio: thanks for the shout-out, btw
  1209. # [18:47] <boblet> oh, hey adactio. nice work on dt/dd idea yo
  1210. # [18:48] <takkaria> but they mean nothing now!!1!
  1211. # [18:48] * Quits: cohitre (n=cohitre@dhcp-0061496037-dc-9f.client.fas.harvard.edu) (Read error: 110 (Connection timed out))
  1212. # [18:48] * takkaria stops sniping
  1213. # [18:49] <Philip`> annevk42: Hmm, anything with a less subtle distinction than that?
  1214. # [18:49] <beowulf> Philip`: <li>?
  1215. # [18:50] <beowulf> that's not a very different meaning though, sry
  1216. # [18:50] * beowulf tries harder
  1217. # [18:51] <annevk42> Philip`, <dfn> sort of depends on the context, but not very different
  1218. # [18:52] <annevk42> Philip`, the <dt>/<dd> is also not that different
  1219. # [18:53] <annevk42> though a bit more
  1220. # [18:53] <boblet> Hixie: I think the “a general rule…” text in the note on #the-section-element isn’t going to make sense to authors.
  1221. # [18:53] * Quits: zcorpan (n=zcorpan@pat.se.opera.com)
  1222. # [18:54] <boblet> Hixie: this is too long, but might be of some use: http://html5doctor.com/the-section-element/#comment-970
  1223. # [18:56] <jgraham_> Philip`: <kbd> and <samp>
  1224. # [18:57] * Joins: cgriego (n=cgriego@rrcs-24-173-70-117.sw.biz.rr.com)
  1225. # [18:58] <boblet> later all
  1226. # [18:59] * aroben is now known as aroben|lunch
  1227. # [18:59] <jgraham_> (also, arguably <aside>)
  1228. # [18:59] * boblet is now known as boblet_
  1229. # [18:59] * Philip` wonders why Opera just says "Secure site: The connection to mail.google.com is secure." with no extra information (e.g. company names) in the address bar thingy or the dialog box
  1230. # [19:00] <Philip`> Does that mean it could easily be a MITM attack? (with a secure connection to an unknown server)
  1231. # [19:00] <AryehGregor> Not unless they've got a CA to give them a certificate for mail.google.com.
  1232. # [19:02] <AryehGregor> If it doesn't give a company name, that just means it might not be a fancy extra-expensive certificate that supposedly verifies that mail.google.com actually belongs to, you guessed it, Google, Inc.
  1233. # [19:02] <AryehGregor> Which is not terribly useful anyway, AFAICT.
  1234. # [19:04] <Pure> Can I have my page have a certificate on it?
  1235. # [19:05] <AryehGregor> Yes, if you pay a CA for it. Or self-sign/use CACert/etc. for free, which browsers will complain about.
  1236. # [19:07] <AryehGregor> "While I was at it, I also did this for <figure>, and removed <dialog> from the spec altogether."
  1237. # [19:07] <AryehGregor> I like the casualness of that statement.
  1238. # [19:08] <AryehGregor> (yay for the death of <dialog>)
  1239. # [19:08] <Pure> Why would a browser complain about it?
  1240. # [19:08] <AryehGregor> Because it doesn't actually verify who you are.
  1241. # [19:08] <AryehGregor> http://en.wikipedia.org/wiki/Public_key_infrastructure
  1242. # [19:09] <Philip`> AryehGregor: If I go to e.g. https://www.ietf.org/ (which I don't think is fancy extra-expensive), it still shows the certificate's domain in the address bar, and has "Certificate summary" and a Certificate tab in the dialog box
  1243. # [19:09] <Philip`> whereas on Gmail I get none of that
  1244. # [19:09] <Philip`> (Amusingly https://ietf.org complains of an invalid certificate, because it doesn't match *.ietf.org)
  1245. # [19:10] * Joins: weinig (n=weinig@17.246.16.129)
  1246. # [19:11] <AryehGregor> http://www.verisign.com/ssl/ssl-information-center/extended-validation-ssl-certificates/index.html
  1247. # [19:11] <AryehGregor> http://en.wikipedia.org/wiki/Extended_Validation_Certificate
  1248. # [19:11] * Quits: Creap (n=Creap@vemod.brg.sgsnet.se) (Remote closed the connection)
  1249. # [19:12] <Philip`> AryehGregor: That doesn't seem relevant when I just want Opera to show me at least a few details of the normal non-EV certificate on Gmail
  1250. # [19:12] * Quits: Hish (n=chatzill@212.23.139.152) (Read error: 131 (Connection reset by peer))
  1251. # [19:12] * Joins: Hish (n=chatzill@mail2.n-e-s.de)
  1252. # [19:12] <AryehGregor> Chrome doesn't seem to show almost anything.
  1253. # [19:12] <AryehGregor> I'm not sure what info you're saying Opera is missing.
  1254. # [19:13] <Philip`> Imagine any kind of information whatsoever
  1255. # [19:13] <Philip`> Opera is missing it
  1256. # [19:13] <AryehGregor> ietf.org doesn't seem to be using an EV cert either.
  1257. # [19:13] * Joins: paul_irish (n=paul_iri@12.33.239.250)
  1258. # [19:13] <AryehGregor> Meh, UI issue.
  1259. # [19:13] * Joins: Creap (n=Creap@vemod.brg.sgsnet.se)
  1260. # [19:14] <Philip`> "I apologize in advance if any of this post duplicates things that have been said before I joined these lists" - hmph, you were too lazy to catch up on the archive before joining?
  1261. # [19:14] <annevk42> Philip`, for mail.google.com I see mail.google.com in the address bar with the padlock... just like for ietf.org
  1262. # [19:14] <Philip`> There's only like twenty thousand messages
  1263. # [19:14] <AryehGregor> Really, that few?
  1264. # [19:17] <Philip`> Next you'll be saying you didn't read all the archived IRC logs
  1265. # [19:18] <Philip`> http://philip.html5.org/misc/gmail-cert.png
  1266. # [19:19] <annevk42> weird
  1267. # [19:19] <Philip`> If I reload Gmail then it starts working fine
  1268. # [19:20] <Philip`> If I view an email with external images, it changes to a question mark and the dialog says it's insecure
  1269. # [19:21] <Philip`> I haven't seen it change back to the empty yellow box yet
  1270. # [19:22] * Quits: mat_t (n=mattomas@91.189.88.12) ("This computer has gone to sleep")
  1271. # [19:22] <Philip`> AryehGregor: If you're looking for examples of summary usage, http://philip.html5.org/data/table-summary-values-dotbot.html has some
  1272. # [19:22] <AryehGregor> Does that say if they actually meet the use cases adequately?
  1273. # [19:23] <AryehGregor> I can't figure out whether the examples given in the spec change proposal meets the proposed use case, let alone stuff on random websites.
  1274. # [19:23] <Philip`> It doesn't say anything, it's just mostly-raw data
  1275. # [19:23] * Quits: erlehmann (n=erlehman@tmo-109-179.customers.d1-online.com) (Read error: 113 (No route to host))
  1276. # [19:24] <Philip`> I think people who've looked at the data say most of it is either useless or garbage
  1277. # [19:24] * Quits: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com) (Remote closed the connection)
  1278. # [19:24] <Philip`> (That is, the summary values are useless or garbage, not the data about summary values)
  1279. # [19:24] <Philip`> (though the data might be too)
  1280. # [19:25] <Philip`> so there's no desire to make the spec accept what random websites do
  1281. # [19:27] * Joins: mpt (n=mpt@canonical/mpt)
  1282. # [19:28] <Philip`> "standards authors can't give authors much incentive to cater to blind people if blind people are 0.1% or less of their audience" - that's what government legislation is for, so people are forced to make things accessible even if it's not in their business interests
  1283. # [19:29] <Philip`> and so standards need to provide features that can be used by people who are forced to make things accessible, and that clearly demonstrate they've done some work to demonstrate they've made things accessible
  1284. # [19:30] <Philip`> (so explicit attributes are good, because you can easily check if they exist or not, and if they exist then someone's clearly been successfully forced to do some work)
  1285. # [19:30] <Philip`> Maybe that's how it works, anyway, or maybe that's totally wrong
  1286. # [19:31] * Quits: boblet_ (n=boblet@p1254-ipbf304osakakita.osaka.ocn.ne.jp)
  1287. # [19:33] * Joins: tantek (n=tantek@70.36.139.108)
  1288. # [19:34] * Joins: taf2 (n=taf2@38.99.201.242)
  1289. # [19:34] * Joins: benward (n=benward@209.131.62.113)
  1290. # [19:36] * jgraham_ feels compelled to make the obvious point that the existance of some accessibility attribute and the content actually being more accessible are not strongly correlated
  1291. # [19:36] <webben> Philip`: I think you'll find many people who think HTML is better off with features like "summary" don't have that much faith in automated testing for accessibility.
  1292. # [19:37] * Quits: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  1293. # [19:38] <annevk42> webben, I hope they don't think that the people who think HTML is worse off with such features do have much faith in that...
  1294. # [19:41] <AryehGregor> webben, I hope nobody has much faith in automated testing for accessibility.
  1295. # [19:41] <AryehGregor> Philip`, you can't realistically require that every website be accessible, or even most.
  1296. # [19:41] <hsivonen> hmm. non-DOM processors out of scope? http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Sep/0093.html
  1297. # [19:42] <AryehGregor> A small minority, sure, maybe.
  1298. # [19:42] <AryehGregor> But even then it's somewhat hard.
  1299. # [19:42] * hsivonen wonders how that's going to go with those who object to DOM-centricity
  1300. # [19:42] * Joins: erlehmann (n=erlehman@tmo-109-179.customers.d1-online.com)
  1301. # [19:42] * Joins: zcorpan (n=zcorpan@c83-252-193-59.bredband.comhem.se)
  1302. # [19:42] * Quits: cardona507 (n=cardona5@c-67-180-160-250.hsd1.ca.comcast.net)
  1303. # [19:42] <AryehGregor> It's not like RL accessibility, where you can say "everywhere has to be wheelchair-accessible by following these detailed rules about the exact width and slope of ramps needed".
  1304. # [19:43] * Joins: ifette_GOOG (n=ifette@nat/google/x-yuzhszcgoqagejle)
  1305. # [19:44] * Philip` wonders what kind of testing is used for accessibility legislation
  1306. # [19:44] * Quits: vs-hs (i=david@91.90.24.168) (Remote closed the connection)
  1307. # [19:45] * Joins: vs-hs (i=david@shell.etttretresju.net)
  1308. # [19:45] <AryehGregor> Web accessibility legislation, you mean?
  1309. # [19:45] * hsivonen thought governments pretty much look at whatever WCAG says for Web accessibility
  1310. # [19:45] * jgraham_ wonders if he should have sent the email explaining why a lxml-based RDFa processor would need to know about the htmlness of documents (or assume anything taht looked like xmlns: under the infoset coercion algorithm was actually html)
  1311. # [19:45] <Philip`> AryehGregor: Yes
  1312. # [19:45] <AryehGregor> Probably lengthy checklists of manually-checked regulations. Maybe just copied from WCAG.
  1313. # [19:45] <jgraham_> s/anything/any attribute with a name starting with something/
  1314. # [19:46] <hsivonen> jgraham_: seems like something to point out
  1315. # [19:48] <jgraham_> hsivonen: I am reluctant to engage in too much discussion about a technology I am as uninterested in as RDFa
  1316. # [19:48] <Philip`> jgraham_: It seems potentially productive to give concrete examples of why some implementers will have to care about these things, even if all the current implementations are coping alright with namespace-unaware APIs
  1317. # [19:48] * Joins: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  1318. # [19:49] * Joins: ap_ (n=ap@17.246.19.174)
  1319. # [19:49] <AryehGregor> Ugh, I shouldn't be posting these long things that will actually attract replies. I don't have time for it.
  1320. # [19:50] * Parts: adactio (n=adactio@host86-138-101-27.range86-138.btcentralplus.com)
  1321. # [19:50] <webben> annevk42: That wasn't what I meant; I see no reason to think they do. AryehGregor: That hope is likely to be disappointed.
  1322. # [19:50] <AryehGregor> What hope?
  1323. # [19:50] <AryehGregor> Oh.
  1324. # [19:50] <AryehGregor> Automated testing.
  1325. # [19:50] <AryehGregor> Oh well.
  1326. # [19:50] <webben> hsivonen: Pretty much, from what I've seen (looking at WCAG).
  1327. # [19:56] <othermaciej> AryehGregor: I think your post was interesting and I don't think it just duplicated previous posts
  1328. # [19:56] * Quits: ifette (n=ifette@nat/google/x-bltkwlrbdzhyrour) (Read error: 110 (Connection timed out))
  1329. # [19:58] * Quits: zdobersek (n=zan@cpe-92-37-65-68.dynamic.amis.net) ("Leaving.")
  1330. # [19:59] * Joins: gsnedders (n=gsnedder@217.44.35.222)
  1331. # [19:59] * dimich_away is now known as dimich
  1332. # [20:00] * Quits: zcorpan (n=zcorpan@c83-252-193-59.bredband.comhem.se) (Read error: 110 (Connection timed out))
  1333. # [20:06] * Quits: arun__ (n=arun@adsl-75-36-189-9.dsl.pltn13.sbcglobal.net) (Read error: 104 (Connection reset by peer))
  1334. # [20:07] * Quits: weinig (n=weinig@17.246.16.129) (Remote closed the connection)
  1335. # [20:07] * Joins: weinig (n=weinig@nat/apple/x-yrabjdruyjapwosv)
  1336. # [20:08] * Quits: Hish (n=chatzill@mail2.n-e-s.de) (Read error: 104 (Connection reset by peer))
  1337. # [20:08] <cgriego> As I read it, the details element content model forbids dd+dt? If I am reading that correctly, then I think that should instead be explicitly allowed.
  1338. # [20:08] * Joins: Hish (n=chatzill@212.23.139.152)
  1339. # [20:10] <Dashiva> cgriego: Hixie is more likely to listen if you give reasoning
  1340. # [20:11] <cgriego> The most common use case would be a more/less use case. Where some teaser content is always visible and you want the control anchored to the bottom.
  1341. # [20:12] * Quits: dbaron (n=dbaron@nat/mozilla/x-njrtwhraoojiwfmx) ("8403864 bytes have been tenured, next gc will be global.")
  1342. # [20:15] <Dashiva> But the teaser content would be the <dt> would it not?
  1343. # [20:15] <Dashiva> So it seems what you really want is control of the UI placement
  1344. # [20:20] <webben> cgriego: Sounds like something to be controlled with CSS.
  1345. # [20:21] <cgriego> No, teaser content would not appear in the dt because the teaser content should not control the show state.
  1346. # [20:21] <cgriego> Example (Show All Amenities): http://travel.ian.com/hotel/propertydetails/134540/SUMMARY?cid=40
  1347. # [20:22] * Joins: jwalden (n=waldo@nat/mozilla/x-ywqkoteajrwwfuwr)
  1348. # [20:22] <cgriego> Example (more under city list): http://www.getaroom.com/
  1349. # [20:22] <webben> cgriego: No teaser content should be extracted from the "hidden" part of details.
  1350. # [20:24] <webben> hmm.
  1351. # [20:26] <webben> cgriego: In the case of getaroom, I don't think the first cities you see should be part of details.
  1352. # [20:26] <cgriego> Agreed, it would appear before the details element.
  1353. # [20:27] <webben> cgriego: so <details><dt>More cities</dt><dd>... additional cities ... </dd></details>
  1354. # [20:29] <webben> cgriego: Though I suspect the widget as a whole is "semantically" http://dev.w3.org/html5/spec/forms.html#attr-input-list
  1355. # [20:29] <cgriego> That's the rub, in the case of adding expanded information, it's common for the control to be below the content.
  1356. # [20:29] <cgriego> As an author, I want to be able to put the dd first.
  1357. # [20:29] <webben> cgriego: Before/after is CSS.
  1358. # [20:30] <webben> though /either/ will gel with native <details> controls I dunno
  1359. # [20:31] <webben> cgriego: In CSS 2.1, position the dt relative to details; in CSS3, http://www.w3.org/TR/css3-content/#moving
  1360. # [20:31] <webben> *how /either/
  1361. # [20:33] <annevk42> cgriego, maybe you should suggest on the list that both orders should be allowed and give the examples
  1362. # [20:33] <annevk42> cgriego, though I'm not sure the second example applies
  1363. # [20:34] * Joins: arun__ (n=arun@adsl-75-36-189-9.dsl.pltn13.sbcglobal.net)
  1364. # [20:34] * arun__ is now known as otherarun
  1365. # [20:38] <cgriego> Additional examples: iTunes artwork panel, iCal calendars/notifications panel, firebug, IE developer tools.
  1366. # [20:39] * Joins: ifette (n=ifette@nat/google/x-opaarrinjcuskhfl)
  1367. # [20:44] * Quits: ifette_GOOG (n=ifette@nat/google/x-yuzhszcgoqagejle) (Read error: 110 (Connection timed out))
  1368. # [20:45] <annevk42> ifette, congrats, though where's Mac/Ubuntu-stable? :)
  1369. # [20:49] <hsivonen> annevk42: did the Chome team ship to stable channel?
  1370. # [20:49] <hsivonen> *Chrome
  1371. # [20:51] * Joins: sbublava_ (n=stephan@77.119.97.98.wireless.dyn.drei.com)
  1372. # [20:51] <hsivonen> it seems so
  1373. # [20:52] <hsivonen> did both Theora and H.264 make it to the stable release?
  1374. # [20:53] * Quits: JonathanNeal (n=Jonathan@76-219-69-134.lightspeed.breaca.sbcglobal.net) (Read error: 110 (Connection timed out))
  1375. # [20:55] * Quits: sbublava (n=stephan@77.117.33.177.wireless.dyn.drei.com) (Read error: 104 (Connection reset by peer))
  1376. # [20:57] * Joins: dbaron (n=dbaron@nat/mozilla/x-hbdojzkuaxacvmkc)
  1377. # [21:03] <hsivonen> hmm. CSSquirrel now has a URL in aria-describedby...
  1378. # [21:04] * Quits: erlehmann (n=erlehman@tmo-109-179.customers.d1-online.com) ("Ex-Chat")
  1379. # [21:09] <Lachy> that's not surprising. I expected that to become a common authoring mistake, as people think aria-describedby is a direct replacement for longdesc
  1380. # [21:09] * Joins: ifette_GOOG (n=ifette@nat/google/x-hrsqleanskewmjym)
  1381. # [21:10] <takkaria> relatively easy cowpath to pave, though
  1382. # [21:14] * Joins: Midler (n=midler@212.37.124.233)
  1383. # [21:17] <hsivonen> Lachy: the interesting part is that CSSquirrel was nonetheless put forward as a positive example by an accessibility expert despite it using the attribute wrong
  1384. # [21:18] * hsivonen assumes that Kyle Weems reads this anyway, so the IRC log counts as a bug report
  1385. # [21:18] * Quits: gsnedders (n=gsnedder@217.44.35.222) (Remote closed the connection)
  1386. # [21:19] * Joins: weinig_ (n=weinig@17.246.16.129)
  1387. # [21:19] <annevk42> it's funny how we always point out the mistakes...
  1388. # [21:20] * Joins: weinig__ (n=weinig@17.246.16.129)
  1389. # [21:20] * Quits: weinig_ (n=weinig@17.246.16.129) (Success)
  1390. # [21:20] * Joins: webben_ (n=benh@nat/yahoo/x-zugbezgvyiffxljg)
  1391. # [21:21] * Joins: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  1392. # [21:21] * Quits: ifette (n=ifette@nat/google/x-opaarrinjcuskhfl) (Read error: 110 (Connection timed out))
  1393. # [21:21] * Quits: weinig__ (n=weinig@17.246.16.129) (Client Quit)
  1394. # [21:22] <Dashiva> Maybe doing something is more important than doing it right
  1395. # [21:23] * jgraham_ is discovering why OpenOffice is not more popular
  1396. # [21:25] <Philip`> Because it's too free?
  1397. # [21:25] <jgraham_> Because the UI is too shit
  1398. # [21:25] <Philip`> Hmm, that too
  1399. # [21:26] * Quits: tantek (n=tantek@70.36.139.108)
  1400. # [21:26] * Philip` only really has Microsoft Office 97 as a point of comparison
  1401. # [21:26] * Joins: clarjon1 (n=clarjon1@unaffiliated/clarjon1)
  1402. # [21:27] <jgraham_> It seems exactly like what you would get if you made a really half assed clone of the Office-97 UI so that seems like a reasonable point of comparison
  1403. # [21:28] <hsivonen> OO.o is like SeaMonkey in need of its Firefox
  1404. # [21:29] <Philip`> I guess part of the problem is that Microsoft Office works pretty well, so few people have a personal desire to work on a replacement
  1405. # [21:30] * Quits: webben (n=benh@nat/yahoo/x-crqxqiozeejfktlv) (Read error: 113 (No route to host))
  1406. # [21:31] <Philip`> (whereas IE6 was old and unmaintained and lacked lots of necessary features, so there was strong incentive for a replacement)
  1407. # [21:32] <othermaciej> OO.o has crufty code and unpleasant UI
  1408. # [21:32] <hsivonen> I mean the OOo engine needs a better UI design
  1409. # [21:32] <jgraham_> But the replacemnets have generally done better by improving the UI not slavishly copying the UI
  1410. # [21:32] <jgraham_> from IE
  1411. # [21:32] <hsivonen> OOo's COM clone is rather horrible.
  1412. # [21:32] * hsivonen has programmed with the UNO Java bridge
  1413. # [21:33] <othermaciej> perhaps the same could be said for old school SeaMonkey, but OO.o's code is a lot bigger, and there's no motivated group of insiders looking to make a radical improvement
  1414. # [21:33] <hsivonen> where you need to do both QueryInterface *and* Java-level casting
  1415. # [21:34] <hsivonen> with the UNO-Java bridge, more than 50% of the lines of code are just dealing with the system and not doing anything productive
  1416. # [21:34] <Philip`> hsivonen: Indeed, and I mean there's probably few people interested in working on a better UI design for it, because those people (and most of the potential audience) can just use MS Office
  1417. # [21:35] <Philip`> (unless they're solely on Linux, in which they can't, but there aren't many people like that and they're not going to care a lot about UI design)
  1418. # [21:35] <Philip`> s/which/which case/
  1419. # [21:35] <roc> Google Docs etc will disrupt all this
  1420. # [21:36] * jgraham_ wonders why Philip` thinks that Linux users don't cre about UI design
  1421. # [21:36] <jgraham_> *care
  1422. # [21:36] * Quits: weinig (n=weinig@nat/apple/x-yrabjdruyjapwosv) (Read error: 110 (Connection timed out))
  1423. # [21:36] <jgraham_> Hmm Google docs. There's an idea
  1424. # [21:36] * taf2 likes nice looking apps on linux..
  1425. # [21:36] <jgraham_> IS it actually any good yet?
  1426. # [21:36] <Philip`> jgraham_: I guess some of them do, but not enough to make Linux a shining example of good UI design
  1427. # [21:37] <roc> jgraham_: no, but it's convenient
  1428. # [21:37] <jgraham_> Philip`: Generally a lot of Gnome stuff has pretty reasonable UI design. KDE is generally pretty awful I grant you
  1429. # [21:37] <takkaria> jgraham_: no, it's not
  1430. # [21:37] <roc> and for collaboration it can't really be beat
  1431. # [21:37] <hsivonen> mpt has lots of stuff to fix still
  1432. # [21:38] <takkaria> the spreadsheet stuff is good, mind
  1433. # [21:38] <mpt> Clearly I should sleep less
  1434. # [21:38] <roc> unless you have sharepoint
  1435. # [21:38] <roc> but most people don't have sharepoint
  1436. # [21:38] <takkaria> but the word processor feels much like sitting a bit contentEditable
  1437. # [21:38] <takkaria> *big contentEditable field
  1438. # [21:39] <jgraham_> mpt: Would it help if you stopped sleeping altogether?
  1439. # [21:39] <annevk42> roc, as uber-late reply, I mean <isindex> being implemented with XBL, not <hr> or <input> (they appear on screen if you use <isindex>)
  1440. # [21:39] <mpt> Sun apparently has a bench of UX designers working on OpenOffice.org
  1441. # [21:39] <jgraham_> takkaria: That's basically what I remember too
  1442. # [21:40] * Joins: Rik`_ (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  1443. # [21:40] <roc> annevk42: oh. The implementation of <isindex> predates XBL
  1444. # [21:40] * Quits: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net) (Read error: 113 (No route to host))
  1445. # [21:40] * Rik`_ is now known as Rik`
  1446. # [21:40] <annevk42> is it done directly in the style tree then or something?
  1447. # [21:41] * Quits: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  1448. # [21:41] <annevk42> oh well, doesn't really matter I guess
  1449. # [21:41] <roc> it uses a different anonymous content system
  1450. # [21:41] <roc> more like what Webkit does if I understand correctly
  1451. # [21:42] * Joins: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  1452. # [21:43] * Quits: webben_ (n=benh@nat/yahoo/x-zugbezgvyiffxljg) (Connection timed out)
  1453. # [21:43] * Joins: Super-Dot (n=Super-Do@66.240.27.50)
  1454. # [21:44] <hsivonen> roc: WebKit seems to have a parser macro for isindex
  1455. # [21:44] <roc> sorry, I mean the way Webkit does anonymous content in general, not for isindex
  1456. # [21:45] <hsivonen> I see
  1457. # [21:45] * Joins: murr4y` (n=murray@85.84-49-67.nextgentel.com)
  1458. # [21:46] * Quits: murr4y (n=murray@85.84-49-67.nextgentel.com) (Read error: 104 (Connection reset by peer))
  1459. # [21:51] * Quits: cying (n=cying@adsl-75-18-225-53.dsl.pltn13.sbcglobal.net)
  1460. # [21:51] * cying_ is now known as cying
  1461. # [21:52] * aroben|lunch is now known as aroben|away
  1462. # [21:53] * Joins: virtuelv (n=virtuelv@125.175.251.212.customer.cdi.no)
  1463. # [21:54] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) (Read error: 110 (Connection timed out))
  1464. # [21:56] <Lachy> now what on earth would be the point of allowing aria-describedby accept URLs instead of IDREFs, and let it be used just like longdesc? That would just repeat exactly the same mistake as longdesc! http://lists.w3.org/Archives/Public/public-html/2009Sep/0591.html
  1465. # [21:57] <Dashiva> But this time it'll be different!
  1466. # [21:58] * Quits: MikeSmith (n=MikeSmit@EM114-48-127-198.pool.e-mobile.ne.jp) (Read error: 110 (Connection timed out))
  1467. # [22:03] * Joins: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com)
  1468. # [22:04] * Quits: ifette_GOOG (n=ifette@nat/google/x-hrsqleanskewmjym) (Read error: 60 (Operation timed out))
  1469. # [22:08] * Quits: cying (n=cying@70.90.171.153)
  1470. # [22:14] * Quits: sbublava_ (n=stephan@77.119.97.98.wireless.dyn.drei.com)
  1471. # [22:14] * Quits: Pure (n=Pure@cpc1-warr5-0-0-cust372.bagu.cable.ntl.com) (Read error: 110 (Connection timed out))
  1472. # [22:16] * Joins: zcorpan (n=zcorpan@c83-252-193-59.bredband.comhem.se)
  1473. # [22:17] * Quits: ROBOd (n=robod@89.122.216.38) ("http://www.robodesign.ro")
  1474. # [22:17] * Quits: roc (n=roc@121-72-179-27.dsl.telstraclear.net)
  1475. # [22:19] <zcorpan> why can't i edit bugs in w3c bugzilla?
  1476. # [22:19] <annevk42> did mike(tm) gave you editbugs?
  1477. # [22:19] <zcorpan> no?
  1478. # [22:20] <annevk42> that's your answer
  1479. # [22:20] <zcorpan> ok
  1480. # [22:20] <annevk42> you can ask him, if it's something trivial i can make the change for you now
  1481. # [22:21] <annevk42> s/,/ for editbugs,/
  1482. # [22:21] <zcorpan> i wanted to make the summary shorter for http://www.w3.org/Bugs/Public/show_bug.cgi?id=7639
  1483. # [22:21] * Quits: pmuellr (n=pmuellr@nat/ibm/x-opunbrvlxwioqslx)
  1484. # [22:24] <annevk42> done
  1485. # [22:25] <zcorpan> thanks
  1486. # [22:31] * Joins: cying (n=cying@70.90.171.153)
  1487. # [22:33] * Joins: cohitre (n=cohitre@dhcp-0061496037-dc-9f.client.fas.harvard.edu)
  1488. # [22:35] <Philip`> Is anyone going to point out the squirrely aria-describedby error on the list?
  1489. # [22:36] * Quits: BlurstOfTimes (n=blurstof@168.203.117.59) ("Leaving...")
  1490. # [22:37] * Quits: cohitre (n=cohitre@dhcp-0061496037-dc-9f.client.fas.harvard.edu) (Client Quit)
  1491. # [22:38] <Dashiva> Doesn't look like it
  1492. # [22:38] <Dashiva> Go ahead if you want to
  1493. # [22:38] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  1494. # [22:39] * Joins: erlehmann (n=erlehman@tmo-109-179.customers.d1-online.com)
  1495. # [22:39] <annevk42> maybe we should put some money on the number of hours until when it comes out and John realizes he's wrong
  1496. # [22:40] <othermaciej> why did Opera add longdesc support anyway?
  1497. # [22:41] <othermaciej> do you guys have data on it being useful, or customer requests, or the like?
  1498. # [22:41] <annevk42> I'd ask chaals
  1499. # [22:41] * annevk42 doesn't really know
  1500. # [22:42] <othermaciej> was chaals involved in the decision, or are you just saying he's likely to know stuff like that in general?
  1501. # [22:43] <annevk42> both, I think
  1502. # [22:43] * Quits: zalan (n=zalan@catv-89-135-144-193.catv.broadband.hu) (Read error: 110 (Connection timed out))
  1503. # [22:43] <annevk42> (at least as far a11y goes)
  1504. # [22:44] * Joins: weinig (n=weinig@17.246.16.129)
  1505. # [22:45] <zcorpan> the impl doesn't work so well for longdesc="#description", however that doesn't work so well in jaws either so maybe it's good to discourage authors from doing that
  1506. # [22:45] <Philip`> Dashiva: I'm happy to leave it for someone else, rather than getting involved
  1507. # [22:46] <Philip`> I presume if the page was unfixed, and then Opera implemented aria-describedby taking precedence over longdesc, the page's description would become inaccessible
  1508. # [22:46] <Philip`> So: Don't implement ARIA, it will demonstrably hurt accessibility
  1509. # [22:49] * Joins: dave_levin (n=dave_lev@74.125.59.65)
  1510. # [22:57] * Joins: cardona507 (n=cardona5@c-67-180-160-250.hsd1.ca.comcast.net)
  1511. # [23:00] * Joins: sicking (n=chatzill@nat/mozilla/x-qsuzoachnsayslhf)
  1512. # [23:01] <zcorpan> maybe he'd find the mistake if he validated against html5 "Error: The aria-describedby attribute must point to an element in the same document."
  1513. # [23:03] * Quits: Hish (n=chatzill@212.23.139.152) (Read error: 131 (Connection reset by peer))
  1514. # [23:04] <zcorpan> hmm. does the spec make document.createElement('isindex') an HTMLElement rather than HTMLUnknownElement by listing it in the obsolete section?
  1515. # [23:04] * Joins: Hish (n=chatzill@212.23.139.152)
  1516. # [23:06] * Quits: ap_ (n=ap@17.246.19.174) (Remote closed the connection)
  1517. # [23:07] * Joins: ap (n=ap@nat/apple/x-mubolunlzcrbdrse)
  1518. # [23:12] * Joins: roc (n=roc@203-97-204-82.dsl.clear.net.nz)
  1519. # [23:13] <gsnedders> zcorpan: I'd say yes, but that does seem horrifically underdefined
  1520. # [23:14] * Joins: jacobolus (n=jacobolu@dhcp-0000104152-52-5b.client.student.harvard.edu)
  1521. # [23:17] * aroben|away is now known as aroben
  1522. # [23:19] * Quits: Maurice (i=copyman@5ED548D4.cable.ziggo.nl)
  1523. # [23:22] * zcorpan considers switching to dt/dd for figure on one of his sites, but concludes that he's too lazy to rewrite the relevant parts of the script and style sheet and retest
  1524. # [23:25] * Quits: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com) (Remote closed the connection)
  1525. # [23:25] <zcorpan> what's a browser supposed to do with <details><dt>x<dd>y<dd>z</details>?
  1526. # [23:25] <zcorpan> always show z?
  1527. # [23:25] * Parts: clarjon1 (n=clarjon1@unaffiliated/clarjon1) ("Nice Scotty, now beam my clothes up too!")
  1528. # [23:26] * Joins: Perceptes (n=Percepte@cpe-76-88-38-155.san.res.rr.com)
  1529. # [23:26] * Quits: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net) (Read error: 104 (Connection reset by peer))
  1530. # [23:27] * Joins: Rik`_ (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  1531. # [23:27] <annevk42> zcorpan, either always show z or always show y
  1532. # [23:27] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  1533. # [23:27] <zcorpan> "The first dd element child of the element, if any, represents the details."
  1534. # [23:28] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Client Quit)
  1535. # [23:30] <zcorpan> the rendering section will make everything but the first dt element hidden
  1536. # [23:31] <beowulf> is jeremy keith not a SuperFriend?
  1537. # [23:31] <annevk42> zcorpan, I filed a bug on that
  1538. # [23:31] <beowulf> ach, nm
  1539. # [23:32] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  1540. # [23:32] * Quits: Hish (n=chatzill@212.23.139.152) (Read error: 131 (Connection reset by peer))
  1541. # [23:32] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Client Quit)
  1542. # [23:33] * Joins: Hish (n=chatzill@212.23.139.152)
  1543. # [23:33] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  1544. # [23:34] <zcorpan> annevk2: ah. me too :)
  1545. # [23:34] * Quits: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  1546. # [23:35] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Client Quit)
  1547. # [23:35] * zcorpan notes that the rendering section relies on case-insensitivity for attribute value selectors
  1548. # [23:36] * Joins: tantek (n=tantek@67.180.202.79)
  1549. # [23:36] <annevk42> sigh
  1550. # [23:36] <annevk42> maybe we cannot remove that then
  1551. # [23:42] * Quits: Rik`_ (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net) (Read error: 104 (Connection reset by peer))
  1552. # [23:42] * Quits: Hish (n=chatzill@212.23.139.152) (Read error: 104 (Connection reset by peer))
  1553. # [23:42] * Joins: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  1554. # [23:43] * Joins: Hish (n=chatzill@mail2.n-e-s.de)
  1555. # [23:44] <zcorpan> css specs should reference mimesniff
  1556. # [23:46] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  1557. # [23:47] <zcorpan> btw, philipj discovered that code reuse in browsers has caused 'load' and 'error' events to be fired on elements when using e.g. css border-image or video poster
  1558. # [23:48] * Quits: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net) (Client Quit)
  1559. # [23:52] * Joins: cohitre (n=cohitre@c-98-216-107-106.hsd1.ma.comcast.net)
  1560. # [23:54] * Joins: Hish_ (n=chatzill@mail2.n-e-s.de)
  1561. # [23:55] * Quits: Hish_ (n=chatzill@mail2.n-e-s.de) (Read error: 104 (Connection reset by peer))
  1562. # [23:55] * Quits: erlehmann (n=erlehman@tmo-109-179.customers.d1-online.com) ("Ex-Chat")
  1563. # [23:56] * Philip` tries to work out how you're meant to take Opera out of F11-style fullscreen view, when viewing a fullscreen Flash plugin
  1564. # [23:56] <Philip`> because the plugin has focus and intercepts the F11 key
  1565. # [23:56] <Philip`> and it's fullscreen so there's no browser chrome left to click on and focus :-/
  1566. # [23:57] * Joins: Hish_ (n=chatzill@mail2.n-e-s.de)
  1567. # [23:57] <Philip`> s/fullscreen Flash plugin/normal embedded Flash plugin which fills 100% of the screen/
  1568. # [23:58] * Quits: Hish_ (n=chatzill@mail2.n-e-s.de) (Read error: 104 (Connection reset by peer))
  1569. # [23:59] <roc> zcorpan: did anyone file a Mozilla bug on that?
  1570. # [23:59] * Joins: Hish_ (n=chatzill@mail2.n-e-s.de)
  1571. # Session Close: Wed Sep 16 00:00:00 2009

The end :)