/irc-logs / freenode / #whatwg / 2009-08-11 / end

Options:

  1. # 
  2. # Session Start: Tue Aug 11 00:00:00 2009
  3. # Session Ident: #whatwg
  4. # [00:00] <sicking> Hixie, i.e. could clearState have any effect even if pushState has never been called?
  5. # [00:00] <Hixie> it includes that, it includes URLs that come from navigating by hand, everything
  6. # [00:00] <Hixie> yes
  7. # [00:00] <Hixie> at least, per spec, iirc
  8. # [00:00] <sicking> Hixie, heh
  9. # [00:00] <Hixie> (whether that's desireable or not is a different question)
  10. # [00:00] <sicking> Hixie, is there a reason for this? I can't really think of a reason one way or another on this
  11. # [00:00] <Hixie> i honestly have no idea off the top of my head
  12. # [00:00] <Hixie> i'd need to look at it closer
  13. # [00:00] <sicking> ok
  14. # [00:01] <Hixie> send mail asking me to if you want to know for sure
  15. # [00:01] <sicking> ok, we might
  16. # [00:01] <sicking> justin lebar is pretty far into an implementation of all of this
  17. # [00:02] <sicking> the plan is to get an implementation and then unleash developers on it to see what makes sense
  18. # [00:02] * Joins: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  19. # [00:03] * Quits: weinig_ (n=weinig@17.246.18.83)
  20. # [00:03] <Hixie> nice
  21. # [00:03] <Hixie> feedback would be very welcome on this
  22. # [00:08] * Joins: tantekc (n=tantekc@69.38.253.114)
  23. # [00:11] * Quits: smedero (n=smedero@D-69-91-162-77.dhcp4.washington.edu)
  24. # [00:11] * Quits: ttepasse (n=ttepas--@p5B017653.dip.t-dialin.net) ("?Q")
  25. # [00:14] * Quits: tantekc (n=tantekc@69.38.253.114)
  26. # [00:15] * Joins: dglazkov_ (n=dglazkov@nat/google/x-1c73effc6c1c8209)
  27. # [00:16] * Quits: dglazkov_ (n=dglazkov@nat/google/x-1c73effc6c1c8209) (Remote closed the connection)
  28. # [00:16] * Joins: dglazkov_ (n=dglazkov@nat/google/x-4d4ed9efb5f44cf6)
  29. # [00:17] * Quits: dglazkov (n=dglazkov@nat/google/x-b46723a2d810f3f1) (Read error: 104 (Connection reset by peer))
  30. # [00:18] * Quits: tantekc_ (n=tantekc@69.38.253.114) (Read error: 113 (No route to host))
  31. # [00:18] * dglazkov_ is now known as dglazkov
  32. # [00:25] * Quits: Frances (n=phaeness@cpc2-acto9-0-0-cust364.brnt.cable.ntl.com)
  33. # [00:26] * Quits: paul_irish (n=paul_iri@12.33.239.250)
  34. # [00:31] * Joins: weinig (n=weinig@17.246.18.83)
  35. # [00:34] * Quits: weinig (n=weinig@17.246.18.83) (Remote closed the connection)
  36. # [00:34] * Joins: weinig (n=weinig@nat/apple/x-5b46ea28d3de79c3)
  37. # [00:38] * Joins: bgalbraith (n=bgalbrai@nat/mozilla/x-9b229dd2c3a043ea)
  38. # [00:39] * Joins: SamerZ (n=SamerZ@CPE0024369ef3ab-CM001ac35cd4b4.cpe.net.cable.rogers.com)
  39. # [00:44] * Quits: olliej (n=oliver@17.246.17.250)
  40. # [00:44] * Quits: hobertoAtWork (n=hobertoa@gw1.mcgraw-hill.com) ("Nettalk6 - www.ntalk.de")
  41. # [00:46] * Joins: smedero (n=smedero@D-69-91-229-112.dhcp4.washington.edu)
  42. # [00:47] * Quits: aroben|meeting (n=aroben@unaffiliated/aroben) ("Leaving")
  43. # [00:48] * Quits: BlurstOfTimes (n=blurstof@168.203.117.59) ("Leaving...")
  44. # [00:51] * Quits: SamerZ (n=SamerZ@CPE0024369ef3ab-CM001ac35cd4b4.cpe.net.cable.rogers.com)
  45. # [00:55] * Joins: SamerZ (n=SamerZ@CPE0024369ef3ab-CM001ac35cd4b4.cpe.net.cable.rogers.com)
  46. # [00:58] * Joins: paulgendek (n=paulgend@240.182.205.68.cfl.res.rr.com)
  47. # [01:03] * Joins: heycam (n=cam@clm-laptop.infotech.monash.edu.au)
  48. # [01:03] <paulgendek> hello
  49. # [01:03] <paulgendek> what is the intended use of <header> and <footer>, is header intended to be semantic for <div id="header">? or is it section headers only like <div class="main-top">, etc. it's my understanding that if <header> is used as <div id="header"> then we will have to still use id="header" to denote that it is the header for body, not header for any other sections, like <section id="content"><header>
  50. # [01:03] <paulgendek> continued: it would seem to be more semantic to have the header of a layout specified as <section id="header"> since it is the "header" section of the layout, and not specifically a header container for <body>
  51. # [01:03] <paulgendek> <section id="header">, container, sidebar, footer, etc. these are all <sections> in of a design, as we design semantic markup just as we design CSS as well
  52. # [01:05] <paulgendek> typically we have <div class="post"> and within we would have <div class="post-top"> or whatever, denoting a top/header container for a post, we could do the same for footer, so is <header> only to be used for this purpose?
  53. # [01:05] <paulgendek> as a "section header" and not the header of a design
  54. # [01:05] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  55. # [01:09] <hober> In HTML5 as currently specced, <header> can be used as the header of many elements, including <body>, <article>, <section>, and the like.
  56. # [01:09] <hober> I don't see why "we will have to still use ..."
  57. # [01:10] <paulgendek> for practical css designs
  58. # [01:10] <hober> just use selectors that pull out the relevant elements
  59. # [01:10] <paulgendek> first child and > don't work in ie6
  60. # [01:10] <hober> consider <body><header>...</header><article><header>...</header>...</article>...</body>
  61. # [01:10] <paulgendek> for body > header
  62. # [01:10] <inimino> IE6 is hardly relevant in the HTML5 timeframe
  63. # [01:11] <hober> the "article header" selector works fine in all relevant browsers, no?
  64. # [01:11] <inimino> for many people IE6 isn't worth supporting even now
  65. # [01:12] <paulgendek> i work for a major publishing company and there is still a significant percentage of ie6 users across all of our brands, of over US magazines
  66. # [01:12] <paulgendek> which is a pretty wide range of diverse niches
  67. # [01:13] <paulgendek> so it seems like it would still need to be supported for some time longer, even though the fight is going pretty strong lately
  68. # [01:13] <paulgendek> and there is a lot of html5 website development moving rapidly
  69. # [01:14] <paulgendek> so i'm worried about moving forward, the problem is that we _need_ id specific selectors for layout structural elements
  70. # [01:14] <hober> you could leave out "layout structural" in that sentence
  71. # [01:14] <paulgendek> so header, content, sidebar, footer, should all be <sections>
  72. # [01:14] <paulgendek> and would still need id's
  73. # [01:15] <hober> there are lots of designs which require the use of class="" and/or id="" in browsers with impoverished selector support
  74. # [01:15] <hober> this isn't a spec bug
  75. # [01:15] <hober> and has nothing to do with the elements you're talking about
  76. # [01:15] * Quits: kinetik (n=kinetik@121.98.132.55) (Read error: 60 (Operation timed out))
  77. # [01:16] * Joins: olliej (n=oliver@17.246.17.250)
  78. # [01:16] <paulgendek> understood, but i don't understand using <header id="header"> and <section id="content"> and being more semantic and organized in the xml style
  79. # [01:16] <hober> I definitely don't follow how you get from "I'll need to use class='' or id='' in some cases" to "we shouldn't have these elements at all"
  80. # [01:16] <hober> err, I don't understand what you just wrote.
  81. # [01:17] <paulgendek> i mean header and footer in the sense of the location of the design/structure of the site, not the actual <header> element.... <header>/<footer> make a lot of sense being the top/bottom containers for <sections>/<articles> etc
  82. # [01:17] <paulgendek> but it doesn't make sense being used as the header container in a design
  83. # [01:18] <paulgendek> i feel that after body, should be sections... and in the #header section, you can have a header/footer, hgroup, inner content, etc
  84. # [01:18] <hober> I don't follow. It makes just as much sense to use <header> as the header for a <body> element as it does to use it as the header for some other sectioning element.
  85. # [01:18] <paulgendek> and if the design requires wrapping containers around sections, divs are used
  86. # [01:18] <hober> sometimes you'll need to distinguish different <header> elements on the page for styling purposes, so we have class="" and id="", but this also applies to all other elements in the language.
  87. # [01:19] <hober> e.g. <em class="rfc2119">should</em> might be styled differently than <em>should</em>
  88. # [01:19] <hober> that doesn't mean we need two separate elements
  89. # [01:21] * Quits: SamerZ (n=SamerZ@CPE0024369ef3ab-CM001ac35cd4b4.cpe.net.cable.rogers.com)
  90. # [01:22] <paulgendek> it just seems like it's redundant to have <header> within the body and still need to add id="header" 90%+ of the time in real-world cases than to group all the "header" items of a design into <section id="header">, would it then make sense to have <header> under body but place a <section> within it to apply the structural/layout id ?
  91. # [01:23] * Joins: kinetik (n=kinetik@121.98.132.55)
  92. # [01:23] <hober> Let's assume I have a page with one <body>, one <header> child of <body>, and several <article> and <section> elements with their own <header>s.
  93. # [01:24] <paulgendek> <header> seems more appropriate at meaning to the top section of the parent element... and using it under <body> would mean the same thing... so then body > header would be appropriate for accessibility links, "skip to", etc, and you would then still have <section id="header">
  94. # [01:24] <hober> the number of <header> elements that require distinguishing with class="" or id="" (in browsers with impoverished selector support) in such as case is more like 10%, not 90%.
  95. # [01:26] <paulgendek> if you write css targeting header, and you want to design the header of the layout, you would need to use body > header selector... which is a lot more to type (ridiculous but practical) and not natively supported in ie6
  96. # [01:26] <Hixie> wtf, http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408!OpenDocument&;Click=
  97. # [01:26] <Hixie> the hard copy of sRGB is cheaper than the PDF!
  98. # [01:27] <hober> what's wrong with <body><header id="foo">...</header><article><header>...</header>...</article>...</body>?
  99. # [01:28] <beowulf> you can select that without a class or id, obviously
  100. # [01:29] <paulgendek> so a 3-col page layout would be header, section.col, section.col, section.col, footer?
  101. # [01:31] <paulgendek> hober: in most cases, at least in my experience with magazine-layout/blog websites, is that the dom is never that simply constructed
  102. # [01:31] * Quits: tndH (n=Rob@cpc2-leed18-0-0-cust427.leed.cable.ntl.com) ("ChatZilla 0.9.85-rdmsoft [XULRunner 1.9.0.1/2008072406]")
  103. # [01:32] <hober> I'd probably use <div> for the columns in such a layout
  104. # [01:32] <paulgendek> i guess that is what i'm looking for... what is the "holy grail" for common floating column page layouts in the html5 world?
  105. # [01:32] <paulgendek> in base structure
  106. # [01:34] <paulgendek> i may be confusing myself here :P
  107. # [01:34] <hober> body { column-count: 3; column-gap: 2em; }?
  108. # [01:34] <paulgendek> hober: in a perfect world
  109. # [01:34] <hober> I was joking :)
  110. # [01:34] <paulgendek> haha
  111. # [01:34] <paulgendek> hoped so
  112. # [01:35] <hober> I think the real answer is something handwavy like "use the most semantically appropriate element for your context, or <div>/<span> if none exists"
  113. # [01:35] <Hixie> 31 to go
  114. # [01:35] <hober> cont. "then layer on additional/more precise semantics with class=''"
  115. # [01:37] <paulgendek> idk, i think this looks much more elegant: http://www.grabup.com/uploads/418240ad1cf963160cc003c2b76cd0fe.png?direct
  116. # [01:40] <paulgendek> and if the h-tags are used in order, along with hgroups when needed, and within <header> tags... it would be practical to design with css, and be semantic...
  117. # [01:40] <paulgendek> am i missing something?
  118. # [01:44] <hober> paulgendek: I think I would have marked that up more like so: http://paste.lisp.org/display/85165
  119. # [01:45] <deltab> Hixie: with the PDF they have to send someone out to colour-calibrate your screen
  120. # [01:46] <Hixie> 26 to go...
  121. # [01:46] <Hixie> deltab: hah
  122. # [01:48] * Quits: kristallpirat (n=kristall@c-base/crew/kristall) ("Wünsche weiterhin guten Flug")
  123. # [01:53] <paulgendek> hober: that really makes me uncomfortable with theming complicated website headers and everything is targeting a first-child or > selector body header:first-child or body > header.... there WILL need to be an id there, and <header id="header"> is redundant
  124. # [01:53] * Joins: rubys (n=rubys@cpe-098-027-052-152.nc.res.rr.com)
  125. # [01:58] * Joins: SamerZ (n=SamerZ@CPE0024369ef3ab-CM001ac35cd4b4.cpe.net.cable.rogers.com)
  126. # [02:03] <paulgendek> are there any documented best practices?
  127. # [02:06] <paulgendek> i consider the header of a design to be sectioning content, not flow content, but that the section contains flow content
  128. # [02:06] <paulgendek> i meant, i consider the header container of a design
  129. # [02:09] * Joins: webben (n=benh@dip5-fw.corp.ukl.yahoo.com)
  130. # [02:14] <paulgendek> would this be appropriate for use today? http://www.grabup.com/uploads/46007d0ff9e19b933047f0eb0cc05ced.png?direct
  131. # [02:15] <paulgendek> using sections with id's for sectioning content, but still using <header>/<footer> in their section containers
  132. # [02:16] <paulgendek> the section element is the only element that is spec'd to be bolth flow content and sectioning content categories
  133. # [02:16] <paulgendek> s/bolth/both
  134. # [02:18] <paulgendek> besides article, aside, and nav, of course
  135. # [02:20] * Quits: SamerZ (n=SamerZ@CPE0024369ef3ab-CM001ac35cd4b4.cpe.net.cable.rogers.com)
  136. # [02:20] * Quits: ap (n=ap@nat/apple/x-1bfe4623f0d3b0f9)
  137. # [02:24] * Quits: dglazkov (n=dglazkov@nat/google/x-4d4ed9efb5f44cf6)
  138. # [02:24] * Parts: rubys (n=rubys@cpe-098-027-052-152.nc.res.rr.com)
  139. # [02:25] <paulgendek> or you would use header, nav, article, aside, footer for the sectioning
  140. # [02:25] <paulgendek> anyone?
  141. # [02:29] <smedero> i've always though <header> & <footer> were more compelling when nested inside an <article> or a <section> than when used in a traditional website template header & footer model.
  142. # [02:31] <smedero> i agree <header id="header"> is annoying and relying on selectors could be problematic with large CMS deployments that have a lot of hands in the pot.
  143. # [02:32] * Quits: dbaron (n=dbaron@nat/mozilla/x-e927d0818ffce3a2) ("8403864 bytes have been tenured, next gc will be global.")
  144. # [02:37] * Joins: wakaba__ (n=wakaba_@122x221x184x68.ap122.ftth.ucom.ne.jp)
  145. # [02:37] <Hixie> 18 to go...
  146. # [02:37] <paulgendek> smedero: here's a template that i'm working with, let me know what you think: http://www.grabup.com/uploads/8b5623a6613dafd5dfd99df70b7081a9.png?direct
  147. # [02:42] * Joins: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  148. # [02:42] * Joins: Rik`_ (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  149. # [02:44] <smedero> on a first pass that only thing I had to go back and re-read the spec on was <hgroup>.
  150. # [02:45] <paulgendek> smedero: i've altered the h-tags throughout slightly, for seo: http://www.grabup.com/uploads/b6e7062958f481eb4088d747c23f2cc3.png?direct
  151. # [02:46] * Quits: bgalbraith (n=bgalbrai@nat/mozilla/x-9b229dd2c3a043ea)
  152. # [02:48] <Hixie> woo, all done
  153. # [02:48] <smedero> wrt <header id="header">. Many layouts I see about, the "page header" tends to have it is own "header" and "footer" so-to-speak... so I really think <section> is most appropriate there (because you can't nest a <footer> in <header>... or at least you couldn't last I read that section.)
  154. # [02:50] <paulgendek> thank you smedero
  155. # [02:50] <paulgendek> that was very helpful
  156. # [02:52] * Quits: jacobolus (n=jacobolu@c-98-248-43-68.hsd1.ca.comcast.net) (Remote closed the connection)
  157. # [02:55] * Joins: webben_ (n=benh@91.85.213.95)
  158. # [02:56] * Quits: smedero (n=smedero@D-69-91-229-112.dhcp4.washington.edu)
  159. # [02:59] * Quits: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net) (Read error: 113 (No route to host))
  160. # [03:06] * Quits: cying (n=cying@70.90.171.153)
  161. # [03:07] * Quits: webben (n=benh@dip5-fw.corp.ukl.yahoo.com) (Read error: 110 (Connection timed out))
  162. # [03:08] * Quits: paulgendek (n=paulgend@240.182.205.68.cfl.res.rr.com)
  163. # [03:09] * Quits: virtuelv (n=virtuelv@201.169.34.95.customer.cdi.no) (Read error: 110 (Connection timed out))
  164. # [03:13] * Joins: bgalbraith (n=bgalbrai@71.202.109.116)
  165. # [03:18] * Quits: bgalbraith (n=bgalbrai@71.202.109.116) (Client Quit)
  166. # [03:18] * Joins: abii (n=macbook@cm27.delta30.maxonline.com.sg)
  167. # [03:20] * Quits: jennb (n=jennb@72.14.227.1)
  168. # [03:21] * Joins: khmer42 (n=chatzill@218.100.51.20)
  169. # [03:23] <khmer42> Does anyone know if any of the broswers (including dev versions) currently have an implementation of the websockets specification?
  170. # [03:23] * Quits: dave_levin (n=dave_lev@72.14.227.1)
  171. # [03:23] * Joins: SamerZ (n=SamerZ@CPE0024369ef3ab-CM001ac35cd4b4.cpe.net.cable.rogers.com)
  172. # [03:24] <Hixie> khmer42: webkit and gecko are working on it, dunno if they have anything testable yet
  173. # [03:27] <khmer42> Hixie: Thanks. Do you know if without using comet techniques is there anything else that we can work against (even if it doesn't follow the spec) until someone has got an implementation out? I'm thinking Gears/Adobe AIr/browser plugins.
  174. # [03:27] <Hixie> i expect flash has something like this
  175. # [03:28] <khmer42> After watching the Google Wave demo, I thought websockets had been released into the wild. Google must be using long polling or something, well I suppose they do have the resources :-)
  176. # [03:32] <khmer42> Yep I see Flash has XMLSocket, I'll see if anyone else has made JS lib to bridge the WebSockets spec to this, if not I'll have a stab at it myself.
  177. # [03:39] * Quits: olliej (n=oliver@17.246.17.250)
  178. # [03:40] <inimino> khmer42: look at Orbited, they had something very similar
  179. # [03:40] <Hixie> gsnedders|work: nevermind, i did the biblio filtering myself
  180. # [03:41] * Quits: iugrina (n=iugrina@brale.math.hr) (Read error: 104 (Connection reset by peer))
  181. # [03:44] <khmer42> inimino: Thanks, I checked them out before and also Kazing but looked like they were using long polling that imitated a socket. We don't have the servers to scale that solution.
  182. # [03:55] * Quits: Creap (n=Creap@vemod.brg.sgsnet.se) (Read error: 104 (Connection reset by peer))
  183. # [03:57] <inimino> khmer42: yes, it is long polling
  184. # [04:15] * Joins: taf2 (n=taf2@216-15-54-105.c3-0.grg-ubr3.lnh-grg.md.cable.rcn.com)
  185. # [04:17] <franksalim> khmer42, at Kaazing, we have done what you are talking about
  186. # [04:18] <franksalim> khmer42, we use flash's socket (not the xml socket, but the tcp one) and bridge to javascript. if we can't use flash, then we try http streaming. then long polling only as a last resort
  187. # [04:19] <franksalim> *(xml messages over tcp. xml vs. tcp doesn't make any sense.)
  188. # [04:19] <khmer42> franksalim: Sounds interesting, I will got check it out. Is it a complete port of the websocket spec so it will just be ignored in future as websocket compliant browsers come into play?
  189. # [04:20] <franksalim> khmer42, yes. it first checks for native websocket
  190. # [04:21] * Joins: othermaciej_ (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  191. # [04:21] * Quits: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  192. # [04:21] <khmer42> franksalim: Cool, I had a play with Kaazing last year and like where it was heading. Is the front end JavaScript API independent of any server products you have? (if you have such products)
  193. # [04:22] <franksalim> khmer42, no, there is a single product
  194. # [04:27] * Joins: cying (n=cying@adsl-75-18-223-3.dsl.pltn13.sbcglobal.net)
  195. # [04:32] * Quits: SamerZ (n=SamerZ@CPE0024369ef3ab-CM001ac35cd4b4.cpe.net.cable.rogers.com)
  196. # [04:33] * Joins: dbaron (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net)
  197. # [04:44] * Joins: yutak (n=yutak@220.109.219.244)
  198. # [04:46] * Quits: archtec2 (n=sv@83.228.56.37) (Read error: 60 (Operation timed out))
  199. # [04:49] * Quits: taf2 (n=taf2@216-15-54-105.c3-0.grg-ubr3.lnh-grg.md.cable.rcn.com)
  200. # [04:51] * Joins: jacobolus (n=jacobolu@user-64-9-236-189.googlewifi.com)
  201. # [04:53] * Joins: dimich (n=dimich@72.14.227.1)
  202. # [04:54] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  203. # [05:01] * Quits: dimich_ (n=dimich@72.14.227.1) (Read error: 110 (Connection timed out))
  204. # [05:03] * Joins: jacobolu_ (n=jacobolu@user-64-9-236-189.googlewifi.com)
  205. # [05:03] * Quits: jacobolus (n=jacobolu@user-64-9-236-189.googlewifi.com) (Read error: 104 (Connection reset by peer))
  206. # [05:11] * Joins: paulgendek (n=paulgend@240.182.205.68.cfl.res.rr.com)
  207. # [05:20] * jacobolu_ is now known as jacobolus
  208. # [05:24] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  209. # [05:30] * Joins: olliej (n=oliver@76.14.73.3)
  210. # [05:33] * Joins: Code_Bleu_ (n=chatzill@64-191-149-154.service.qx.net)
  211. # [05:34] * Quits: vs-hs (n=vs-hs@shell.etttretresju.net) (Client Quit)
  212. # [05:34] * Joins: vs-hs (i=david@shell.etttretresju.net)
  213. # [05:36] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  214. # [05:36] <paulgendek> why can't <nav> be inside of <footer> ?
  215. # [05:42] * Quits: jorlow (n=jorlow@nat/google/x-9ca2694f8a9fd1b9)
  216. # [05:52] <Code_Bleu_> for those of you using Twitter, I created a "Twibbon" overlay for your avatar. Sorry if this is inappropriate to do..just thought you might like to show your support. http://twibbon.com/join/WHATWG---HTML5
  217. # [05:53] * Joins: dimich_ (n=dimich@c-98-203-252-208.hsd1.wa.comcast.net)
  218. # [05:53] * Quits: khmer42 (n=chatzill@218.100.51.20) (Remote closed the connection)
  219. # [05:53] * Quits: dimich_ (n=dimich@c-98-203-252-208.hsd1.wa.comcast.net) (Client Quit)
  220. # [05:54] * Joins: dimich_ (n=dimich@c-98-203-252-208.hsd1.wa.comcast.net)
  221. # [05:56] * Joins: darbour (n=Rachel@c-98-216-48-49.hsd1.ma.comcast.net)
  222. # [05:56] * Parts: darbour (n=Rachel@c-98-216-48-49.hsd1.ma.comcast.net)
  223. # [05:56] * Joins: ap (n=ap@c-24-130-131-182.hsd1.ca.comcast.net)
  224. # [06:01] * Quits: Code_Bleu_ (n=chatzill@64-191-149-154.service.qx.net) ("ChatZilla 0.9.85 [Firefox-3.5 3.5.2/20090808154447]")
  225. # [06:05] <othermaciej_> So far I am really enjoying Microsoft's new more active participation in the WG
  226. # [06:14] * Quits: ginger (n=nessy@124-171-241-171.dyn.iinet.net.au) ("This computer has gone to sleep")
  227. # [06:21] * Joins: jorlow (n=jorlow@72.14.224.1)
  228. # [06:23] * Joins: stefanschipor (n=stefansc@78.96.155.118)
  229. # [06:26] <stefanschipor> Has anyone tried using new html5 elements like article with css pseudo-class selectors (I'm trying first-child)? I'm running FF 3.5 and it doesn't seem to work.
  230. # [06:27] * Quits: jorlow (n=jorlow@72.14.224.1)
  231. # [06:27] * Quits: michaeln1 (n=michaeln@nat/google/x-7116163ddbe39c9d) ("Leaving.")
  232. # [06:27] <stefanschipor> btw, if this is the wrong place or way to ask the question please correct me. new here
  233. # [06:33] * Quits: jwalden (n=waldo@nat/mozilla/x-ca03fde61517a8bf) ("->home")
  234. # [06:38] * Joins: jacobolu_ (n=jacobolu@user-64-9-239-232.googlewifi.com)
  235. # [06:41] * Joins: jorlow (n=jorlow@72.14.224.1)
  236. # [06:41] * Joins: bgalbraith (n=bgalbrai@71.202.109.116)
  237. # [06:49] <othermaciej_> I haven't tried it
  238. # [06:49] <othermaciej_> did you check if the <article> element ends up in the DOM properly?
  239. # [06:50] * othermaciej_ is now known as othermaciej
  240. # [06:50] * Quits: jacobolus (n=jacobolu@user-64-9-236-189.googlewifi.com) (Read error: 110 (Connection timed out))
  241. # [06:52] * Joins: jwalden (n=waldo@c-98-248-40-206.hsd1.ca.comcast.net)
  242. # [07:03] * Quits: bgalbraith (n=bgalbrai@71.202.109.116)
  243. # [07:11] * Quits: dbaron (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net) ("8403864 bytes have been tenured, next gc will be global.")
  244. # [07:15] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  245. # [07:18] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  246. # [07:26] <stefanschipor> that's it :) I had a h1 before the articles which was hidden so I kinda missed it. thanks a lot! :)
  247. # [07:28] * Joins: tantek (n=tantek@ool-4570acce.dyn.optonline.net)
  248. # [07:28] * Joins: tantekc (n=tantekc@ool-4570acce.dyn.optonline.net)
  249. # [07:31] <othermaciej> did Mozilla drop their <a ping> implementation?
  250. # [07:31] <othermaciej> I can't remember what happened with that
  251. # [07:32] <paulgendek> if anyone is bored and would like to critique: http://paulgendek.com/html5/ html5 blog layout, validates, with some hcard microformats...
  252. # [07:32] <paulgendek> going to do single article view with <dialog> for comments
  253. # [07:33] * Quits: roc (n=roc@203-97-204-82.dsl.clear.net.nz)
  254. # [07:34] * jacobolu_ is now known as jacobolus
  255. # [07:34] * Joins: wakaba___ (n=wakaba_@112-68-212-111.eonet.ne.jp)
  256. # [07:39] <tantek> paulgendek - looks like Optimus likes your microformats: http://microformatique.com/optimus/?format=validate&uri=http%3A//paulgendek.com/html5/
  257. # [07:40] <paulgendek> tantek: :) i also added a few hResume tags, although i don't know what will pick up on it
  258. # [07:40] <tantek> I think microtron might
  259. # [07:41] <paulgendek> tantek: is it running anywhere?
  260. # [07:41] <paulgendek> online
  261. # [07:42] * Quits: tantekc (n=tantekc@ool-4570acce.dyn.optonline.net) (Read error: 104 (Connection reset by peer))
  262. # [07:42] * Joins: tantekc_ (n=tantekc@ool-4570acce.dyn.optonline.net)
  263. # [07:44] * Joins: tantekc (n=tantekc@ool-4570acce.dyn.optonline.net)
  264. # [07:45] * Quits: tantekc_ (n=tantekc@ool-4570acce.dyn.optonline.net) (Read error: 104 (Connection reset by peer))
  265. # [07:47] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  266. # [07:49] <othermaciej> ok, I proposed actually closing some issue tracker issues
  267. # [07:50] <othermaciej> let's see if it works!
  268. # [07:50] <tantekc> othermaciej - your proposed closures seem reasonable to me.
  269. # [07:50] * Quits: wakaba__ (n=wakaba_@122x221x184x68.ap122.ftth.ucom.ne.jp) (Read error: 113 (No route to host))
  270. # [07:53] * Quits: jacobolus (n=jacobolu@user-64-9-239-232.googlewifi.com) (Remote closed the connection)
  271. # [07:54] <hsivonen> othermaciej: I think I saw the code for implementing @ping last month
  272. # [07:54] <hsivonen> my guess is that the code is there but preffed off
  273. # [07:55] <othermaciej> hsivonen: do you know if Mozilla has any intent to actually ship the feature?
  274. # [07:55] <hsivonen> othermaciej: I know nothing about intent
  275. # [07:55] <othermaciej> hsivonen: that's what I was hoping to flush out
  276. # [07:56] * Quits: cying (n=cying@adsl-75-18-223-3.dsl.pltn13.sbcglobal.net)
  277. # [08:00] <Hixie> i imagine chrome will want to support it eventually
  278. # [08:00] <Hixie> though i doubt it's a priority
  279. # [08:01] <Hixie> (ping="" could dramatically improve the performance of google search while improving the user's ability to control his privacy, which are both things google cares very much about)
  280. # [08:02] * Quits: weinig (n=weinig@nat/apple/x-5b46ea28d3de79c3)
  281. # [08:04] * Quits: Rik`_ (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  282. # [08:05] * Joins: Mrmil (n=ut_ollie@host-77-236-204-8.blue4.cz)
  283. # [08:07] <Hixie> othermaciej: re ARIA, I don't think we have any reason to believe the ARIA group isn't working at the fastest rate possible
  284. # [08:08] <othermaciej> Hixie: at the last HTML WG telecon, someone (who I think was a PFWG member) they said they would not give a reply to your issue for 2-3 months
  285. # [08:08] <Hixie> oh
  286. # [08:08] <Hixie> well then aria won't make LC
  287. # [08:08] <Hixie> we can always do it after LC
  288. # [08:08] <othermaciej> I don't care if it's the fastest rate possible, it's clearly not acceptable
  289. # [08:09] <Hixie> is there a rush?
  290. # [08:09] <othermaciej> (they said they want to do that so they can address all LC comments at once)
  291. # [08:09] <Hixie> do they realise that the odds are that the LC comments will get further replies from people saying "i'm not happy with this..."
  292. # [08:09] <Hixie> ?
  293. # [08:09] <othermaciej> I'm not sure they thought it through
  294. # [08:09] <othermaciej> I guess they want to make sure all their answers consider all comments... or something
  295. # [08:10] * Quits: olliej (n=oliver@76.14.73.3)
  296. # [08:10] <othermaciej> given when you sent your comment, 2-3 months from now would result in a 6 month response time from them
  297. # [08:10] <othermaciej> which I think is unacceptable for meaningful coordination
  298. # [08:11] <othermaciej> also, I think ARIA missing LC is totally an option for the WHATWG, but probably would not fly in the HTML WG (it's possible the WG would vote to agree that ARIA can wait until after first LC, but I wouldn't bet on it)
  299. # [08:11] <Hixie> it's far less than the time it took me to reply to the e-mails i was replying to today
  300. # [08:12] <othermaciej> that is true, but you reply to emails that are specifically cast as urgent requests much faster than that
  301. # [08:12] <Hixie> yeah well i'm not expecting the HTMLWG to actually reach LC until the WHATWG is ready for CR, at the rate the chairs are running the group
  302. # [08:12] <Hixie> sure
  303. # [08:12] * Joins: roc (n=roc@121-72-200-124.dsl.telstraclear.net)
  304. # [08:13] <othermaciej> in case you haven't noticed - I'm trying to change the way the chairs are running the HTML WG for pretty much that reason
  305. # [08:13] <Hixie> good luck
  306. # [08:13] <othermaciej> I'll need it :-(
  307. # [08:14] * Joins: jacobolus (n=jacobolu@adsl-75-36-149-231.dsl.pltn13.sbcglobal.net)
  308. # [08:15] <Hixie> i expect that they're working on this weekly cycle now, because of the telecon
  309. # [08:15] <Hixie> so you'll not hear anything until thursday or whenever the telecons are
  310. # [08:15] <Hixie> this is another reason i hate telecons -- people end up paralysed and unable to make decisions without holding the phone in their hands
  311. # [08:16] <othermaciej> I do not enjoy anything about telecons
  312. # [08:17] <othermaciej> If the issues I suggested for immediate closure get closed on Thursday, or, hell, even a week from Thursday, that will still be better than I am expecting
  313. # [08:17] <Hixie> me too
  314. # [08:23] <hsivonen> othermaciej: IIRC, I have sent some unresponded-to ARIA feedback in March 2008 (before ARIA went to LC). My preference would be for PFWG to send out replies as soon as they know what they are going to say.
  315. # [08:23] <othermaciej> hsivonen: if I understood what was said on the telecon correctly, they want to defer deciding what they are going to say until they have had time to consider every single issue
  316. # [08:24] <hsivonen> othermaciej: it seems to me, that key questions regarding inclusion by reference into HTML 5 hinge on the "Implementors' Guide" side--not necessarily on "ARIA 1.0"
  317. # [08:24] <othermaciej> that doesn't seem like a good approach to me, but I'd rather just send a WG-to-WG request for expedited processing
  318. # [08:25] <othermaciej> hsivonen: what do you think are the key questions?
  319. # [08:25] <hsivonen> othermaciej: UA implementation requirements
  320. # [08:25] <hsivonen> othermaciej: and I think the UA implementation requirements have some bearing on what makes sense to author
  321. # [08:26] <othermaciej> hsivonen: can you give a specific example?
  322. # [08:26] <hsivonen> othermaciej: what must an UA do with <input type=radio checked role=checkbox aria-checked=false>
  323. # [08:27] <othermaciej> hsivonen: I think regardless of the UA implementation requirements, that markup should be non-conforming
  324. # [08:27] <hsivonen> othermaciej: I agree, but that's just our opinion
  325. # [08:28] <othermaciej> hsivonen: sure, but I don't think the Implementor's Guide will affect our opinion one way or the other
  326. # [08:28] * Joins: webben (n=benh@dip5-fw.corp.ukl.yahoo.com)
  327. # [08:28] <othermaciej> Here's why I think so.
  328. # [08:28] <hsivonen> othermaciej: it will affect HTML 5 plus its normative references having UA implmentation reqs
  329. # [08:30] <othermaciej> (A) ARIA can't (by its own goals and scope) require anything different than HTML5 for display and behavior of that markup other than through accessibility APIs - so that markup has to be rendered as a checked radio button for normal visual interactive use.
  330. # [08:30] * Quits: ap (n=ap@c-24-130-131-182.hsd1.ca.comcast.net)
  331. # [08:30] <othermaciej> (B) ARIA Implementor's Guide can specify two possible behaviors for that markup from an accessibility POV:
  332. # [08:30] <othermaciej> (1) The conflicting ARIA markup is ignored.
  333. # [08:30] * Quits: heycam (n=cam@clm-laptop.infotech.monash.edu.au) ("bye")
  334. # [08:31] <othermaciej> (2) The conflicting ARIA markup means that the checked radio button is expressed as an unchecked checkbox through screen readers and such.
  335. # [08:31] * Joins: pesla (n=retep@procurios.xs4all.nl)
  336. # [08:31] <othermaciej> clearly neither of B.1 or B.2 is likely to be intended or good behavior, so either way the markup should be nonconforming
  337. # [08:31] <othermaciej> now, it might be that we think B.2 is bad UA behavior on its own terms, but that seems like a separate issue from authoring conformance
  338. # [08:32] * Joins: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  339. # [08:32] <othermaciej> I personally would expect B.1 to be a little bit easier to implement, but perhaps more complex to specify
  340. # [08:32] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Remote closed the connection)
  341. # [08:33] * Joins: SamerZ (n=SamerZ@CPE002129bd5f2a-CM0014e8b57926.cpe.net.cable.rogers.com)
  342. # [08:33] <hsivonen> othermaciej: it seems that there's disagreement on what's easier: B.1 or B.2
  343. # [08:34] <hsivonen> othermaciej: IIRC, Aaron Leventhal advocated position B.2
  344. # [08:34] <othermaciej> hsivonen: neither is completely trivial
  345. # [08:34] * Joins: wakaba__ (n=wakaba_@112-68-212-111.eonet.ne.jp)
  346. # [08:34] <othermaciej> personally I'd be willing to implement either, if it's considered as error-handling behavior
  347. # [08:35] <othermaciej> (the hard part of B.1 is explicitly ignoring certain aria roles, states and properties in particular cases)
  348. # [08:35] * Joins: dave_levin (n=dave_lev@c-98-203-247-78.hsd1.wa.comcast.net)
  349. # [08:36] <othermaciej> (the hard part of B.2 is explicitly ignoring built-in behavior of the element when certain aria roles/states are set)
  350. # [08:38] <othermaciej> I think there's other examples where it's not clear to me how B.1 or B.2 would dictate the UA behavior
  351. # [08:38] <othermaciej> for example: <input type=radio checked aria-checked=false>
  352. # [08:39] <othermaciej> I guess it's mainly a problem for position B.2, for B.1 the answer is clear
  353. # [08:39] <othermaciej> but in the case of B.2, does the aria state still apply, even though there is no relevant role defined?
  354. # [08:39] <othermaciej> or, conversely: <input type=radio checked role=checkbox>
  355. # [08:39] * Joins: gunderwonder (n=gunderwo@172.80-202-84.nextgentel.com)
  356. # [08:40] <othermaciej> under B.2, does ARIA report that as a checked checkbox, or a checkbox with no defined checked state at all?
  357. # [08:42] * Quits: wakaba___ (n=wakaba_@112-68-212-111.eonet.ne.jp) (Read error: 110 (Connection timed out))
  358. # [08:43] <hsivonen> no idea
  359. # [08:44] * Quits: webben_ (n=benh@91.85.213.95) (Read error: 110 (Connection timed out))
  360. # [08:44] * Joins: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl)
  361. # [08:45] * Quits: SamerZ (n=SamerZ@CPE002129bd5f2a-CM0014e8b57926.cpe.net.cable.rogers.com)
  362. # [08:46] * Joins: nessy (n=nessy@124-171-241-171.dyn.iinet.net.au)
  363. # [08:49] * Joins: gsnedders (n=gsnedder@c83-252-194-54.bredband.comhem.se)
  364. # [08:52] <paulgendek> is there an issue with 'figure legend' ? it's in the source but firebug doesn't see the legend, font is inherited from figure
  365. # [08:52] <Hixie> yeah <figure> doesn't work in most browsers yet
  366. # [08:53] <paulgendek> is there a javascript fix for that yet?
  367. # [08:53] <Hixie> dunno
  368. # [08:53] <paulgendek> thx
  369. # [08:54] <Hixie> if there is, nobody has updated the issue marker at http://www.whatwg.org/specs/web-apps/current-work/#the-legend-element yet
  370. # [08:54] <Hixie> (the fifth icon in those boxes represents js implementations)
  371. # [08:55] <hsivonen> What document conformance rules is Optimus based on?
  372. # [09:00] * Quits: gunderwonder (n=gunderwo@172.80-202-84.nextgentel.com)
  373. # [09:03] <Lachy> othermaciej, why didn't you suggest closing ISSUE-4?
  374. # [09:03] <Lachy> (html-versioning)
  375. # [09:04] <othermaciej> Lachy: I personally think it should be closed with no change to the spec, but there has been continuing debate and Larry intends to make a proposal
  376. # [09:04] <othermaciej> Lachy: so I'm leaving that one in the hands of the chairs
  377. # [09:04] <Lachy> ok
  378. # [09:04] <Philip`> Hixie: #refsE163 and #refsRFC2965 are still missing
  379. # [09:05] <Hixie> i just fixed 2965
  380. # [09:05] <Hixie> E163 is there though
  381. # [09:05] <othermaciej> paulgendek: there's a problem with parsing of <legend> in all existing browsers, and you can't practically use <figure> with backup styling until it is fixed
  382. # [09:05] <othermaciej> paulgendek: I raised the issue with Hixie but he was not inclined to increase the number of elements in HTML to fix it
  383. # [09:06] <Hixie> <figure>'s not important enough. just pretend that it's not in html5 and that we added it 3 years from now.
  384. # [09:06] <othermaciej> Lachy: I tried to limit my suggested closures to thinks that it's just painfully obvious should be closed, and where there has not really been discussion to the contrary
  385. # [09:07] <Lachy> othermaciej, any idea when the <legend> parsing issues will be fixed in webkit?
  386. # [09:07] <othermaciej> once all browsers either adopt HTML5 parsing or at least change parsing of <legend> not found in a <fieldset>, <figure> will be practically usable
  387. # [09:08] <Hixie> on a completely different note, does anyone want to volunteer to take point on the encoding aliases issue?
  388. # [09:08] <othermaciej> Lachy: at the very latest, when we adopt HTML5 parsing, but I will propose doing it sooner
  389. # [09:08] <Lachy> Hixie, what's the issue?
  390. # [09:08] <Hixie> lachy: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-July/021207.html
  391. # [09:08] <Philip`> Hixie: I don't see E163 there
  392. # [09:08] <Philip`> e.g. http://www.whatwg.org/specs/web-apps/current-work/#refsE163 doesn't exist
  393. # [09:08] <Philip`> (but is referenced)
  394. # [09:08] <Hixie> Philip`: hm, odd
  395. # [09:09] <Hixie> it's in the source
  396. # [09:09] <Hixie> wonder what broke
  397. # [09:11] <Lachy> Hixie, what specifically needs to be done? Do we need to update the IANA registry?
  398. # [09:12] <Hixie> Lachy: yeah
  399. # [09:12] <Hixie> Lachy: basically i want to remove the "Additional character encoding aliases" table
  400. # [09:12] <Hixie> Lachy: and just have hte IANA registry be all up to date
  401. # [09:13] <Hixie> Philip`: wtf
  402. # [09:13] <Lachy> ok. I don't have time to do it right now, but if no-one else volunteers within a few weeks, I might be able to do it
  403. # [09:14] <Hixie> k
  404. # [09:14] <Lachy> what's the process for updating the IANA registry?
  405. # [09:14] <Hixie> depends on the registry; i haven't looked into what it takes to update that one
  406. # [09:16] <Hixie> given this line: href="#refsE163">[E163]</a> <a href="#refsX121">[X121]</a></p>
  407. # [09:16] <othermaciej> Hixie, hsivonen: does either of you think it is useful to continue tracking this as an issue: http://www.w3.org/html/wg/tracker/issues/17
  408. # [09:17] <Hixie> why does this not match two things: while ($substedline =~ m/\G.*href="#refs([^"]+)"/osg) {
  409. # [09:18] <Lachy> Looks like it will take a few e-mails to this list http://www.iana.org/assignments/charset-info
  410. # [09:18] <hsivonen> othermaciej: depends on what MQ says now. I'll have to check
  411. # [09:19] <Lachy> http://tools.ietf.org/html/rfc2978
  412. # [09:19] <othermaciej> would it be inappropriate spamming if I suggested a bunch more issue closures?
  413. # [09:19] <othermaciej> I am doing one per message to associate them in the issue tracker
  414. # [09:19] <Lachy> othermaciej, doesn't the issue tracker allow one message to be associated with multiple issues?
  415. # [09:20] <othermaciej> Lachy: I don't know - I'm counting on the automated detection of ISSUE-nn in the subject
  416. # [09:20] <Hixie> othermaciej: we fixed that years ago
  417. # [09:20] <hsivonen> othermaciej: as far as I can tell, the MQ WS issue still stands
  418. # [09:20] <Lachy> looks like it does
  419. # [09:21] <Hixie> othermaciej: (U+000B isn't a whitespace character anymore in HTML5)
  420. # [09:21] <othermaciej> is it fixed in HTML5?
  421. # [09:21] <hsivonen> Hixie: oh
  422. # [09:21] <Lachy> see http://www.w3.org/html/wg/tracker/issues/1 and http://www.w3.org/html/wg/tracker/issues/4 -- your last mail appears in both
  423. # [09:21] <hsivonen> Hixie: nice
  424. # [09:21] <hsivonen> I wonder how I forgot
  425. # [09:21] <Hixie> i'd forgotten too
  426. # [09:21] <Hixie> i just checked :-)
  427. # [09:21] <Hixie> had to look up wtf vertical tab was first
  428. # [09:22] <othermaciej> Lachy: is it searching the text?
  429. # [09:22] <hsivonen> othermaciej: so yeah, the issue has been addressed. No point in keeping it open.
  430. # [09:22] <Lachy> othermaciej, yes
  431. # [09:22] <othermaciej> Lachy: do you think it would be better to gang them up?
  432. # [09:22] <Lachy> yes
  433. # [09:22] * Joins: heycam (n=cam@203-217-71-141.dyn.iinet.net.au)
  434. # [09:23] * Quits: sebmarkbage (n=miranda@h-6-72.A146.priv.bahnhof.se) ("http://calyptus.eu/")
  435. # [09:23] <Philip`> Hixie: Because the .* is greedy and will match the whole first href, I expect
  436. # [09:24] <Philip`> Hixie: You probably want .*?
  437. # [09:24] <Hixie> ohhh!
  438. # [09:24] <Hixie> yes
  439. # [09:24] <Hixie> thanks
  440. # [09:25] * Joins: olliej (n=oliver@76.14.73.3)
  441. # [09:26] * Philip` would just use "while ($substedline =~ /href="#refs([^"]+)"/g)" which works the same and has fewer funny characters
  442. # [09:27] <Hixie> there's an implied \G?
  443. # [09:27] <Hixie> i always had problems using /g
  444. # [09:27] <othermaciej> Hixie: is there anything to do in response to this: http://www.w3.org/html/wg/tracker/issues/26
  445. # [09:28] <Hixie> (without the \G, i mean)
  446. # [09:28] <othermaciej> (it appears to be suggestions for accessibility of the spec text itself)
  447. # [09:28] <Hixie> for one of those things we're waiting for gsnedders to add features to anolis
  448. # [09:29] <Hixie> i can't read the bottom two paragraphs, they're too "wall of text" for me
  449. # [09:29] <Hixie> i guess i have a disability, and whoever wrote that doesn't know how to write accessible comments :-)
  450. # [09:29] <hsivonen> what's still pending about issue 37?
  451. # [09:29] <othermaciej> #3 explains why hex/rgb colors are supposed to be bad
  452. # [09:29] <hsivonen> also, wasn't issue 54 addressed long ago?
  453. # [09:30] * Quits: stefanschipor (n=stefansc@78.96.155.118)
  454. # [09:30] <Hixie> Philip`: ok fixed, thanks for catching that
  455. # [09:30] <hsivonen> issue 60 is not realistically actionable
  456. # [09:31] * Joins: gunderwonder (n=gunderwo@garage.upstruct.com)
  457. # [09:31] <othermaciej> #4 in issue-26 looks too vague to be actionable
  458. # [09:31] * Quits: gunderwonder (n=gunderwo@garage.upstruct.com) (Read error: 104 (Connection reset by peer))
  459. # [09:31] <Lachy> issue 60 should have been closed at the telcon a month ago. It was kept open for silly reasons
  460. # [09:31] <othermaciej> I guess I won't suggest closing it if there are anolis changes planned which will help
  461. # [09:31] * Joins: gunderwonder (n=gunderwo@garage.upstruct.com)
  462. # [09:31] <othermaciej> hsivonen: I don't understand why 37 is open, indeed
  463. # [09:32] <othermaciej> also I thought 54 was addressed
  464. # [09:32] <hsivonen> Is anyone but Larry expressing active interest in keeping issue 4 open?
  465. # [09:32] <othermaciej> and 60 should obviously be closed in light of the news about the XHTML2 WG
  466. # [09:32] <Lachy> issue 54 is pending the registration of the about: URI scheme
  467. # [09:32] * Joins: Creap (n=Creap@vemod.brg.sgsnet.se)
  468. # [09:33] <Lachy> I haven't heard from Joseph in a while, so I don't know what he's doing about that RFC
  469. # [09:33] <othermaciej> hsivonen: no idea - I would hope the chairs would make some assessment of who has objections
  470. # [09:34] <Philip`> Hixie: It's similar to an implied \G, except it starts where the previous execution of the current regexp on the current string left off, whereas \G starts where the previous regexp on the current string left off (even if it's a different regexp)
  471. # [09:35] <Philip`> Hixie: (so \G is useful when chaining multiple regexps together, and /g works fine if you're just looping over a single one)
  472. # [09:35] <Hixie> Philip`: ah, i see. yeah, i usually use /g with multiple regexps, that's why i had trouble without \G.
  473. # [09:35] <Hixie> Philip`: thanks.
  474. # [09:35] * Quits: olliej (n=oliver@76.14.73.3)
  475. # [09:36] * Quits: jwalden (n=waldo@c-98-248-40-206.hsd1.ca.comcast.net) ("ChatZilla 0.9.85 [Firefox 3.5.3pre/20090809031611]")
  476. # [09:37] <othermaciej> do these remain issues of controversy (it's not clear to me from the issue tracker item what the point is): <http://www.w3.org/html/wg/tracker/issues/27> <http://www.w3.org/html/wg/tracker/issues/28>
  477. # [09:37] <Hixie> for 27, i'm fine with the WHATWG registry, but others are probably not
  478. # [09:37] <Philip`> Hixie: (Also the /o is redundant unless you've got interpolated variables in the regexp, and the /s is redundant since you're only processing a single line)
  479. # [09:38] <Hixie> 28 is fixed by abarth's mimesniff draft
  480. # [09:38] <Philip`> Hixie: (Also you should get rid of all the pesky whitespace and variable names, they're just wasting bytes :-( )
  481. # [09:38] <gsnedders> othermaciej: Anolis changes for #4 in issue-26?
  482. # [09:38] <Hixie> Philip`: yeah i just always include /o and /s
  483. # [09:38] <gsnedders> othermaciej: Or one of the others?
  484. # [09:38] <othermaciej> gsnedders: Hixie mentioned that something in http://www.w3.org/html/wg/tracker/issues/26 is waiting on anolis changes - I do not know what he had in mind
  485. # [09:38] <gsnedders> ah, yeah
  486. # [09:38] <Hixie> Philip`: /s actually isn't redundant here, one of the operations that makes $line into $substedline can introduce more lines
  487. # [09:38] <othermaciej> Hixie: does the HTML5 spec completely defer to mimesniff now?
  488. # [09:39] <Hixie> othermaciej: yeah
  489. # [09:39] <Hixie> othermaciej: where appropriate, anyway
  490. # [09:39] * gsnedders wonders where in the multi-level feedback queue of his to-do list that is
  491. # [09:40] <gsnedders> oh, there
  492. # [09:40] * gsnedders shrugs, and heads off to work
  493. # [09:40] <Philip`> Hixie: Oh, okay
  494. # [09:40] * Joins: tndH (n=Rob@cpc2-leed18-0-0-cust427.leed.cable.ntl.com)
  495. # [09:40] <gsnedders> Hixie: I'll try and work out the encoding change today though
  496. # [09:40] <Philip`> Hixie: Clearly you shouldn't use such confusing variable names like "$substedline", and should try to put absolutely everything into $_
  497. # [09:41] <Hixie> gsnedders: i don't mind the encoding change at all
  498. # [09:41] <gsnedders> Hixie: I do. You specify US-ASCII and get UTF-8.
  499. # [09:41] <Hixie> Philip`: this is nested inside several loops, one of which uses $_ :-)
  500. # [09:41] <Hixie> gsnedders: k :-)
  501. # [09:42] <gsnedders> Hixie: If you specify US-ASCII, you should get US-ASCII.
  502. # [09:42] <gsnedders> I spoke to jgraham about it briefly yesterday, I suspect it is in the PMS code the bug :P
  503. # [09:42] <heycam> Hixie, what do you expect calling mutator methods like setHours() on a Date object returned from HTMLTimeElement.time and friends to do?
  504. # [09:42] <heycam> anything?
  505. # [09:43] * Joins: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  506. # [09:43] <Hixie> gsnedders: can i specify cross-spec cross refs and get those too? :-)
  507. # [09:43] * gsnedders stabs Hixie
  508. # [09:44] <Lachy> gsnedders, great, now who will edit the spec?
  509. # [09:44] <Hixie> manu, apparently
  510. # [09:44] <gsnedders> Lachy: I didn't say I killed him, or harmed him that much.
  511. # [09:44] <Hixie> heycam: i expect the Date object to be a real Date object with no relationship to the underlying attribute
  512. # [09:44] <heycam> ok, so a new one gets returned every time you access it?
  513. # [09:44] <Hixie> yeah
  514. # [09:44] <heycam> ok you'll need to say that i think
  515. # [09:44] <gsnedders> Lachy: Just a bit of knife play :P
  516. # [09:45] <Hixie> heycam: can you add a comment in the comment box to that effect and hit the button? it'll file a bug for you
  517. # [09:45] <heycam> sure
  518. # [09:45] * Philip` hopes gsnedders used a stab-proof knife
  519. # [09:46] * Quits: jorlow (n=jorlow@72.14.224.1)
  520. # [09:47] <jgraham> He just used one of those plasic toy knives where the blade goes in
  521. # [09:47] * Quits: gsnedders (n=gsnedder@c83-252-194-54.bredband.comhem.se)
  522. # [09:48] <heycam> Hixie, i'm still not sure of the usefulness of having separate date/time/timezone attributes
  523. # [09:48] <heycam> it might be better to have one Date and then booleans to state whether certain parts were present
  524. # [09:48] <Lachy> Philip`, are they anything like those useless plastic, cut-proof scissors often given to children so they can't cut themselves, or paper?
  525. # [09:49] <Hixie> heycam: it seems that whatever you do, you're going to have to end up creating these Date objects for yourself, typically
  526. # [09:49] <Hixie> heycam: having just these dates seems as useful or more than one date and booleans
  527. # [09:50] <Philip`> Lachy: They're like http://www.foxnews.com/story/0,2933,526590,00.html
  528. # [09:52] <Lachy> the claim about them being inneffective as a weapon seems a little inaccurate
  529. # [09:52] <heycam> Hixie, I suppose I'd like to see use cases to convince me. maybe i'll send mail about it.
  530. # [09:52] <Lachy> they may not be effective for stabbing due to the blunt end, but they look to be perfectly effective for slitting someone's throat
  531. # [09:53] <heycam> btw are <time>s meant to represent an instance in time or an instance in time and an associated time zone?
  532. # [09:53] <othermaciej> they seem unlikely to reduce the risk of injuries
  533. # [09:53] <othermaciej> most accidental knife injuries while cooking are from the edge, not the point
  534. # [09:54] <Hixie> heycam: heycam: a date, a time, or an instance in time with time zone
  535. # [09:54] <Philip`> othermaciej: It seems it's designed to reduce injuries when e.g. a burglar breaks into your house and you disturb him and he grabs the nearest knife and stabs you, not when cooking
  536. # [09:54] <heycam> Hixie, ok. currently the spec says only "The time element represents a precise date and/or a time in the proleptic Gregorian calendar."
  537. # [09:55] <othermaciej> Philip`: s/injuries/accidental injuries/
  538. # [09:55] <othermaciej> it might prevent deliberate stabbings, but it would also prevent self-defense with a knife
  539. # [09:55] <Philip`> (Presumably it's no good for premeditated attacks, because you've have to be pretty stupid to intentionally take a stab-proof knife to stab someone with)
  540. # [09:55] <othermaciej> then again, the UK doesn't believe in self-defense any more
  541. # [09:56] <Hixie> bbiab
  542. # [09:56] <Lachy> it may not be effecitve for stabbing, but slicing attacks are still as effective as before
  543. # [09:57] <Lachy> unless they make it blunt on the edge as well
  544. # [09:57] <Philip`> Were slicing attacks still effective before?
  545. # [09:57] <Philip`> I imagine they're much harder to do
  546. # [09:57] <Philip`> and much harder to cause fatal injuries
  547. # [09:57] <othermaciej> if you are any good at knife fighting you can mess up an attacker really bad, probably fatally
  548. # [09:57] <Lachy> just grab someone from behind, hold the knife to their throat and slice
  549. # [09:57] <othermaciej> or if you are strong enough to overpower someone, you can cut their throat or the like
  550. # [09:58] * Lachy notes that discussing murdering techniques is a new low for this channel :-)
  551. # [09:58] <othermaciej> just slashing at the arms of someone coming for you, they will quickly reach a point where they are likely to bleed to death
  552. # [09:58] <othermaciej> (forearms)
  553. # [10:00] <Philip`> Hmm, seems more difficult and situational than just shoving the knife into someone's chest and then running off before anyone notices you
  554. # [10:01] <Philip`> (Mostly this is in the context of e.g. http://www.telegraph.co.uk/news/newstopics/politics/2078201/Gordon-Brown-urges-tougher-punishments-for-teenage-knife-crime.html and not trained knife fighters)
  555. # [10:08] * Joins: foolip (n=philip@pat.se.opera.com)
  556. # [10:11] * Quits: webben (n=benh@dip5-fw.corp.ukl.yahoo.com) (Read error: 104 (Connection reset by peer))
  557. # [10:16] * Joins: MadAtWork (n=not_@ip-113-239.static.adsl.cheapnet.it)
  558. # [10:28] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  559. # [10:34] * Joins: archtech (n=sv@83.228.56.37)
  560. # [10:36] * Quits: Rik` (n=Rik`@pha75-2-81-57-187-57.fbx.proxad.net)
  561. # [10:36] <jgraham> I guess the main use case for the stab-proof knife is "violent hasband flies into a rage and attacks wife"
  562. # [10:36] <jgraham> *husband
  563. # [10:37] <gsnedders|work> Are you calling myself and Hixie husband and wife? :\
  564. # [10:37] * Joins: maikmerten (n=merten@ls5dhcp196.cs.uni-dortmund.de)
  565. # [10:38] <hsivonen> I'd like to have stab-proof knives just to mitigate the consequences of dropping a knife
  566. # [10:38] * jgraham shan't enquire which recesses of gsnedders psyche caused him to infer that
  567. # [10:38] <hsivonen> I wonder if the stab-proof knives will be delayed by 20 due to a patent
  568. # [10:39] <hsivonen> *20 years
  569. # [10:40] <gsnedders|work> jgraham: Well, I seemingly often attack Hixie in a rage…
  570. # [10:40] * gsnedders|work thinks something is a bit backwards though, seeming he's the one wearing a girls T-shirt
  571. # [10:41] <GPHemsley> well, this is an interesting conversation to walk into...
  572. # [10:43] <hsivonen> it's inappropriate for use cases to assign gender to attacker and victim
  573. # [10:43] <gsnedders|work> GPHemsley: See /topic :)
  574. # [10:44] <GPHemsley> you people really should have a logic detector at the entrance
  575. # [10:44] <GPHemsley> you can't expect me to remember to voluntarily relinquish it every time I come in here
  576. # [10:44] * hsivonen also thinks non-violent discourse without stabbing would be good on #whatwg
  577. # [10:44] * Quits: dimich_ (n=dimich@c-98-203-252-208.hsd1.wa.comcast.net)
  578. # [10:46] <hsivonen> aargh. I just realized that if nodes have been moved from a document to another during the parse, the HTML5 parser in Gecko notifies the subsequent child insertion on the wrong document
  579. # [10:46] <hsivonen> fixing that in a performant way seems like a can of worms
  580. # [10:48] <hsivonen> I guess I need to ship a pointer to the parser's doc to each tree operation
  581. # [10:48] <hsivonen> sigh.
  582. # [10:53] <hsivonen> hey. Theora support has migrated from Chrome dev channel to beta channel
  583. # [10:53] <hsivonen> nice
  584. # [10:55] * Joins: ROBOd (n=robod@89.122.216.38)
  585. # [10:55] * Quits: Lachy (n=Lachlan@85.196.122.246) ("This computer has gone to sleep")
  586. # [10:56] * Joins: webben (n=benh@nat/yahoo/x-3a252b4ddd664024)
  587. # [10:56] * Joins: Lachy (n=Lachlan@85.196.122.246)
  588. # [11:00] * Quits: tyoshino (n=tyoshino@220.109.219.244) ("Leaving...")
  589. # [11:06] * Joins: mat_t (n=mattomas@nat/canonical/x-a792fe205bef80c3)
  590. # [11:34] <hsivonen> I wonder how hard it would be to generate static status markers from the WHATWG dynamic status marker data
  591. # [11:35] <jgraham> hsivonen: Not hard but possibly not worthwhile either.
  592. # [11:36] <jgraham> I can't imagine that it would make people happy
  593. # [11:37] <othermaciej> status markers are a bit of a sideshow
  594. # [11:37] <othermaciej> issues need to actually be resolved in some final way - it's only the total lack of closure on anything in the HTML WG that makes people play games with publishing WD and adding status markers and such
  595. # [11:39] <jgraham> Indeed. I would rather we spent time resolving issues than shuffling little red boxes around
  596. # [11:39] <hsivonen> jgraham: it seems to me that autogenerating the markers into the W3C snapshots would address the issue Manu's draft is said to address
  597. # [11:39] <hsivonen> I agree that actully resolving issues is better
  598. # [11:40] <hsivonen> hmm. looks like Wikipedia now tells a bogus story about video codec debate as far as dates of events go
  599. # [11:41] * Quits: dave_levin (n=dave_lev@c-98-203-247-78.hsd1.wa.comcast.net)
  600. # [11:46] * Quits: MadAtWork (n=not_@ip-113-239.static.adsl.cheapnet.it) (Read error: 110 (Connection timed out))
  601. # [11:47] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  602. # [11:52] * Joins: Lachy_ (n=Lachy@pat-tdc.opera.com)
  603. # [11:55] * Joins: annevk42 (n=annevk@ABordeaux-156-1-31-53.w86-213.abo.wanadoo.fr)
  604. # [12:01] * Quits: Creap (n=Creap@vemod.brg.sgsnet.se) (Remote closed the connection)
  605. # [12:15] * Quits: Lachy_ (n=Lachy@pat-tdc.opera.com) ("Leaving")
  606. # [12:33] * Quits: tantek (n=tantek@ool-4570acce.dyn.optonline.net)
  607. # [12:51] <Philip`> http://www.exalead.com/search/web/results/?q=html5 - wow, a site that actually uses SVG for real
  608. # [12:52] <Philip`> (in the Languages/Countries pie charts)
  609. # [12:53] * Joins: Lachy_ (n=Lachy@pat-tdc.opera.com)
  610. # [12:53] <pablof> Philip`: http://www.opera.com/company/jobs/ ;-)
  611. # [12:57] <Philip`> Oh, looks like they didn't write the SVG themselves, they just used http://raphaeljs.com/
  612. # [13:07] * Joins: wakaba___ (n=wakaba_@112-68-212-111.eonet.ne.jp)
  613. # [13:12] * Joins: wakab____ (n=wakaba_@122x221x184x68.ap122.ftth.ucom.ne.jp)
  614. # [13:17] * Quits: wakaba___ (n=wakaba_@112-68-212-111.eonet.ne.jp) (Read error: 60 (Operation timed out))
  615. # [13:23] * Joins: StefanShipor (n=StefanSh@78.96.155.118)
  616. # [13:24] * Quits: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  617. # [13:25] * Quits: wakaba__ (n=wakaba_@112-68-212-111.eonet.ne.jp) (Read error: 110 (Connection timed out))
  618. # [13:26] <StefanShipor> hey people! could you take a look at http://bearditch.com/stuff/debate.html and give your 2cents about the markup. Would you structure it differently? It's for a general tabbed content section of a site. If you have the time or mood ofc.
  619. # [13:32] <hsivonen> http://twitter.com/mattur
  620. # [13:34] * Quits: Richardigel (n=igel@247-72.60-188.cust.bluewin.ch)
  621. # [13:34] <paulgendek> hsivonen: followed...
  622. # [13:36] <paulgendek> StefanShipor: looks pretty good!
  623. # [13:37] * Joins: Richardigel (n=igel@247-72.60-188.cust.bluewin.ch)
  624. # [13:38] <jgraham> paulgendek, StefanShipor: You may find http://gsnedders.html5.org/outliner/ useful in assessing whether you are using sectioning elements in the right way
  625. # [13:39] <paulgendek> cool, thanks!
  626. # [13:40] <jgraham> paulgendek: In your case I think you have too many sibling <section>s
  627. # [13:40] <StefanShipor> jgraham: but why do the untitled sections appear? http://gsnedders.html5.org/outliner/process.py?url=http%3A%2F%2Fbearditch.com%2Fstuff%2Fdebate.html
  628. # [13:40] <StefanShipor> I waas expecting only one since it doesn't have a heading
  629. # [13:42] <jgraham> StefanShipor: You have a <body> with no heading, a <nav> with no heading at the top and two <nav>s with no heading further down
  630. # [13:42] <paulgendek> <nav> should have <heading> within?
  631. # [13:42] <jgraham> (FWIW I think that the approach to sections with no heading in the spec needs to change)
  632. # [13:43] <jgraham> paulgendek: Theoretically, yes
  633. # [13:44] <paulgendek> i stared at my dom for a few hours and couldn't think of any other ways of ordering elements, etc. it seems like the most practical for a real world solution, as a base theme, etc
  634. # [13:44] <jgraham> paulgendek: e.g. you miught say <nav><h1>Blogroll</h1></nav>
  635. # [13:45] <jgraham> paulgendek: In yoour specific case, I think you want to structure the page so that the main page header is outside of the <section>s
  636. # [13:45] <paulgendek> that doesn't make sense, because from what i read, you would put the h-tags in the <header>, followed by the <nav>
  637. # [13:46] * Quits: archtech (n=sv@83.228.56.37)
  638. # [13:46] <jgraham> Like <body><header><h1>My blog</h1></header><nav></nav><article><h1>My post</h1></article>
  639. # [13:46] <paulgendek> i think body's header should be reserved for accessibility links, in a magazine/blog layout
  640. # [13:47] <StefanShipor> there will be lots of navs on sites for navigation through posts and such. I hope they don't leave the heading inside nav mandatory
  641. # [13:47] <jgraham> I don't know what you mean by accessibility links really (do you mean "skip to content" type links?) but that seems like a strange belief
  642. # [13:47] <StefanShipor> cause if you fave "older" and "newer" it's already pretty self-explanatory
  643. # [13:48] <StefanShipor> have*
  644. # [13:48] <paulgendek> it's nowhere near 2022, we still need to be practical here...
  645. # [13:48] <paulgendek> in 2009/2010, i still need skip to content links
  646. # [13:49] <paulgendek> may be a want, idk
  647. # [13:49] <jgraham> paulgendek: Maybe, I'm not sure what the state of the art in AT is in this regard. But I see no readon why that precludes having a header for the body
  648. # [13:50] <paulgendek> because in modern web design, where we have containers, centered, with borders, padding, maybe even nested with special corners, etc
  649. # [13:50] <paulgendek> the body header should be reserved for top-most content
  650. # [13:51] <jgraham> What is the title of your blog if not topmost content?
  651. # [13:51] <paulgendek> like an admin bar that is position absolute, or leaderboard ads that are outside of the centered/bordered container, or the accessibility links that are hidden for screen
  652. # [13:51] * Joins: tantek (n=tantek@ool-4570acce.dyn.optonline.net)
  653. # [13:52] * StefanShipor is now known as StefanSchipor
  654. # [13:53] <jgraham> In any case, at the very least the articles on the page should be nested below the main page title otherwise your markup has the wrong structure (which will show up as an incorrect outline)
  655. # [13:53] <paulgendek> we can agree that title of the blog should be an h1, which will take its order correctly just by being an h1... let it be in section#header's header with the site slogan, logo, and primary nav... better for designing real website header sections
  656. # [13:54] <jgraham> paulgendek: That's not how headers work in HTML5
  657. # [13:54] <gsnedders|work> paulgendek: Why should one section's header apply to one of its siblings?
  658. # [13:54] <jgraham> Any header can be a <h1> as long as you get the structual elements right
  659. # [13:55] <paulgendek> or for the sake of having a clean outline, and the elements where they need to be in the dom for design, should we then hide the h1 in body header, and use an h2 for the logo in the actual header section of the design?
  660. # [13:55] <gsnedders|work> paulgendek: Why is it a section, even?
  661. # [13:55] <paulgendek> because it's a page layout section
  662. # [13:55] <jgraham> Note that <header> is not a sectioning element
  663. # [13:55] <paulgendek> "header, content, sidebar, footer"
  664. # [13:55] <hsivonen> about.validator.nu, etc. going down now
  665. # [13:56] <paulgendek> exactly, section is sectioning, which is why i apply the id to sections, for building the page structure
  666. # [13:56] <gsnedders|work> paulgendek: "section" is _not_ a page layout section. It is a semantic section.
  667. # [13:56] <paulgendek> gsnedders|work: the spec says that it's flow AND structural
  668. # [13:56] <jgraham> Doing <body><section><header><h1>My blog instead of <body><header><h1>My blog is both unnecessary and wrong
  669. # [13:57] <jgraham> Unless you further nest all other content in that outer section
  670. # [13:57] <paulgendek> headers are only for sections and articles
  671. # [13:57] <gsnedders|work> the body is a section.
  672. # [13:57] <paulgendek> body's header is reserved for top content imo
  673. # [13:58] <paulgendek> at least, in blog layout
  674. # [13:58] <paulgendek> maybe for a single page site or basic app
  675. # [13:58] <paulgendek> sure
  676. # [13:58] <jgraham> paulgendek: I don't see how to reach your opinion from the spec or from logic
  677. # [13:58] <paulgendek> but not for magazine/blog layout that can be fairly complex
  678. # [13:58] <annevk42> http://tools.ietf.org/html/bcp19#section-2.4 how can HTML be a character set?
  679. # [13:58] <jgraham> But I have toi go now...
  680. # [13:58] <paulgendek> jgraham: i'll continue to work on it, and we'll see how it goes, thanks
  681. # [14:00] <gsnedders|work> paulgendek: If you absolutely don't want the body's header to be that, which I think is what you do, then don't you want the whole page in that section?
  682. # [14:01] <paulgendek> i see it as the body has a header and a footer, and sections... and all of the structural sections are grouped in a div#container to remain ambiguous... body's header for top most meta-ish content, body footer for debug/version info, javascripts, etc
  683. # [14:02] <paulgendek> the #container can then constrain the width and be centered of all the structural sections of the layout
  684. # [14:02] <gsnedders|work> What is wrong with using header for the header?
  685. # [14:03] <paulgendek> i think there is confusion between <header> as the top part of a section, and #header which is the container for the structural header of a design
  686. # [14:04] <paulgendek> gsnedders|work: because any css done to the body header for a complex design's header section would nest a lot of selectors based off of "header", which would inherit down to all other headers, you would need to use body > header:first-child, which is much more to type, and not really much more semantic, body is more like a canvas for sections imo
  687. # [14:05] <gsnedders|work> paulgendek: Per the spec, body is a section.
  688. # [14:05] <paulgendek> i'm a front-end developer and i bring this up from tons of real-world application in common practice
  689. # [14:05] <gsnedders|work> paulgendek: And yes, you do end up with complex selectors in CSS doing almost anything
  690. # [14:05] * Quits: bzed (n=bzed@2001:6f8:118a:0:0:0:0:100) ("leaving")
  691. # [14:06] <annevk42> hmm, all the charset registry lists are offline?
  692. # [14:06] * Joins: bzed (n=bzed@devel.recluse.de)
  693. # [14:06] <paulgendek> it's much easier for css and javascript to target #header than body > header:first-child
  694. # [14:06] <annevk42> btw, if I'm right and we cannot use the Unicode mapping algorithm for charsets we prolly need to register more aliases
  695. # [14:06] <gsnedders|work> then give the body > header:first-child an id of header
  696. # [14:06] <gsnedders|work> annevk42: http://www.iana.org/assignments/character-sets wfm
  697. # [14:06] <paulgendek> but then you'll have <header id="header"> which is then pointless
  698. # [14:07] <paulgendek> might as well go back to it being a div
  699. # [14:07] <paulgendek> at least it's 3 less chars on open/close
  700. # [14:07] <gsnedders|work> paulgendek: @id has no semantic value anyway, id="foobar" is just as meaningful. It's just a way to select the element.
  701. # [14:07] <annevk42> gsnedders|work, that's not a mailing list
  702. # [14:07] <paulgendek> and the container with #header is a structural section of a design, not necessarily the header of body
  703. # [14:07] <Philip`> "12:52 < jgraham> [...] <body><header><h1>My blog is both unnecessary and wrong" - sounds like an accurate description of many blogs
  704. # [14:07] <gsnedders|work> annevk42: It is a charset registry list :D
  705. # [14:08] <annevk42> sure, but not the one I'm after
  706. # [14:08] * annevk42 wants ietf-charsets@iana.org archives
  707. # [14:08] <gsnedders|work> annevk42: I don't think I ever managed to subscribe to that when I tried
  708. # [14:09] <annevk42> it is supposed to be based here: http://mail.apps.ietf.org/ietf/charsets/threads.html
  709. # [14:09] <gsnedders|work> That's long gone
  710. # [14:09] <annevk42> doh
  711. # [14:09] <annevk42> where's Julian when you need him
  712. # [14:10] <gsnedders|work> Not on IRC? :)
  713. # [14:12] <beowulf> paulgendek: can't you select every header but the body header on the basis that they're all children of another element?
  714. # [14:13] <Lachy_> annevk42, http://lists.w3.org/Archives/Public/ietf-charsets/
  715. # [14:13] <gsnedders|work> Lachy_: That's older and more dead :P
  716. # [14:13] <Lachy_> I noticed taht
  717. # [14:13] <Lachy_> *that
  718. # [14:13] <gsnedders|work> beowulf: Only with :not that really isn't well supported
  719. # [14:14] <annevk42> yeah, that's not the archive I was looking for
  720. # [14:14] <annevk42> I wonder if we should email iana@iana.org
  721. # [14:14] * Quits: Mrmil (n=ut_ollie@host-77-236-204-8.blue4.cz) (Read error: 104 (Connection reset by peer))
  722. # [14:14] <beowulf> header {foo:bar}; body * header {foo:none} # no?
  723. # [14:14] <gsnedders|work> I guess
  724. # [14:14] <gsnedders|work> beowulf: That would work, but you then have to override everything
  725. # [14:15] <beowulf> gsnedders|work: c'est la vie
  726. # [14:15] <gsnedders|work> beowulf: Only CSS 3 Selectors can be relied upon, body > header and *:not(body) > header
  727. # [14:15] <gsnedders|work> *Once
  728. # [14:16] <Philip`> If you want to style a specific element, why would you not simply use id?
  729. # [14:16] * Joins: BlurstOfTimes (n=blurstof@168.203.117.59)
  730. # [14:16] <beowulf> Philip`: iurro
  731. # [14:17] <gsnedders|work> Philip`: Because @id is _so_ yesterday, and XPointer is _so_ the future.
  732. # [14:17] <paulgendek> like i said, maybe in 2015 or whatever, but right now i have to cover all bases, which means older browsers and screen readers, and search crawlers
  733. # [14:17] <beowulf> i don't have bare headers in my documents, so it doesn't apply to me :)
  734. # [14:17] <beowulf> the top header is usually nested in a <div id=banner> or some such
  735. # [14:17] <gsnedders|work> paulgendek: Why doesn't @id work now?
  736. # [14:18] <gsnedders|work> paulgendek: If you want to get one specific element, it seems the most sensible way
  737. # [14:18] <paulgendek> header for body, section, article, aside, nav, sure... but that doesnt mean the same as the structural header of the design
  738. # [14:19] <beowulf> paulgendek: but that has nothing to do with css, surely?
  739. # [14:19] <gsnedders|work> paulgendek: How does that effect selecting elements?
  740. # [14:19] <paulgendek> it affects css, with the > and :first-child selectors not being supported in ie6
  741. # [14:19] <gsnedders|work> paulgendek: Well how would you select a specific p element for example?
  742. # [14:20] <paulgendek> nested selectors
  743. # [14:20] <paulgendek> section#primary article header p
  744. # [14:20] <gsnedders|work> And when you can't do that?
  745. # [14:20] <gsnedders|work> (Because of other siblings, or whatever)
  746. # [14:21] * Joins: Mrmil (n=ut_ollie@host-77-236-204-8.blue4.cz)
  747. # [14:21] <beowulf> paulgendek: doesn't that get all the p's in a header? how do you get just one specific p?
  748. # [14:21] <paulgendek> if there is a reason to target that specific p versus the others, then the article would need an id to specify why it's different
  749. # [14:21] <paulgendek> section#primary article.different-view header p
  750. # [14:21] <gsnedders|work> How does that not apply to the case of getting one specific header?
  751. # [14:21] <gsnedders|work> What is so different between the two cases?
  752. # [14:21] <paulgendek> seems like going backwards though
  753. # [14:21] <beowulf> paulgendek: that would still get all the p's in the header, no?
  754. # [14:21] <paulgendek> <header id="header">
  755. # [14:22] <paulgendek> just looks wrong
  756. # [14:22] <gsnedders|work> Is that more backwards than <p id=p>?
  757. # [14:22] <beowulf> <header id=banner>
  758. # [14:22] <gsnedders|work> <header id=pageheader>?
  759. # [14:22] <beowulf> <header id=typeline>
  760. # [14:22] <beowulf> <header id=hammer>
  761. # [14:22] <paulgendek> beowulf: ok, header#banner, sure, but that still is not the header of a layout where you would place user meta, logo, site name/slogan, primary menu, search, etc
  762. # [14:23] <gsnedders|work> Well what header is it?
  763. # [14:23] <gsnedders|work> I'm sure you can come up with a sensible id for it.,
  764. # [14:23] <paulgendek> the body's header, which i said i'd prefer to reserve for accessibility links, banners, admin bars, etc
  765. # [14:23] <beowulf> paulgendek: when i do html like that i create a div called banner, and place header in it with all that other stuff as siblings
  766. # [14:23] <beowulf> div with id banner
  767. # [14:23] <paulgendek> the "header" that contains a design's header elements are a section, imo
  768. # [14:24] <beowulf> selecting the header is then simply #banner header
  769. # [14:24] <paulgendek> why a div? it's structural
  770. # [14:24] <paulgendek> div/span seems to be block/inline containers for design
  771. # [14:25] <beowulf> is that not what we're talking about?
  772. # [14:26] <beowulf> perhaps i'm being stupid
  773. # [14:27] * gsnedders|work thinks that trying to describe what design you're talking about in words is never going to be as effective as showing us it graphically
  774. # [14:28] <paulgendek> i have to run to work
  775. # [14:28] <paulgendek> but here's the design in question
  776. # [14:28] <paulgendek> http://paulgendek.com/html5
  777. # [14:29] <Philip`> We could avoid a lot of debate if the new elements were named <element0>, <element1>, etc, instead of <section>, <header>, etc, because that would avoid the problem of people having different intepretations of what the names mean
  778. # [14:29] <paulgendek> well i don't agree that <header> is the same a section#header
  779. # [14:29] <paulgendek> but we will continue this some other time ;)
  780. # [14:29] <gsnedders|work> It isn't.
  781. # [14:30] <Philip`> Ooh, there's the "WAHTWG" image again
  782. # [14:30] <Dashiva> Philip`: That would be too easy to confuse. How about naming them after animals instead?
  783. # [14:30] * Philip` wonders where it originally came from
  784. # [14:31] <Philip`> Dashiva: Hmm, that could work
  785. # [14:32] <Philip`> Dashiva: Then we could add easy-to-remember conventions to distinguish different classes of elements, e.g. inline elements can be named after insects while block elements are named after mammals, so you never have to wonder "hmm, is <video> inline or block?" because it'll be obvious from the name
  786. # [14:32] * Quits: paulgendek (n=paulgend@240.182.205.68.cfl.res.rr.com)
  787. # [14:37] <jgraham> hsivonen: Do yo have a bug on file about adding document outline functionality to validator.nu?
  788. # [14:39] <beowulf> paulgendek: http://pastie.org/private/9iv6v5eikq3ahbccblhxig # that's how I'd go about it, though I could be wrong
  789. # [14:39] <hsivonen> jgraham: I think I do, but the bugzilla machine is undergoing a dist upgrade
  790. # [14:41] <jgraham> hsivonen: OK
  791. # [14:41] <hsivonen> hrm. interpid seems to map .ogg to audio/ogg rather than application/ogg
  792. # [14:41] <beowulf> (there is no need for that class on the nav, obv)
  793. # [14:42] <jgraham> beowulf: What's the point of <div class=page>?
  794. # [14:42] <beowulf> jgraham: you need a wrapper for the 'page' in the design
  795. # [14:42] <jgraham> Oh OK
  796. # [14:43] <beowulf> a div of a certain width that sits margin auto left and right in the middle of the page
  797. # [14:43] <jgraham> I assume just styling <body> doesn't work for some reason that isn't clear in your fragment
  798. # [14:43] <beowulf> jgraham: correct
  799. # [14:44] <beowulf> jgraham: i'd have to try hard to remember why though :)
  800. # [14:46] * Joins: pmuellr (n=pmuellr@nat/ibm/x-9a0ab285604aad30)
  801. # [14:48] * Joins: MikeSmith (n=MikeSmit@207.192.197.231)
  802. # [14:50] <jgraham> "OSError: [Errno 26] Text file busy" - WTF?
  803. # [14:50] <jgraham> What was my file doing?
  804. # [14:50] <gsnedders|work> Oh, yeah, sorry, I'll stop looking at that.
  805. # [14:54] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) ("Ex-Chat")
  806. # [14:59] * Joins: ttepasse (n=ttepas--@p5B0133D1.dip.t-dialin.net)
  807. # [15:01] * Parts: StefanSchipor (n=StefanSh@78.96.155.118)
  808. # [15:04] * Joins: ttepass- (n=ttepas--@p5B01391E.dip.t-dialin.net)
  809. # [15:06] * Quits: tantekc (n=tantekc@ool-4570acce.dyn.optonline.net)
  810. # [15:06] * Joins: virtuelv (n=virtuelv@213.236.208.247)
  811. # [15:08] * Quits: tantek (n=tantek@ool-4570acce.dyn.optonline.net)
  812. # [15:12] * Quits: jacobolus (n=jacobolu@adsl-75-36-149-231.dsl.pltn13.sbcglobal.net) (Remote closed the connection)
  813. # [15:13] * Quits: Lachy_ (n=Lachy@pat-tdc.opera.com) (Read error: 104 (Connection reset by peer))
  814. # [15:20] * Quits: abii (n=macbook@cm27.delta30.maxonline.com.sg)
  815. # [15:25] * Joins: abii (n=macbook@cm27.delta30.maxonline.com.sg)
  816. # [15:25] * Joins: jacobolus (n=jacobolu@c-98-248-43-68.hsd1.ca.comcast.net)
  817. # [15:29] * Quits: ttepasse (n=ttepas--@p5B0133D1.dip.t-dialin.net) (Read error: 110 (Connection timed out))
  818. # [15:30] * Joins: ttepasse (n=ttepas--@p5B016789.dip.t-dialin.net)
  819. # [15:33] * Quits: virtuelv (n=virtuelv@213.236.208.247) (Remote closed the connection)
  820. # [15:36] * Joins: aroben (n=aroben@unaffiliated/aroben)
  821. # [15:37] * Quits: ttepass- (n=ttepas--@p5B01391E.dip.t-dialin.net) (Read error: 110 (Connection timed out))
  822. # [15:38] * Parts: annevk42 (n=annevk@ABordeaux-156-1-31-53.w86-213.abo.wanadoo.fr)
  823. # [15:38] * Joins: annevk42 (n=annevk@ABordeaux-156-1-31-53.w86-213.abo.wanadoo.fr)
  824. # [15:38] * Joins: Lachy_ (n=Lachy@pat-tdc.opera.com)
  825. # [15:38] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Read error: 110 (Connection timed out))
  826. # [15:41] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
  827. # [15:41] * Joins: ttepass- (n=ttepas--@p5B016916.dip.t-dialin.net)
  828. # [15:46] * Quits: Super-Dot (n=Super-Do@adsl-75-61-93-143.dsl.pltn13.sbcglobal.net)
  829. # [15:50] * Quits: ttepasse (n=ttepas--@p5B016789.dip.t-dialin.net) (Read error: 60 (Operation timed out))
  830. # [15:50] * Joins: ttepasse (n=ttepas--@p5B01599A.dip.t-dialin.net)
  831. # [16:04] * Joins: archtech (n=sv@83.228.56.37)
  832. # [16:06] * Joins: tantekc (n=tantekc@rrcs-24-103-229-234.nyc.biz.rr.com)
  833. # [16:08] * Joins: tantek (n=tantek@rrcs-24-103-229-234.nyc.biz.rr.com)
  834. # [16:08] * Quits: ttepass- (n=ttepas--@p5B016916.dip.t-dialin.net) (Read error: 110 (Connection timed out))
  835. # [16:09] * Joins: ttepass- (n=ttepas--@p5B014EB4.dip.t-dialin.net)
  836. # [16:10] * Quits: Lachy_ (n=Lachy@pat-tdc.opera.com) ("Leaving")
  837. # [16:17] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  838. # [16:22] * Quits: ttepasse (n=ttepas--@p5B01599A.dip.t-dialin.net) (Read error: 110 (Connection timed out))
  839. # [16:23] * Quits: ttepass- (n=ttepas--@p5B014EB4.dip.t-dialin.net) (Read error: 60 (Operation timed out))
  840. # [16:26] * Joins: paul_irish (n=paul_iri@12.33.239.250)
  841. # [16:33] * Quits: paul_irish (n=paul_iri@12.33.239.250)
  842. # [16:41] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  843. # [16:41] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  844. # [16:54] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) ("Ex-Chat")
  845. # [16:55] * Joins: hobertoAtWork (n=hobertoa@gw1.mcgraw-hill.com)
  846. # [17:02] * Quits: maikmerten (n=merten@ls5dhcp196.cs.uni-dortmund.de) (Remote closed the connection)
  847. # [17:07] * Joins: adactio (n=adactio@rrcs-24-103-229-234.nyc.biz.rr.com)
  848. # [17:08] * Quits: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl) ("Disconnected...")
  849. # [17:11] * Joins: myakura (n=myakura@p1207-ipbf4203marunouchi.tokyo.ocn.ne.jp)
  850. # [17:13] * beowulf starts editing a spec with warnings on the warnings
  851. # [17:13] * Parts: Mrmil (n=ut_ollie@host-77-236-204-8.blue4.cz)
  852. # [17:13] * Quits: nessy (n=nessy@124-171-241-171.dyn.iinet.net.au) ("This computer has gone to sleep")
  853. # [17:14] <Philip`> "Warning: This warning is controversial"?
  854. # [17:14] <Philip`> Add that into each of the warnings, and then everyone should be happy
  855. # [17:15] <Dashiva> Warning: This warning may be self-referential
  856. # [17:15] <beowulf> I just want one that says "Danger Will Robinson!" or something
  857. # [17:21] * Joins: dglazkov (n=dglazkov@nat/google/x-5f2421044a2d3dec)
  858. # [17:22] * Quits: archtech (n=sv@83.228.56.37)
  859. # [17:26] * Joins: ttepasse (n=ttepas--@p5B014C57.dip.t-dialin.net)
  860. # [17:30] * Quits: annevk42 (n=annevk@ABordeaux-156-1-31-53.w86-213.abo.wanadoo.fr) (Read error: 110 (Connection timed out))
  861. # [17:31] * Quits: wakab____ (n=wakaba_@122x221x184x68.ap122.ftth.ucom.ne.jp) ("Leaving...")
  862. # [17:31] * Joins: annevk42 (n=annevk@ABordeaux-156-1-31-53.w86-213.abo.wanadoo.fr)
  863. # [17:34] * Quits: jlebar (n=jlebar@nat/mozilla/x-5aed8dcaafc88338) ("Leaving")
  864. # [17:34] * Joins: jlebar (n=jlebar@nat/mozilla/x-827cd4af2a788ac4)
  865. # [17:42] * Quits: gunderwonder (n=gunderwo@garage.upstruct.com)
  866. # [17:45] * Joins: abii_ (n=macbook@cm27.delta30.maxonline.com.sg)
  867. # [17:52] <Dashiva> I see the poll is open. A comment about vote whipping is trying to find its way here.
  868. # [17:55] * Quits: shepazu (n=schepers@adsl-150-130-169.rmo.bellsouth.net) ("Core Breach")
  869. # [18:02] * Joins: d8uv (i=d84318cd@gateway/web/freenode/x-b99cb87620c8d357)
  870. # [18:04] * Quits: abii (n=macbook@cm27.delta30.maxonline.com.sg) (Read error: 110 (Connection timed out))
  871. # [18:04] * Joins: sbp (i=sbp@59.176.232.72.static.reverse.ltdomains.com)
  872. # [18:05] <d8uv> <article pubdate="2009-08-19">[stuff]</article> is invalid. @pubdate can only work for full time AND date strings. This is stupid as hell.
  873. # [18:11] * Joins: shepazu (n=schepers@adsl-150-130-169.rmo.bellsouth.net)
  874. # [18:12] <Lachy> d8uv, not to worry, the pubdate attribute should be dropped anyway
  875. # [18:12] <sbp> Lachy: should be as in it is your opinion that it ought to be dropped?
  876. # [18:12] <sbp> Lachy: or should be as in it should soon actually be dropped as this is planned?
  877. # [18:13] <d8uv> I kinda like the pubdate attribute, honestly. It'd be better if it were more like atom:updated
  878. # [18:13] <Lachy> should be as soon as Hixie deals with my feedback about it and realises how much of a stupid idea it was to add it
  879. # [18:13] <Lachy> use the <time> element instead
  880. # [18:13] <Lachy> visible metadata is always better
  881. # [18:13] <sbp> so the former... :-)
  882. # [18:13] <d8uv> That's a damn good point
  883. # [18:13] <gsnedders|work> Lachy: The time element still requires datetime, so you don't avoid the issue.
  884. # [18:14] <Lachy> time doesn't require a full date AND time. It allows just dates or just times
  885. # [18:15] <Lachy> "The datetime attribute, if present, must contain a valid date or time string that identifies the date or time being specified."
  886. # [18:15] <sbp> Lachy: where ought the <time> element be used to *explicitly* associate it with the <article>?
  887. # [18:15] <d8uv> Yeah. What I'm working on is HTML5 -> Atom, sans micro*
  888. # [18:15] <sbp> otherwise you might just be mentioning random times in your article content
  889. # [18:16] * Quits: Richardigel (n=igel@247-72.60-188.cust.bluewin.ch)
  890. # [18:16] <Lachy> <article><h1>Heading</h1><p>By Author, <time>2009-08-11</time></p> ...</article>
  891. # [18:16] * Quits: shepazu (n=schepers@adsl-150-130-169.rmo.bellsouth.net) (Client Quit)
  892. # [18:16] <d8uv> And time is too floofy semantically to be of terrible use
  893. # [18:16] <sbp> how does that explicitly associate it?
  894. # [18:16] <Lachy> you may also wish to throw in a <header> element there too
  895. # [18:16] <sbp> that would require natural language parsing
  896. # [18:16] <Lachy> it doesn't
  897. # [18:16] <Lachy> what's your use case for requiring explicit association?
  898. # [18:16] <sbp> so, it's impossible to explicitly associate it?
  899. # [18:17] <sbp> d8uv's HTML5 -> Atom thing
  900. # [18:17] <Lachy> currently, yes, but there were ideas floated yesterday about how to achieve that
  901. # [18:17] * Joins: archtech (n=sv@83.228.56.37)
  902. # [18:17] <sbp> hmm. what kind of options were mooted?
  903. # [18:17] <sbp> got a reference?
  904. # [18:17] <Lachy> does the hAtom microformat solve your use case?
  905. # [18:17] <Lachy> check the IRC logs for yesterday
  906. # [18:18] <d8uv> Use case being how to best semantically do article headers/footers, using explicit data
  907. # [18:18] <d8uv> And yeah, I breathe hAtom, but... with hAtom, it's kind of an all-or-nothing thing
  908. # [18:18] * Joins: Creap (n=Creap@vemod.brg.sgsnet.se)
  909. # [18:18] <Lachy> d8uv, that's not a use case. Why do you need to "semantically do article headers/footers, using explicit data"
  910. # [18:18] * Joins: tantekc_ (n=tantek@rrcs-24-103-229-234.nyc.biz.rr.com)
  911. # [18:19] * Joins: adactio_ (n=adactio@rrcs-24-103-229-234.nyc.biz.rr.com)
  912. # [18:19] * Joins: dave_levin (n=dave_lev@c-98-203-247-78.hsd1.wa.comcast.net)
  913. # [18:19] <sbp> hmm. time/@for=$id and time/@role='pubdate'
  914. # [18:19] * Joins: tantekc__ (n=tantekc@rrcs-24-103-229-234.nyc.biz.rr.com)
  915. # [18:19] <Lachy> sbp, yeah, something like that
  916. # [18:19] <sbp> ref: http://krijnhoetmer.nl/irc-logs/whatwg/20090810#l-326
  917. # [18:19] <d8uv> Pretty much to do hAtom, but natively. The use cases for hAtom are really really strong, and I think too strong to hide in Microformat land
  918. # [18:20] <Lachy> or there's various RDFa/Microdata/Microformts solutions as well
  919. # [18:20] * Joins: Maurice (i=copyman@5ED548D4.cable.ziggo.nl)
  920. # [18:20] <d8uv> Yeah, I'm working on all of the former, honestly
  921. # [18:20] * Joins: dbaron (n=dbaron@nat/mozilla/x-25270c623b127adc)
  922. # [18:21] <d8uv> I just hate overloading @class with stuff that would be better expressed explicitly using native semantics
  923. # [18:21] * Joins: shepazu (n=schepers@adsl-150-130-169.rmo.bellsouth.net)
  924. # [18:21] * jgraham agress that bolt-on sematics are less nice than baked in ones
  925. # [18:22] <tantekc_> d8uv - web designers have been using the class attribute to "subclass" elements for nearly a decade now. so it's a solution that's both works and has been widely adopted in the wild
  926. # [18:22] <tantekc_> hence why microformats took advantage of that existing design pattern
  927. # [18:22] <sbp> Lachy: does this mean you'd like ins/@datetime removed too?
  928. # [18:23] <sbp> (and del/@datetime)
  929. # [18:23] <tantekc_> jgraham - indeed, microformats specifically instructs authors to make use of native language semantics *before* using microformats.
  930. # [18:24] * Quits: pesla (n=retep@procurios.xs4all.nl) ("( www.nnscript.com :: NoNameScript 4.21 :: www.esnation.com )")
  931. # [18:24] <Lachy> sbp, those are questionable. But given their nature, they really can't use visible metadata alternatives. It's more a question of whether or not they're acutally useful in practice
  932. # [18:24] <tantekc_> sbp ins/del with datetime attribute is purely backward compat IMHO. I wouldn't recommend authors actually use those tags since they encourage invisible metadata.
  933. # [18:24] <Lachy> I've never seen an application actually make use of the datetime attribute on ins and del elements
  934. # [18:25] <tantekc_> Lachy - every mediawiki diff page
  935. # [18:25] * jgraham would happily remove <ins> and <del>
  936. # [18:25] <Lachy> tantekc_, oh, I stand corrected
  937. # [18:25] <sbp> well, I was thinking about <ins datetime="..."><article>...</></> for doing what d8uv asks
  938. # [18:25] <tantekc_> with green and red inserted/deleted sections
  939. # [18:25] <tantekc_> and *visible* date time information
  940. # [18:25] <tantekc_> in practice, real world examples of ins and del have visible datetimes or at least titles
  941. # [18:25] <Lachy> I didn't realise they actually used the datetime attributes
  942. # [18:25] <d8uv> Is there any block-level equivalent to @datetime?
  943. # [18:26] <Lachy> d8uv, I don't understand the question
  944. # [18:26] <sbp> shame that certain attributes can't be agglomerated together on mouseover. so for example, if you had <article title="ABC" pubdate="2008"> a mouseover on that could display "ABC / Published: 2008" or something
  945. # [18:27] <sbp> that would solve the visible metadata problem. it'd be visible!
  946. # [18:27] <Lachy> tantekc_, are there any client side applications that make use of the datetime attributes on ins and del elements though?
  947. # [18:27] <d8uv> @datetime is used on time, ins, and del. To say that X happened on D date. I'd love to see something like that, but for section content
  948. # [18:27] <tantekc_> Lachy - not that I know of, but I haven't particularly searched, so I wouldn't claim that there aren't any.
  949. # [18:27] <Lachy> sbp, it'd also be incredibly annoying
  950. # [18:28] <sbp> well, that's a subjective opinion
  951. # [18:28] <sbp> I'm not sure how to find out whether it really would be
  952. # [18:28] <tantekc_> sbp - indeed, even partial visibility (e.g. via title attribute) is better than invisibility.
  953. # [18:28] <sbp> apart from doing a wide poll
  954. # [18:28] <Lachy> sbp, just imagine hoving your mouse anywhere over an article and having a tooltip displayed constantly?
  955. # [18:28] * Quits: tantek (n=tantek@rrcs-24-103-229-234.nyc.biz.rr.com) (Read error: 110 (Connection timed out))
  956. # [18:29] <sbp> no, I mean only for certain attributes
  957. # [18:29] <sbp> so basically certain attributes could be treated as @title adjuncts
  958. # [18:29] <d8uv> That's what sbp does on his blog, actually
  959. # [18:29] <Lachy> sure, I get what you mean. I just don't think it's usually a good idea to give a tooltip to an entire article
  960. # [18:29] <Lachy> where is sbp's blog?
  961. # [18:30] <sbp> so article/@title is a bad idea too?
  962. # [18:30] <sbp> my blog is a bunch of cheats, I wouldn't take it seriously
  963. # [18:30] * Quits: tantekc (n=tantekc@rrcs-24-103-229-234.nyc.biz.rr.com) (Read error: 110 (Connection timed out))
  964. # [18:30] <Lachy> I generally wouldn't use it
  965. # [18:30] <Lachy> but there may be a few cases that it might be acceptble
  966. # [18:30] * Joins: bgalbraith (n=bgalbrai@nat/mozilla/x-4462a468e6aef8fd)
  967. # [18:31] * Quits: adactio (n=adactio@rrcs-24-103-229-234.nyc.biz.rr.com) (Read error: 110 (Connection timed out))
  968. # [18:35] <sbp> thinking about it, the date information is only required in Atom
  969. # [18:35] <sbp> there is a motivation for it being secret. I might not want to display it
  970. # [18:35] <sbp> as a matter of fact, I don't like displaying dates in my articles
  971. # [18:35] <sbp> I don't find them important on a trashy weblog
  972. # [18:36] <sbp> but they are required by Atom
  973. # [18:36] <annevk42> display:none?
  974. # [18:36] <d8uv> BTW, Lachy? You rule. And have convinced me to drop article@pubdate, for the verdant fields of footer/time@datetime. If I want to make it more explicit, I'll use Microdata, possibly RDFa or microformats
  975. # [18:36] <sbp> so I wonder about @data-date
  976. # [18:36] <sbp> annevk42: sure, or that. but @data-* require no styling at least :-)
  977. # [18:36] <tantekc_> d8uv - feel free to hang out in #microformats and ask any questions about hAtom
  978. # [18:36] <annevk42> or pubdata then :)
  979. # [18:37] * tantekc_ is now known as tantek
  980. # [18:37] * Joins: ap (n=ap@nat/apple/x-43cebf1a19e54647)
  981. # [18:37] <sbp> annevk42: well, in the context of Lachy wanting @pubdate removed...
  982. # [18:37] <sbp> sure, if @pubdate stays then obviously that'd be the thing to use...
  983. # [18:37] <Lachy> sbp, dates are very useful for readers, as it gives some temporal context to an article.
  984. # [18:38] <d8uv> I love microformats, and hAtom has saved me thousands of hours of work, due to my unconventional workflow
  985. # [18:38] <sbp> Lachy: temporal context is not important for my articles
  986. # [18:38] <Lachy> sbp, it takes talent to be able to write articles of a timeless nature
  987. # [18:38] <sbp> no, the opposite
  988. # [18:38] * Joins: olliej (n=oliver@76.14.73.3)
  989. # [18:38] <Lachy> I guess it depends what you write about
  990. # [18:38] <sbp> I mean I do not expect them even worth reading now
  991. # [18:38] <Lachy> LOL
  992. # [18:39] <sbp> so why date them? :-)
  993. # [18:39] <d8uv> sbp writes mainly about 80s hairstyles, so... you know. Dates aren't important, really
  994. # [18:39] <Lachy> sbp, can you give a link to your blog?
  995. # [18:39] <sbp> yeah. you're just going there for folicular action really
  996. # [18:39] <sbp> http://inamidst.com/whits/
  997. # [18:39] <gsnedders|work> Well, personally, I just mindlessly vandalize my own blog, if you believe jgraham, at least.
  998. # [18:40] <sbp> note that I'm using HTML5, but only those elements and attributes which were already available in HTML 4.01. the source is just a few lines of python2, http://inamidst.com/whits/code/iris/feed.py
  999. # [18:41] * Joins: sbublava (n=stephan@77.117.71.37.wireless.dyn.drei.com)
  1000. # [18:42] <Lachy> gsnedders|work, that's true. you're site is unique case in which it's administrator is also considered an out of control vandal
  1001. # [18:42] <d8uv> gsnedders works with Hixie?
  1002. # [18:43] <Lachy> d8uv, on HTML5, yes, like the rest of us. But otherwise no
  1003. # [18:43] <gsnedders|work> I mean, it's hardly as if I stabbed him earlier.
  1004. # [18:43] <gsnedders|work> With one of those toy plastic knives, though, so no harm done.
  1005. # [18:43] <Lachy> LOL
  1006. # [18:43] * Joins: sebmarkbage (n=miranda@h-6-72.A146.priv.bahnhof.se)
  1007. # [18:44] <jgraham> So, do I point out that removing @summary never put us in conflict with another spec or not?
  1008. # [18:44] <jgraham> I have written the email but I am scared of a new thread being generated
  1009. # [18:45] <sbp> point out to whom?
  1010. # [18:45] <sbp> have WAI PF said much more about this issue?
  1011. # [18:45] <annevk42> jgraham, no
  1012. # [18:45] <sbp> last time I went looking, just a few days ago, it seemed they were very quiet
  1013. # [18:46] <annevk42> jgraham, there's no real benefit to saying "you were wrong" imo
  1014. # [18:46] * Quits: dave_levin (n=dave_lev@c-98-203-247-78.hsd1.wa.comcast.net)
  1015. # [18:47] <jgraham> annevk42: You might be right. But the point is really that where HTML 5 is actually in conflict with other specs it is generally because of irreconcilable technical differences between those specs and required browser behaviour
  1016. # [18:48] <jgraham> Manu seems to want to paint it as "WHATWG are selfish and don't care about anyone else's ideas"
  1017. # [18:48] <Lachy> jgraham, that's been pointed out before
  1018. # [18:48] <jgraham> Lachy: Which part?
  1019. # [18:49] <Lachy> the part about removing @summary not actually conflicting with another spec
  1020. # [18:49] <Lachy> in that it only contradicts a non-normative guidline in a NOTE
  1021. # [18:49] <jgraham> Lachy: Indeed. But it is still being presented as if it were an actual spec conflict
  1022. # [18:49] * Quits: adactio_ (n=adactio@rrcs-24-103-229-234.nyc.biz.rr.com)
  1023. # [18:50] <Lachy> I know. But there doesn't appear to be much that can be done to make them acknowledge that fact
  1024. # [18:50] <annevk42> jgraham, we've not always approached every group when there was a problem
  1025. # [18:50] <annevk42> jgraham, e.g. CharMod was after the fact, I think
  1026. # [18:50] * Joins: maikmerten (n=maikmert@U2b44.u.pppool.de)
  1027. # [18:50] <annevk42> jgraham, for URLs we did try, but were initially rejected
  1028. # [18:51] <jgraham> annevk42: Yeah, but we had a meeting with the i18n people and explained the requirements and everything was more or less OK
  1029. # [18:51] <sbp> funny thing is that WAI PF aren't even chartered
  1030. # [18:51] <Lachy> what?
  1031. # [18:51] <sbp> their charter expired in 30th June 2009
  1032. # [18:51] <sbp> *on
  1033. # [18:51] <jgraham> So it wasn't like we were unwilling to work with others
  1034. # [18:51] <Lachy> didn't it get renewed?
  1035. # [18:51] <sbp> not according to the charter, nope
  1036. # [18:52] <gsnedders|work> I guess it's in the process of being renewed.
  1037. # [18:52] <sbp> if it did, the charter hasn't been updated to reflect that
  1038. # [18:52] <gsnedders|work> CSS WG was unchartered for a time
  1039. # [18:52] <sbp> probably. they keep giving it little extensions, which is weird
  1040. # [18:52] <sbp> I don't know why they don't just heap another couple of years on it
  1041. # [18:52] <sbp> probably internal stuff going on
  1042. # [18:52] <Lachy> It would make much more sense if they were just given a perpetual charter with the ability to revise it when needed
  1043. # [18:52] <annevk42> jgraham, maybe you should ask Manu first for a list of where he fails we have not taken our input to other groups
  1044. # [18:53] <sbp> yeah, that'd be fine
  1045. # [18:53] <annevk42> jgraham, maybe his concern is that we put anything in the draft at all without first solving the issue
  1046. # [18:54] * Quits: olliej (n=oliver@76.14.73.3)
  1047. # [18:54] <jgraham> annevk42: Maybe. Which might be a reasonable position (dunno how it would work in practice) but it's not really what he said
  1048. # [18:54] <sbp> also I notice Janina Sajka signs herself PFWG chair
  1049. # [18:54] <sbp> whereas the charter says Al Gilman is still chair
  1050. # [18:54] <gsnedders|work> Charters often aren't updated for chair changes, FWIW
  1051. # [18:54] <sbp> ah
  1052. # [18:55] <sbp> ah yes, the homepage is accurate
  1053. # [18:55] <annevk42> jgraham, since this borders on having a process discussion better safe than sorry applies :)
  1054. # [18:56] <annevk42> well, maybe not, but this discussion has been going back and forth a long time already, so figuring out what everyone wants first seems better
  1055. # [18:57] <sbp> better Spiderman than sorry...
  1056. # [18:57] * Joins: mlpug (n=mlpug@a91-156-62-135.elisa-laajakaista.fi)
  1057. # [18:58] * jgraham also notes that if the intent of the warnings draft is to make the draft indicate the stability of various sections of HTML5 then it is woefully inadequate and the process that people have been talking about using to get issues is not going to help
  1058. # [18:58] <jgraham> hsivonen's suggestion of porting the WHATWG annotaions would work better
  1059. # [18:59] * Joins: Richardigel (n=igel@247-72.60-188.cust.bluewin.ch)
  1060. # [19:00] <sbp> I'm off. thanks for your help, Lachy et al.
  1061. # [19:00] * Parts: sbp (i=sbp@59.176.232.72.static.reverse.ltdomains.com) ("Leaving")
  1062. # [19:00] <Philip`> Is anyone intending/planning to actually port the annotations?
  1063. # [19:03] <jgraham> Philip`: I have too many other things to do to add more things to the pile at the moment
  1064. # [19:05] * Joins: jorlow (n=jorlow@67.218.110.220)
  1065. # [19:08] <Lachy> Philip`, port them to where?
  1066. # [19:08] <Philip`> Lachy: To the W3C version
  1067. # [19:08] <Philip`> (without scripting)
  1068. # [19:18] * Joins: dave_levin (n=dave_lev@72.14.227.1)
  1069. # [19:18] * Quits: dave_levin (n=dave_lev@72.14.227.1) (Remote closed the connection)
  1070. # [19:18] * Joins: dave_levin (n=dave_lev@72.14.227.1)
  1071. # [19:19] * Quits: d8uv (i=d84318cd@gateway/web/freenode/x-b99cb87620c8d357) (Ping timeout: 180 seconds)
  1072. # [19:19] * Joins: gsnedders (n=gsnedder@c83-252-194-253.bredband.comhem.se)
  1073. # [19:21] * Quits: tantek (n=tantek@rrcs-24-103-229-234.nyc.biz.rr.com)
  1074. # [19:22] * Quits: annevk42 (n=annevk@ABordeaux-156-1-31-53.w86-213.abo.wanadoo.fr) (Read error: 110 (Connection timed out))
  1075. # [19:27] * Quits: abii_ (n=macbook@cm27.delta30.maxonline.com.sg)
  1076. # [19:29] * Joins: cying (n=cying@70.90.171.153)
  1077. # [19:34] * Quits: archtech (n=sv@83.228.56.37) (No route to host)
  1078. # [19:37] * Joins: maikmerten_ (n=maikmert@U023e.u.pppool.de)
  1079. # [19:38] * Quits: jorlow (n=jorlow@67.218.110.220)
  1080. # [19:40] * Joins: slightlyoff (n=slightly@nat/google/x-c3b834f2e1e45c21)
  1081. # [19:42] * Joins: jorlow (n=jorlow@nat/google/x-7cc45a4ae85c87db)
  1082. # [19:47] * Parts: Richardigel (n=igel@247-72.60-188.cust.bluewin.ch)
  1083. # [19:52] * Quits: maikmerten (n=maikmert@U2b44.u.pppool.de) (Read error: 110 (Connection timed out))
  1084. # [19:52] * Quits: mat_t (n=mattomas@nat/canonical/x-a792fe205bef80c3) ("This computer has gone to sleep")
  1085. # [19:53] * Quits: cying (n=cying@70.90.171.153) (Remote closed the connection)
  1086. # [19:53] * Joins: cying (n=cying@70.90.171.153)
  1087. # [19:57] * Joins: annevk42 (n=annevk@ABordeaux-156-1-136-243.w90-5.abo.wanadoo.fr)
  1088. # [19:59] * Joins: pmuellr_ (n=pmuellr@nat/ibm/x-0515176b915d34b2)
  1089. # [20:03] * Quits: maikmerten_ (n=maikmert@U023e.u.pppool.de) (Remote closed the connection)
  1090. # [20:05] * Joins: jlebar_ (n=jlebar@nat/mozilla/x-31bff6bde2e18dce)
  1091. # [20:06] * Joins: maikmerten (n=maikmert@U023e.u.pppool.de)
  1092. # [20:08] <Philip`> http://www.w3.org/mid/PM-GA.20090811195755.954F1.1.1D@semsol.com
  1093. # [20:09] <annevk42> jgraham, maybe you should call it out
  1094. # [20:09] <annevk42> jgraham, Manu is not really representing things factual
  1095. # [20:10] * Joins: jwalden (n=waldo@c-98-248-40-206.hsd1.ca.comcast.net)
  1096. # [20:10] * Joins: dbaron_ (n=dbaron@nat/mozilla/x-c42f3fc5fc06d9be)
  1097. # [20:10] <annevk42> also, if it's just about other specifications, why does microdata need to be called out?
  1098. # [20:11] * Quits: pmuellr (n=pmuellr@nat/ibm/x-9a0ab285604aad30) (Read error: 110 (Connection timed out))
  1099. # [20:13] <Dashiva> Philip`: Now watch that email get buried
  1100. # [20:13] * Joins: olliej (n=oliver@17.246.17.250)
  1101. # [20:15] * aroben is now known as aroben|lunch
  1102. # [20:16] * Quits: foolip (n=philip@pat.se.opera.com) (Read error: 110 (Connection timed out))
  1103. # [20:18] * Quits: jlebar (n=jlebar@nat/mozilla/x-827cd4af2a788ac4) (Read error: 110 (Connection timed out))
  1104. # [20:21] * Quits: dbaron (n=dbaron@nat/mozilla/x-25270c623b127adc) (Read error: 110 (Connection timed out))
  1105. # [20:27] * Quits: gsnedders (n=gsnedder@c83-252-194-253.bredband.comhem.se) (Remote closed the connection)
  1106. # [20:34] * Joins: michaeln (n=michaeln@nat/google/x-48c56986c524759a)
  1107. # Aug 11 20:08:48 <Dashiva> Philip`: Now watch that email get buried
  1108. # Aug 11 20:09:02 * olliej (n=oliver@17.246.17.250) has joined #whatwg
  1109. # Aug 11 20:10:42 * aroben is now known as aroben|lunch
  1110. # Aug 11 20:11:47 * foolip has quit (Read error: 110 (Connection timed out))
  1111. # Aug 11 20:14:17 * jlebar has quit (Read error: 110 (Connection timed out))
  1112. # Aug 11 20:17:11 * dbaron has quit (Read error: 110 (Connection timed out))
  1113. # Aug 11 20:22:32 * gsnedders has quit (Remote closed the connection)
  1114. # Aug 11 20:29:21 * michaeln (n=michaeln@nat/google/x-48c56986c524759a) has joined #whatwg
  1115. # Aug 11 20:30:26 * webben has quit (Read error: 110 (Connection timed out))
  1116. # Aug 11 20:31:31 <Philip`> "... the idea that it is not dangerous to read any part of the standard" - hmm, it can often be dangerous to one's composure and/or sanity
  1117. # Aug 11 20:32:38 * gsnedders (n=gsnedder@c83-252-194-253.bredband.comhem.se) has joined #whatwg
  1118. # Aug 11 20:34:03 <Dashiva> So any section without a warning is set in stone?
  1119. # Aug 11 20:35:36 <Philip`> I think we should carve the HTML5 spec into a mountain, so that it won't be lost to future archeologists
  1120. # Aug 11 20:45:24 * tantek (n=tantek@rrcs-24-103-229-234.nyc.biz.rr.com) has joined #whatwg
  1121. # Aug 11 20:47:59 * krijnh has quit (Read error: 110 (Connection timed out))
  1122. # Aug 11 20:48:48 * othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net) has joined #whatwg
  1123. # Aug 11 20:50:46 * pmuellr_ has quit ()
  1124. # Aug 11 20:57:57 * pmuellr (n=pmuellr@nat/ibm/x-3a363835a3bdacbf) has joined #whatwg
  1125. # Aug 11 20:59:08 * weinig (n=weinig@nat/apple/x-868972eccef9f0f2) has joined #whatwg
  1126. # Aug 11 21:08:35 * adactio (n=adactio@rrcs-24-103-229-234.nyc.biz.rr.com) has joined #whatwg
  1127. # Aug 11 21:09:00 * aroben|lunch is now known as aroben|away
  1128. # Aug 11 21:14:10 * jwalden has quit ("inbound")
  1129. # Aug 11 21:22:45 * MikeSmith has quit ("Tomorrow to fresh woods, and pastures new.")
  1130. # Aug 11 21:24:38 <Lachy> oh no, Manu's draft has pulled ahead in the polls :-(
  1131. # Aug 11 21:25:33 <Lachy> oh well, I suppose, even if it is published, at least it will become irrelevant as soon as its published
  1132. # Aug 11 21:25:36 * jlebar_ has quit (Read error: 110 (Connection timed out))
  1133. # Aug 11 21:27:44 <Hixie> hsivonen: there's already a version of the contents list that has static issue markers, iirc
  1134. # Aug 11 21:27:48 <Hixie> hsivonen: ask mikesmith
  1135. # Aug 11 21:30:05 * jwalden (n=waldo@nat/mozilla/x-1d1a3ed668c38576) has joined #whatwg
  1136. # Aug 11 21:32:00 * dbaron_ has quit (Read error: 110 (Connection timed out))
  1137. # Aug 11 21:32:30 * dbaron_ (n=dbaron@nat/mozilla/x-e8bd6a5e09ea0ed2) has joined #whatwg
  1138. # Aug 11 21:32:55 <tantekc__> Lachy - it appears that the form presents the *option* to cc answers to public-html, but by default no-one is cc'd.
  1139. # Aug 11 21:33:00 * tantekc__ is now known as tantekc
  1140. # Aug 11 21:33:18 * othermaciej has quit ()
  1141. # Aug 11 21:34:37 <tantekc> tabulated results: http://www.w3.org/2002/09/wbs/40318/wd08/results
  1142. # Aug 11 21:34:58 <Lachy> tantekc, I know. That's what I've been looking at
  1143. # Aug 11 21:35:21 * [tantekc] (n=tantekc@rrcs-24-103-229-234.nyc.biz.rr.com): Tantek Çelik
  1144. # Aug 11 21:35:21 * [tantekc] #whatwg #microformats
  1145. # Aug 11 21:35:21 * [tantekc] irc.freenode.net :http://freenode.net/
  1146. # Aug 11 21:35:21 * [tantekc] End of WHOIS list.
  1147. # Aug 11 21:40:27 * pmuellr has quit (Read error: 110 (Connection timed out))
  1148. # Aug 11 21:42:06 * jlebar_ (n=jlebar@nat/mozilla/x-d57f23cd2120578a) has joined #whatwg
  1149. # Aug 11 21:45:46 * heycam` (n=cam@203-217-91-14.dyn.iinet.net.au) has joined #whatwg
  1150. # Aug 11 21:46:52 * Super-Dot (n=Super-Do@adsl-75-61-93-143.dsl.pltn13.sbcglobal.net) has joined #whatwg
  1151. # Aug 11 21:49:45 * taf2 (n=taf2@38.99.201.242) has joined #whatwg
  1152. # Aug 11 21:52:25 * ChrisWilson (n=cwilso@nat/microsoft/x-23f69c67fedb8c14) has joined #whatwg
  1153. # Aug 11 21:52:43 * archtech (n=sv@83.228.56.37) has joined #whatwg
  1154. # Aug 11 21:54:33 * heycam has quit (Read error: 101 (Network is unreachable))
  1155. # Aug 11 21:59:50 * taf2 has quit ()
  1156. # Aug 11 22:00:12 * Chris_Wilson has quit (Read error: 110 (Connection timed out))
  1157. # Aug 11 22:02:38 * virtuelv (n=virtuelv@201.169.34.95.customer.cdi.no) has joined #whatwg
  1158. # Aug 11 22:07:43 * maikmerten has quit (Remote closed the connection)
  1159. # Aug 11 22:24:57 * roc has quit ()
  1160. # Aug 11 22:27:20 * mlpug has quit (Remote closed the connection)
  1161. # Aug 11 22:28:02 * alina (n=chatzill@122.173.57.97) has joined #whatwg
  1162. # Aug 11 22:28:05 * othermaciej (n=mjs@17.246.19.10) has joined #whatwg
  1163. # Aug 11 22:29:16 <othermaciej> Lachy: I see more "yes" votes for the vanilla draft so far
  1164. # Aug 11 22:31:42 <Dashiva> This doesn't actually specifiy votes for or against :) "I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft."
  1165. # Aug 11 22:32:52 * anne-w (i=5a05cff3@gateway/web/freenode/x-4402acd2a9f8880f) has joined #whatwg
  1166. # Aug 11 22:34:05 <anne-w> test
  1167. # Aug 11 22:34:14 <othermaciej> lol
  1168. # Aug 11 22:35:03 <anne-w> guess it works... what happened to the logs?
  1169. # Aug 11 22:35:05 <gsnedders> anne-w: fail
  1170. # Aug 11 22:35:32 <Dashiva> Too bad Ericsson isn't sending in 39 people to vote here
  1171. # Aug 11 22:35:52 <Lachy> othermaciej, it changed in the short time since I said Manu's was in the lead
  1172. # Aug 11 22:40:25 * ROBOd has quit ("http://www.robodesign.ro")
  1173. # Aug 11 22:41:06 * anne-w has quit (Ping timeout: 180 seconds)
  1174. # Aug 11 22:42:59 * SamerZ (n=SamerZ@CPE002129bd5f2a-CM0014e8b57926.cpe.net.cable.rogers.com) has joined #whatwg
  1175. # Aug 11 22:45:22 * SamerZ has quit (Client Quit)
  1176. # Aug 11 22:48:55 * sbublava has quit ()
  1177. # Aug 11 22:50:35 <othermaciej> Lachy: seems like it will be close, either way
  1178. # Aug 11 22:51:43 * erikvold (n=erikvvol@96.49.192.204) has joined #whatwg
  1179. # Aug 11 22:55:13 * alina has quit ("ChatZilla 0.9.85 [Firefox 3.0.13/2009080315]")
  1180. # Aug 11 22:55:49 <Lachy> I updated my response to the poll linking to jgraham's comments http://lists.w3.org/Archives/Public/public-html/2009Aug/0447.html
  1181. # Aug 11 22:56:02 <Lachy> oops, wrong link
  1182. # Aug 11 22:56:17 <Lachy> http://lists.w3.org/Archives/Public/public-html/2009Aug/0563.html
  1183. # Aug 11 23:02:37 * erikvvold has quit (Read error: 110 (Connection timed out))
  1184. # Aug 11 23:20:02 <othermaciej> how long is the poll going to be open?
  1185. # Aug 11 23:20:50 <Lachy_> "This questionnaire is open from 2009-08-10 to 2009-08-17."
  1186. # Aug 11 23:21:18 <othermaciej> fun, fun
  1187. # Aug 11 23:22:37 * gsnedders has quit ()
  1188. # Aug 11 23:22:59 <Dashiva> I don't get this comment: "I just dislike having content inside attributes in general..."
  1189. # Aug 11 23:23:15 * zdobersek1 (n=zan@cpe-92-37-66-43.dynamic.amis.net) has joined #whatwg
  1190. # Aug 11 23:23:32 <Dashiva> It's for a 'yes' vote to Hixie's draft
  1191. # Aug 11 23:24:02 <othermaciej> maybe an elliptical comment about summary?
  1192. # Aug 11 23:24:35 * zdobersek1 has quit (Client Quit)
  1193. # Aug 11 23:25:02 * Lachy has quit (Read error: 110 (Connection timed out))
  1194. # Aug 11 23:25:41 * othermaciej has quit (Remote closed the connection)
  1195. # Aug 11 23:25:55 * othermaciej (n=mjs@nat/apple/x-b3c85c40daf6dcf7) has joined #whatwg
  1196. # Aug 11 23:25:57 * Maurice has quit ("Disconnected...")
  1197. # Aug 11 23:45:20 <othermaciej> it looks like there are only 2 people who voted yes on both documents
  1198. # Aug 11 23:45:26 <othermaciej> if I am doing my math right
  1199. # Aug 11 23:45:50 <Dashiva> I wonder if they know about the poll flaw
  1200. # Aug 11 23:45:51 * nessy (n=nessy@124-171-241-171.dyn.iinet.net.au) has joined #whatwg
  1201. # Aug 11 23:48:26 <Hixie> http://www.w3.org/2002/09/wbs/40318/wd08/results?view=compact is a more useful view, i think
  1202. # Aug 11 23:49:07 * Dashiva shakes fist at Member-only
  1203. # Aug 11 23:49:41 <othermaciej> it looks like the WG really doesn't want to publish two competing documents
  1204. # Aug 11 23:49:48 <Lachy_> oh, much better
  1205. # Aug 11 23:50:36 <othermaciej> I'm not clear on how voting yes on both amounts to an abstain - is it just because it fails to express a preference, where voters may have a preference in the case we publish only one?
  1206. # Aug 11 23:52:13 <Dashiva> othermaciej: Yes
  1207. # Aug 11 23:52:40 <Dashiva> If you had voted for only one, the 'do both' would still have failed, but your preference would be better placed to be the one
  1208. # Aug 11 23:52:41 <othermaciej> I guess preferred / acceptable / unacceptable would have been better than yes / no voting
  1209. # Aug 11 23:52:42 * tantekc has quit ()
  1210. # Aug 11 23:53:33 * tantekc (n=tantekc@rrcs-24-103-229-234.nyc.biz.rr.com) has joined #whatwg
  1211. # Aug 11 23:58:29 * weinig_ (n=weinig@17.246.18.83) has joined #whatwg

The end :)