/irc-logs / freenode / #whatwg / 2008-04-22 / end

Options:

  1. # Session Start: Tue Apr 22 00:00:00 2008
  2. # Session Ident: #whatwg
  3. # [00:02] <Molly_> I'm going to work on some text about the event
  4. # [00:04] <Lachy> what's the new domain name?
  5. # [00:04] <hsivonen> Molly_, annevk: 10 points: http://pastebin.ca/992541
  6. # [00:04] <Molly_> Lachy: Hey Lachlan!
  7. # [00:05] * Joins: jruderman_ (n=jruderma@guest-226.mountainview.mozilla.com)
  8. # [00:05] <Molly_> the new domain names are futurewebevent.com and futurewebevent.org
  9. # [00:05] <Molly_> I like the singularity of the name :D
  10. # [00:05] * Quits: jruderman (n=jruderma@guest-226.mountainview.mozilla.com) (Read error: 104 (Connection reset by peer))
  11. # [00:05] <Molly_> we can have one event, or many
  12. # [00:06] <Molly_> and of course, it could happen at /any/ time
  13. # [00:06] <Molly_> it's totally asynchronous
  14. # [00:08] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  15. # [00:09] <Lachy> hi Molly!
  16. # [00:13] <Molly_> Lachy: Nice to "see" you :D
  17. # [00:16] * Quits: qwert666_ (n=qwert666@acbd33.neoplus.adsl.tpnet.pl) ("Leaving")
  18. # [00:23] * Quits: virtuelv (n=virtuelv@225.80-203-100.nextgentel.com) ("Ex-Chat")
  19. # [00:48] * Quits: weinig (n=weinig@17.203.15.172)
  20. # [00:49] * Joins: weinig (n=weinig@nat/apple/x-7d0e13c07501d1d1)
  21. # [00:50] * Quits: weinig (n=weinig@nat/apple/x-7d0e13c07501d1d1) (Client Quit)
  22. # [01:12] * Quits: eseidel (n=eseidel@nat/google/x-9038ea68c8faec60)
  23. # [01:15] * Quits: Lachy (n=Lachlan@ti200710a340-2662.bb.online.no) ("Leaving")
  24. # [01:18] * Joins: othermaciej_ (n=mjs@17.203.15.181)
  25. # [01:19] * Quits: KevinMarks (n=KevinMar@nat/google/x-96658129b74f1b1f) ("The computer fell asleep")
  26. # [01:20] * Joins: KevinMarks (n=KevinMar@nat/google/x-4d3fdf91a32420d8)
  27. # [01:20] * Joins: Lachy (n=Lachlan@ti200710a340-2662.bb.online.no)
  28. # [01:26] * Quits: KevinMarks (n=KevinMar@nat/google/x-4d3fdf91a32420d8) (Remote closed the connection)
  29. # [01:42] * Joins: eseidel (n=eseidel@70-3-27-13.area5.spcsdns.net)
  30. # [01:43] * Joins: webben (n=benh@91.84.239.85)
  31. # [01:47] * Joins: kingryan (n=ryan@c-24-5-77-167.hsd1.ca.comcast.net)
  32. # [01:49] * Quits: eseidel (n=eseidel@70-3-27-13.area5.spcsdns.net) (Read error: 104 (Connection reset by peer))
  33. # [01:52] * Parts: hasather_ (n=hasather@90-231-107-133-no62.tbcn.telia.com)
  34. # [01:52] * Dashiva chuckles at 1472
  35. # [01:53] * othermaciej_ is now known as othermaciej
  36. # [01:55] * Quits: Lachy (n=Lachlan@ti200710a340-2662.bb.online.no) ("This computer has gone to sleep")
  37. # [01:58] * Parts: Molly_ (i=user@ip70-171-193-169.tc.ph.cox.net)
  38. # [01:58] <webben> Philip`: Have you done a survey of @abbr ?
  39. # [01:59] * Joins: eseidel (n=eseidel@72-57-227-255.area5.spcsdns.net)
  40. # [02:04] * Quits: andersca (n=andersca@nat/apple/x-5cbcdafbc6f6af6a) (Read error: 104 (Connection reset by peer))
  41. # [02:05] <takkaria> The Endgame
  42. # [02:05] <takkaria> mispaste there
  43. # [02:08] <Philip`> webben: What kind of survey?
  44. # [02:09] * Quits: shepazu (n=schepers@218.246.74.90)
  45. # [02:09] * Joins: andersca (n=andersca@nat/apple/x-acb3a5bd9ea8d9ca)
  46. # [02:09] * Joins: webben_ (n=benh@dip5-fw.corp.ukl.yahoo.com)
  47. # [02:11] <Philip`> webben_: http://krijnhoetmer.nl/irc-logs/whatwg/20080422#l-43
  48. # [02:11] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  49. # [02:12] * Joins: csarven (n=csarven@modemcable130.251-202-24.mc.videotron.ca)
  50. # [02:12] <Philip`> From looking at a few cases of @abbr, it's used almost entirely for day names in calendars, and I think that's all from Wordpress
  51. # [02:12] <webben_> any sort of survey
  52. # [02:13] <Philip`> except for some who get the full/abbreviated forms the wrong way round
  53. # [02:14] <Philip`> and some who have abbr="abbrText" and abbr="%A"
  54. # [02:14] <webben_> Philip`: Do you have a link to that survey?
  55. # [02:14] <Philip`> webben_: No, since I only just started my thing looking for @abbr uses - it'll probably take ten minutes or so
  56. # [02:14] <webben_> oh right, that was quick
  57. # [02:15] <Philip`> Actually, it'd be more useful if I got the full cell text as well as the @abbr value
  58. # [02:15] <webben_> Yep.
  59. # [02:18] * Philip` wonders what happens if he runs the surveyer process twice
  60. # [02:18] <Philip`> (*twice simultaneously)
  61. # [02:18] * Quits: eseidel (n=eseidel@72-57-227-255.area5.spcsdns.net)
  62. # [02:19] <Philip`> Oh, the second one goes fast since all the HTML data is cached
  63. # [02:20] <Philip`> webben_: Do you have any ideas of a useful way to present the data?
  64. # [02:21] <webben_> um ... cell innerHTML, abbreviation, URL to page/ideally page fragment
  65. # [02:22] <webben_> Philip`: conceivably one might want to include some other markers of sanity
  66. # [02:22] <webben_> e.g. abbr doesn't make much sense for a layout table: is this table using th/caption/summary/headers/scope
  67. # [02:22] <webben_> dunno how hard that would be to build into your tests though
  68. # [02:23] <Philip`> webben_: Hmm, there seems to be few enough non-calendar @abbr examples that it'd probably be better just to check those cases manually
  69. # [02:24] <webben_> maybe it's worth gathering non-calendar examples
  70. # [02:24] <webben_> specifically
  71. # [02:24] <Philip`> It'd be nice if I could automatically detect all the calendars
  72. # [02:24] * Quits: webben (n=benh@91.84.239.85) (Read error: 110 (Connection timed out))
  73. # [02:24] <Philip`> but they're in lots of languages
  74. # [02:24] <webben_> if the calendar examples are just some devs following the same markup pattern, they won't tell us much
  75. # [02:24] <webben_> but they all have months and stuff?
  76. # [02:25] <webben_> I mean, it's not like the localizations are that complex
  77. # [02:25] <Philip`> (土曜日, woensdag, Martedì, domingo, ...)
  78. # [02:25] <Philip`> They're mostly day names, and only occasional month names
  79. # [02:25] <Philip`> (as far as I can tell)
  80. # [02:25] <webben_> hmm
  81. # [02:26] <webben_> if you had days of the week in major languages, that might do it.
  82. # [02:26] <Philip`> 星期六 -- hmm, charset error
  83. # [02:26] * Joins: othermaciej_ (n=mjs@17.255.106.116)
  84. # [02:27] <Philip`> Maybe I could just look for any page with seven @abbr attributes
  85. # [02:27] <webben_> that's a bit fuzzy, might quasi-work though
  86. # [02:28] * Quits: othermaciej (n=mjs@17.203.15.181) (Read error: 104 (Connection reset by peer))
  87. # [02:28] * Joins: othermaciej (n=mjs@17.203.15.181)
  88. # [02:29] * Philip` wonders if he can write the result-processing script before the result-collecting program finishes the last 50K pages...
  89. # [02:30] <webben_> hehe :)
  90. # [02:31] <Philip`> Erk, only 7K left
  91. # [02:31] <Philip`> I think I'm going to lose
  92. # [02:32] <webben_> Quick! Code faster ;)
  93. # [02:33] * Quits: aroben (n=aroben@unaffiliated/aroben) (Read error: 104 (Connection reset by peer))
  94. # [02:33] <Philip`> I lost
  95. # [02:42] <Philip`> webben_: Is http://philip.html5.org/data/table-abbr.html vaguely useful?
  96. # [02:42] <Philip`> Uh, that table needs borders
  97. # [02:42] <Philip`> (How do I give a table borders?)
  98. # [02:42] <webben_> td {border: 1px solid black;}
  99. # [02:43] <Philip`> Ah, thanks, that doesn't look too ugly
  100. # [02:45] * Philip` updates the file
  101. # [02:45] * Quits: othermaciej_ (n=mjs@17.255.106.116) (Read error: 110 (Connection timed out))
  102. # [02:45] <Philip`> It's sorted by number of abbr on the page, so all the ones with 5 are grouped together
  103. # [02:50] <Philip`> (By "5", I obviously mean "7", though that doesn't change the validity of my statement)
  104. # [02:51] * Joins: tommorris (n=tommorri@i-83-67-98-32.freedom2surf.net)
  105. # [02:51] <Dashiva> Philip`: Are you saying the ones with 5 aren't grouped? :)
  106. # [02:52] <Hixie> well
  107. # [02:52] <Philip`> Dashiva: I am making no statement whatsoever about the ones with 5
  108. # [02:52] <Philip`> except to the extent that my statement about 7 generalises to all values of 7, including 5
  109. # [02:52] <Hixie> what we determine from this is that people suck and abbr is as much of a mess as the rest of the web
  110. # [02:52] <Hixie> good times!
  111. # [02:52] <Philip`> I'm quite surprised that that page is valid HTML5, since I was hardly even trying
  112. # [02:52] <Dashiva> I used abbr for actual abbreviations today, so all is not lost
  113. # [02:52] <Philip`> though I doubt it's a very accessible table
  114. # [02:53] <Philip`> and also it doesn't render right unless you have a beta browser
  115. # [02:55] <Philip`> Hixie: Alternatively, we can determine that Wordpress has ensured that a majority of @abbr users are using it correctly and usefully
  116. # [02:55] <Philip`> (Well, I'm guessing it's Wordpress, but I only looked at about two examples...)
  117. # [02:56] <Philip`> Oh, I'm guessing wrong, there's lots of generic calendar widgets too
  118. # [03:03] * Joins: MikeSmith (n=MikeSmit@123.127.99.86)
  119. # [03:03] * Joins: shepazu (n=schepers@123.127.99.15)
  120. # [03:12] * Quits: roc (n=roc@202.0.36.64) (Read error: 104 (Connection reset by peer))
  121. # [03:22] <Hixie> Philip`: yeah, because the odds of someone knowing what "Sun" means in teh context of a calendar are so low that it's critical that it be marked up!
  122. # [03:25] <Philip`> Hixie: It seems reasonably critical when the headers say "M, T, W, T, ..." and you're navigating through the table and want to work out what day the 22nd is (by getting your AT to read the cell's headings) and you're in a "T" column
  123. # [03:25] <Dashiva> Surely you can afford two letters
  124. # [03:25] <Philip`> Two-letter day names are ugly
  125. # [03:25] <Philip`> Three letters looks fine by takes too much space
  126. # [03:26] <Hixie> Philip`: maybe.
  127. # [03:26] <Dashiva> Then use single letter but Tu and Th
  128. # [03:26] <jruderman_> i've seen R used for thursday
  129. # [03:26] <Philip`> That's even worse
  130. # [03:26] <jruderman_> MTWRF
  131. # [03:26] <Philip`> jruderman_: That's even worser, since it doesn't even make sense
  132. # [03:26] <Dashiva> jruderman_: That ruins the WTF substring
  133. # [03:27] <jruderman_> haha
  134. # [03:27] <jruderman_> "My Japanese class isn't just a WTF class. it meets on monday and tuesday too!"
  135. # [03:29] <Philip`> Making tables uglier for a vast majority of users, to make it more accessible for a minority, doesn't seem like a tradeoff that people will often pick
  136. # [03:30] <Philip`> so there should be a way to make the table accessible whose cost is lower than that ugliness
  137. # [03:31] <jwalden> R for Thursday makes total sense
  138. # [03:31] * Joins: othermaciej_ (n=mjs@17.203.15.181)
  139. # [03:31] <Philip`> I can't stop myself reading it as "Rursday"
  140. # [03:31] * Quits: othermaciej (n=mjs@17.203.15.181) (Read error: 104 (Connection reset by peer))
  141. # [03:32] <Philip`> And you still get problems on weekends, unless you say Sunday = U or N or something
  142. # [03:32] <Dashiva> You're only allowed to do that on days ending in -amburger
  143. # [03:32] * Quits: kingryan (n=ryan@c-24-5-77-167.hsd1.ca.comcast.net)
  144. # [03:36] <Philip`> Catalan(?) calendars look fun to abbreviate, since the days are dilluns, dimarts, dimecres, dijous, divendres, dissabte, diumenge
  145. # [03:37] <MikeSmith> 日月火水木金土
  146. # [03:38] <Philip`> 日一二三四五六
  147. # [03:39] <Philip`> (Chinese?)
  148. # [03:39] <Philip`> (I'm guessing based on the web site design, not on the text)
  149. # [03:40] <MikeSmith> 日一二三四五六 is not used in Japan at least
  150. # [03:40] <MikeSmith> so must be Chinese I guess
  151. # [03:40] <MikeSmith> weird that it uses numbers for every day except Sunday
  152. # [03:40] <Philip`> Is Sunday the first or last?
  153. # [03:41] <Philip`> (or middle?)
  154. # [03:41] <MikeSmith> Sunday is the first character
  155. # [03:41] <Philip`> Okay
  156. # [03:41] <MikeSmith> the last one is six
  157. # [03:41] <MikeSmith> 日 actually means "Sun"
  158. # [03:42] <MikeSmith> or also "day"
  159. # [03:42] <blooberry> mikesmith: wow, what you had just said could be hard to interpret if you didn't know the kanji.
  160. # [03:42] <Philip`> Looks more like a chest of drawers to me
  161. # [03:43] <Hixie> looks like the svgwg's requirement for svg in text/html is that any svg thing that works in text/html must work in xml if copy-pasted
  162. # [03:43] <Hixie> i wonder if that requirement is achievable
  163. # [03:43] <Philip`> What about SVG things that don't work in text/html?
  164. # [03:43] <Philip`> (and what does "work" mean?)
  165. # [03:43] <Hixie> not sure about svg things that don't work in text/html
  166. # [03:44] <Hixie> work means that you get an equivalent rendering with no new errors if you copy and paste the fragment from the original source bytestream and reserve it as image/svg+xml
  167. # [03:45] <Hixie> which i guess means we have to do extreme validity checking, e.g. making sure there are no conflicting xmlns attributes, and not rendering any graphics if there are any errors
  168. # [03:46] <othermaciej_> Hixie: I don't see how to achieve it without introducing some level of draconian handling to text/html
  169. # [03:46] <othermaciej_> which, to my mind, largely defeats the purpose of putting svg in text/html
  170. # [03:46] <Hixie> yes, you would have to introduce some sort of draconian handling for svg subtrees
  171. # [03:46] * othermaciej_ is now known as othermaciej
  172. # [03:46] <Hixie> i'm not saying i agree with the requirement
  173. # [03:46] <Hixie> i'm saying that that is their requirement
  174. # [03:47] <Hixie> if we disagree with their requirement, then unless either we change our mind or they change their mind, we won't get consensus on what the spec should say
  175. # [03:47] <Hixie> the point might be moot if the requirement is no achievable, though
  176. # [03:48] <Hixie> so if one disagrees with the requirement, one has two lines of attack, either argue against the requirement, or argue that the requirement is not met (assuming it is indeed not met by their proposals)
  177. # [03:48] <Hixie> if one agrees with the requirement, then one would have to find a solution that meets it
  178. # [03:48] <Hixie> i don't see a sane solution that achieves it yet
  179. # [03:51] * Joins: h3h (n=w3rd@c-76-103-254-118.hsd1.ca.comcast.net)
  180. # [03:52] <Philip`> Hixie: Even if you do agree with the requirement, shouldn't you still argue that the requirement is not met if it's not met?
  181. # [03:53] <Philip`> That argument seems independent of opinions on the requirements, it's just about technical facts of the proposals
  182. # [03:54] <jruderman_> Philip`: whoever came up with the names for the days of the week clearly didn't think it through
  183. # [03:55] <Philip`> They really should have predicted that I'd have a digital watch with only space for two uppercase letters
  184. # [03:56] <h3h> isn't two easy?
  185. # [03:56] <Hixie> Philip`: sure
  186. # [03:56] <Hixie> Philip`: i
  187. # [03:56] <h3h> one is the hard case
  188. # [03:56] <Hixie> er
  189. # [03:56] <jruderman_> and that colleges would want to be able to express classes as being held on "MWF" or "TR"
  190. # [03:56] <h3h> I love Rursday
  191. # [03:56] <Hixie> Philip`: i'm just saying that if the requirement can't be met, and you're against hte requirement, it may be easier to argue that you agree with it and that it isn't met, than to disagree with it
  192. # [03:57] <Philip`> h3h: It's easy but it doesn't look very elegant
  193. # [03:57] <Hixie> Philip`: usually requirements _can_ be met, and thus arguing that it isn't met is not a successful argument against the requirement
  194. # [03:57] <h3h> true. it's easier to just use 0-6
  195. # [03:57] <Philip`> Hixie: That seems like a dishonest way to argue
  196. # [03:58] <jruderman_> http://www.google.com/search?q=Rursday+mtwrf "Did you mean: Thursday mtwrf"
  197. # [03:58] <jruderman_> <3 google
  198. # [03:58] <Hixie> Philip`: i'm not necessarily advocating it
  199. # [03:58] <Hixie> Philip`: just making an observation :-)
  200. # [03:58] <Philip`> h3h: 0-6 is not easier when sensible people think weeks start on Monday but everyone else says Sunday
  201. # [03:59] <Hixie> Philip`: (it is important to be able to recognise such debate tactics since often people use them in the standards world)
  202. # [03:59] <Philip`> Hixie: I'm not necessarily implying it's a bad thing to do :-)
  203. # [03:59] <h3h> sounds like it's ripe for an RFC
  204. # [03:59] <Hixie> (or in politics in general!)
  205. # [04:01] <Philip`> (At least numeric day-of-week input is easy, because you can accept 0 and 7 as Sunday, and people can choose whether they want to think about Su-Sa=0-6 or Mo-Su=1-7)
  206. # [04:05] * Quits: h3h (n=w3rd@c-76-103-254-118.hsd1.ca.comcast.net) ("|")
  207. # [04:06] <othermaciej> Hixie: by the way, when do you plan to update acid3?
  208. # [04:07] <othermaciej> we've been sitting on the patch to fix WebKit
  209. # [04:07] <othermaciej> (which is lame and cheesy of us, admittedly)
  210. # [04:13] * Joins: roc (n=roc@202.0.36.64)
  211. # [04:18] <Hixie> oh right
  212. # [04:18] <Hixie> will do that shortly
  213. # [04:23] * Quits: Camaban (n=alee@77-103-78-94.cable.ubr08.hawk.blueyonder.co.uk) ("Ex-Chat")
  214. # [04:30] * Joins: weinig (n=weinig@17.203.15.172)
  215. # [04:32] <Hixie> just did big updates the the faq
  216. # [04:38] * Quits: andersca (n=andersca@nat/apple/x-acb3a5bd9ea8d9ca) (Read error: 110 (Connection timed out))
  217. # [04:52] * Quits: MikeSmith (n=MikeSmit@123.127.99.86) (Excess Flood)
  218. # [04:53] * Joins: MikeSmith (n=MikeSmit@123.127.99.86)
  219. # [04:53] * Quits: MikeSmith (n=MikeSmit@123.127.99.86) (Read error: 104 (Connection reset by peer))
  220. # [04:53] * Quits: annevk (n=annevk@77.163.243.203) (Read error: 110 (Connection timed out))
  221. # [05:38] * Joins: MikeSmith (n=MikeSmit@123.127.99.86)
  222. # [06:07] * Quits: othermaciej (n=mjs@17.203.15.181)
  223. # [06:41] * Quits: csarven (n=csarven@modemcable130.251-202-24.mc.videotron.ca) ("http://www.csarven.ca/")
  224. # [07:05] * Quits: Dashiva (i=Dashiva@wikia/Dashiva) (Read error: 110 (Connection timed out))
  225. # [07:09] * Joins: billyjack (n=MikeSmit@123.127.99.32)
  226. # [07:10] * Quits: MikeSmith (n=MikeSmit@123.127.99.86) (Read error: 110 (Connection timed out))
  227. # [07:16] * Joins: Dashiva (i=Dashiva@wikia/Dashiva)
  228. # [07:17] * Joins: jgraham (n=james@81-86-217-60.dsl.pipex.com)
  229. # [07:21] * Joins: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  230. # [07:44] * Quits: Yudai (n=Yudai@p9258c3.kngwnt01.ap.so-net.ne.jp) ("SIGTERM received; exit")
  231. # [07:44] * Joins: maikmerten (n=merten@ls5laptop14.cs.uni-dortmund.de)
  232. # [07:48] * Joins: MacDome (n=eric@c-24-130-11-246.hsd1.ca.comcast.net)
  233. # [07:48] * Joins: Yudai (n=Yudai@p9258c3.kngwnt01.ap.so-net.ne.jp)
  234. # [07:51] * Quits: jruderman_ (n=jruderma@guest-226.mountainview.mozilla.com)
  235. # [07:54] * Quits: roc (n=roc@202.0.36.64)
  236. # [07:56] <Hixie> the ps3 web browser is so great i can't even click on the link to go to the acid3 test
  237. # [07:57] <Hixie> 25/100 and a renderig better than IE's
  238. # [07:57] <Hixie> not bad
  239. # [07:57] <othermaciej> heh
  240. # [07:59] * Quits: weinig (n=weinig@17.203.15.172)
  241. # [08:00] * Quits: jgraham (n=james@81-86-217-60.dsl.pipex.com) ("I get eaten by the worms")
  242. # [08:02] <Hixie> hey it passes acid1 perfectly
  243. # [08:03] * Joins: KevinMarks (n=KevinMar@c-98-207-134-151.hsd1.ca.comcast.net)
  244. # [08:10] * Joins: Lachy (n=Lachlan@ti200710a340-2662.bb.online.no)
  245. # [08:30] * billyjack is now known as MikeSmith
  246. # [08:34] * Joins: heycam (n=cam@124-168-100-30.dyn.iinet.net.au)
  247. # [08:41] * Joins: jruderman (n=jruderma@c-67-180-174-213.hsd1.ca.comcast.net)
  248. # [08:46] * Quits: MacDome (n=eric@c-24-130-11-246.hsd1.ca.comcast.net)
  249. # [08:59] <webben_> Philip`: Thanks for the table :) From an initial look through, the abbr are either wrong and harmless (), or just harmless, or helpful (albeit not always /shorter/, but when not shorter, clearer)
  250. # [09:00] <webben_> wrong and harmless e.g. empty abbr on td when td is a layout cell in a layout table, not acting as a header.
  251. # [09:01] <webben_> It's interesting to see some people using abbr in a somewhat similar way to how I've used it (not just shortening/clarifying, but also dropping widgets like links out of headers)
  252. # [09:01] <webben_> e.g. where you have << M, dropping the << link to the previous week and substituting Monday for M.
  253. # [09:02] <Hixie> apparently the ps3 browser is a netfront build of some description
  254. # [09:02] <Hixie> which explains the less than stellar results i've been getting
  255. # [09:02] <Hixie> it also appears to not support |for (x in o) ...|
  256. # [09:02] <webben_> Hixie: is it still being developed?
  257. # [09:02] <Hixie> in js
  258. # [09:02] <Hixie> webben_: no idea
  259. # [09:03] <webben_> I got the impression a lot of the console browsers are developed by those mobile browser companies who've been thrown onto the rocks by Opera Mini and WebKit-derivatives.
  260. # [09:06] <othermaciej> Opera developed the Wii browser did they not?
  261. # [09:06] <othermaciej> (or do you count them as thrown on the rocks?)
  262. # [09:07] <webben_> othermaciej: I wouldn't count Opera as a mobile browser company (by which I really mean, a company that produces dedicated rendering engines for mobile, but not for desktop)
  263. # [09:07] <webben_> so not thrown on the rocks
  264. # [09:08] <webben_> s/by Opera Mini and WebKit-derivatives/by Opera and WebKit-derivatives/
  265. # [09:08] <webben_> there's a least one browser of that sort where development has been canned entirely
  266. # [09:08] <webben_> forget which console it's for now
  267. # [09:08] <othermaciej> I'm just saying, there is no reason a console browser can't use a top tier engine
  268. # [09:09] <webben_> Oregan
  269. # [09:09] <othermaciej> I have heard of pure mobile browsers having trouble yeah
  270. # [09:09] <webben_> othermaciej: Absolutely. That's why the old products are being thrown on the rocks, as I understand it.
  271. # [09:09] <Hixie> yeah really, i don't understand why the ps3 doesn't use webkit or gecko
  272. # [09:09] <Hixie> the netfront browser is pretty crappy
  273. # [09:10] <webben_> it's funny they don't support for (x in o) given they have a whole Ajax widgets platform
  274. # [09:10] <othermaciej> they probably contracted it out and with with the lowest bidder
  275. # [09:10] <webben_> maybe this is an old version though
  276. # [09:10] <webben_> http://www.access-company.com/products/netfrontmobile/browser/widgets.html
  277. # [09:11] * webben_ tries to imagine being paid to develop a Netfront mobile widget. Can't quite see it.
  278. # [09:11] <webben_> we have way too many widget platforms
  279. # [09:12] <hsivonen> their marketing material shows the network operator as someone who should read browser marketing material. that's a bug right there.
  280. # [09:21] * Joins: MacDome (n=eric@c-24-130-11-246.hsd1.ca.comcast.net)
  281. # [09:27] * Joins: tndH (i=Rob@adsl-77-86-9-123.karoo.KCOM.COM)
  282. # [09:27] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  283. # [09:28] <hsivonen> Lachy: deleted spam and spammer from WHATWG blog
  284. # [09:39] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  285. # [09:42] * Joins: annevk (n=annevk@77.163.243.203)
  286. # [09:45] <annevk> it seems that almost all abbr= usage is wrong from http://philip.html5.org/data/table-abbr.html
  287. # [09:46] <annevk> after all, abbr= should contain the abbreviated form, not the expansion
  288. # [09:46] <Lachy> hsivonen, thanks
  289. # [09:46] <annevk> admittedly, i never got that either when i've used it so i used it incorrectly too...
  290. # [09:47] <Lachy> hmm. There's still more to delete. I'll do it shortly.
  291. # [09:47] <Lachy> I also have to upgrade to WP2.5
  292. # [09:52] <webben_> annevk: Well, it's "wrong" in a strict spec sense of not being an abbreviation; but unlike a lot of HTML usage, it's /right/ in the sense of picking up on how the attribute is meant to be used by user agents.
  293. # [09:52] <webben_> "Abbreviated names should be short since user agents may render them repeatedly. For instance, speech synthesizers may render the abbreviated headers relating to a particular cell before rendering that cell's content."
  294. # [09:53] <webben_> i.e. authors using expanded names for days are actually doing something useful for that usecase
  295. # [09:53] <webben_> even if they're tunnelling it through abbr
  296. # [09:54] <webben_> I suppose one could also argue that Monday is an "abbreviated form of the cell's content" of M in so far as M only really makes sense in the context of that row.
  297. # [09:56] <webben_> I grant it wouldn't work very well for " For visual media, the latter may be appropriate when there is insufficient space to render the full contents of the cell. " ... but then UAs could trivially detect which is shorter.
  298. # [09:56] <webben_> and in any case, no UA has implemented that visual use AFAIK.
  299. # [09:58] <webben_> see also: "Provide terse substitutes for header labels with the "abbr" attribute on TH. These will be particularly useful for future speaking technologies that can read row and column labels for each cell. Abbreviations cut down on repetition and reading time." (WCAG 1.0) ... Monday is a "summary information" for that header cell, given its context.
  300. # [09:59] <webben_> http://www.w3.org/TR/WCAG10-HTML-TECHS/#table-summary-info
  301. # [10:00] * Quits: maikmerten (n=merten@ls5laptop14.cs.uni-dortmund.de) ("Verlassend")
  302. # [10:00] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  303. # [10:00] * webben_ wonders if any mobile browsers might implement short abbr attribute in visual display.
  304. # [10:00] <webben_> I can't see how an attribute works well for that, given table headers often contain links and so forth.
  305. # [10:00] <annevk> I don't think arguing it's right is useful. It's clear that nobody understood how it was to be used.
  306. # [10:01] <webben_> They understood how it /was/ used.
  307. # [10:01] <webben_> (and is used)
  308. # [10:01] * Joins: mpt (n=mpt@canonical/launchpad/mpt)
  309. # [10:03] <webben_> annevk: I'm not so much arguing it's right, as that the way it's used is useful, and reflects a use-case envisaged in the spec and actual UA implementations.
  310. # [10:04] <webben_> Actually, given it only says "may be appropriate", I guess it's consistent with the unimplemented(?) feature too.
  311. # [10:04] * Quits: tommorris (n=tommorri@i-83-67-98-32.freedom2surf.net)
  312. # [10:05] * webben_ concludes most abbr= usage is more-or-less right in Philip's sample.
  313. # [10:07] <webben_> that is, it's not unreasonable for UAs to apply an algorithm to decide whether it /is/ more appropriate.
  314. # [10:07] * Joins: roc (n=roc@121-72-181-158.dsl.telstraclear.net)
  315. # [10:10] * Joins: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  316. # [10:12] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net) (Client Quit)
  317. # [10:12] <hsivonen> wow. issue graph looking good.
  318. # [10:13] * Joins: ROBOd (n=robod@89.122.216.38)
  319. # [10:16] <Hixie> hsivonen: notice the new blue line :-)
  320. # [10:18] <hsivonen> Hixie: what's that?
  321. # [10:18] <Hixie> number of occurances of "XXX" and "big-issue" in the spec
  322. # [10:18] <hsivonen> lots of those
  323. # [10:18] <Hixie> 508
  324. # [10:19] <hsivonen> I now see that the page documents the blue line
  325. # [10:19] * Joins: zcorpan (n=zcorpan@pat.se.opera.com)
  326. # [10:19] <hsivonen> somehow it's hard to pick up from the middle of a paragraph
  327. # [10:19] <Hixie> i added it last week when my mail was being slow, since i started working on XXXs instead of mails
  328. # [10:20] <Hixie> that's where the document.scripts, applets, etc, was added
  329. # [10:21] * Joins: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  330. # [10:21] <hsivonen> looking at my open schema bugs, unresolved WF2 questions are the main theme
  331. # [10:21] * Quits: webben_ (n=benh@dip5-fw.corp.ukl.yahoo.com)
  332. # [10:22] <Hixie> yeah
  333. # [10:22] <Hixie> i'm waiting for the task force to resolve in some way
  334. # [10:22] <Hixie> i don't want to merge wf2 if the w3c decides we're doing something else
  335. # [10:22] <Hixie> (though i'm likely to time out when i run out of other things to deal with)
  336. # [10:23] <hsivonen> I'm rather disappointed that there hasn't been more WF2 action in the Gecko and WebKit code bases by now
  337. # [10:24] <Philip`> http://code.google.com/soc/2008/webkit/about.html has a WF2 one
  338. # [10:26] <othermaciej> part of the reason we haven't moved very fast on WF2 is due to it being in semi-limbo
  339. # [10:26] <roc> yeah, didn't Hixie just say he was going to gut it?
  340. # [10:27] * annevk would like most to stay in
  341. # [10:27] <annevk> though i'm obviously biased working for an implementor and having made a test suite
  342. # [10:27] <roc> personally I want XBL2 more
  343. # [10:28] <annevk> yeah, that'd be nice
  344. # [10:28] <hsivonen> roc: I thought Hixie said the repetetion model will be axed
  345. # [10:28] <othermaciej> XBL2 is also a WebKit gsoc project
  346. # [10:28] <othermaciej> both of those are pretty ambitious
  347. # [10:28] <hsivonen> othermaciej: implementing it would be the best way to get out of limbo
  348. # [10:28] <othermaciej> likely will not get to 100% in the scope of a single summer
  349. # [10:29] <othermaciej> hsivonen: yeah, but when we implement things we almost always have comments
  350. # [10:29] <Hixie> roc: i dunno about gutted, but maybe slimmed and trimmed
  351. # [10:29] <hsivonen> I thought "everyone" was expecting hyatt do implement XBL2 in WebKit
  352. # [10:29] <othermaciej> and the path to fielding them and updating the spec is a little unclear
  353. # [10:29] <othermaciej> hyatt has a short attention span
  354. # [10:29] <othermaciej> you can expect "someone" or maybe "multiple people" to implement XBL2 in WebKit sometime
  355. # [10:31] <hsivonen> Hixie: are you considering trimming something other than the repetition model?
  356. # [10:33] <roc> also, WF2 gives you better ways to do things that you can already do today
  357. # [10:34] <roc> but features like offline apps give you ways to do things you just can't do today
  358. # [10:34] <roc> the latter are a bit more compelling
  359. # [10:34] <Hixie> yeah
  360. # [10:34] <Hixie> hsivonen: everything is always at risk
  361. # [10:34] <hsivonen> roc: yeah, but not having native sliders sucks. and having to use ARIA to make the "today" version accessible sucks
  362. # [10:35] <roc> yeah, I understand
  363. # [10:35] <othermaciej> roc: we try to balance improvements to existing stuff and brand new functionality
  364. # [10:35] <othermaciej> Selectors API would be in the former category
  365. # [10:35] <roc> so do we
  366. # [10:35] <othermaciej> arguably CSS Transitions too
  367. # [10:35] <roc> I would argue that's more in the new functionality category
  368. # [10:36] <othermaciej> really? almost every JS library has a well-optimized version
  369. # [10:36] <Hixie> it's a continuum
  370. # [10:36] <othermaciej> saving the big pile o' code and the > order of magnitude speedup is good of course
  371. # [10:36] <roc> giving the browser control of the frame rate is a great new capability
  372. # [10:37] <othermaciej> well, being able to write an AJAX combo box without a big pile of script and explicit XHR is also a great new capability
  373. # [10:37] <othermaciej> as is a slider control (though that one we already have in WebKit)
  374. # [10:37] <Hixie> the slider control was the first whatwg feature to get a public demo
  375. # [10:38] <Hixie> though i doubt steve jobs knew what he was demoing when he showed it
  376. # [10:38] <Hixie> wwdc 2004, iirc
  377. # [10:38] <roc> othermaciej: stuff like GWT exists
  378. # [10:38] <roc> I'm not saying WF2 is worthless
  379. # [10:39] <Hixie> it's not as exciting
  380. # [10:39] <othermaciej> roc: GWT is surely far more of a burden for delivering features than, say, jQuery or Dojo
  381. # [10:39] <roc> sure, they exist too
  382. # [10:39] <othermaciej> I really want <input type="search"> and <input placeholder=""> in the spec
  383. # [10:39] * Quits: Lachy (n=Lachlan@ti200710a340-2662.bb.online.no) ("This computer has gone to sleep")
  384. # [10:39] <othermaciej> so I know what we need to fix to make them spec-compatible
  385. # [10:40] <Hixie> othermaciej: get the task force disolved :-)
  386. # [10:40] <Hixie> or at least resp;ved
  387. # [10:40] <othermaciej> Hixie: I did my best!
  388. # [10:40] <Hixie> resolved
  389. # [10:40] <othermaciej> I will have to write the Architectural Consistency document myself, I guess
  390. # [10:40] <othermaciej> and fruitlessly get people to comment
  391. # [10:40] <roc> I spent a significant amount of effort polishing getBoundingClientRect/getClientRects this cycle, so I do care about improving existing stuff :-)
  392. # [10:40] <othermaciej> I guess odds are no one else on the TF will do real work though
  393. # [10:41] <annevk> i will update the webpage to point to your document :)
  394. # [10:42] <othermaciej> roc: I'm not even sure what we are debating because I almost always agree with your judgment about what is good to add to the web platform
  395. # [10:43] <Hixie> othermaciej: well, if nobody does any real work, your job is easier -- just do the work you want, and keep pushing it and giving deadlines until you basically have a de facto resolution
  396. # [10:43] <roc> yeah, it's one of those silly conversations
  397. # [10:44] * Joins: sverrej (n=sverrej@pat-tdc.opera.com)
  398. # [10:47] <annevk> so since you're all here
  399. # [10:47] <annevk> would it be problematic if i pushed rangeFromPoint and caretRangeFromPoint to v2?
  400. # [10:48] <annevk> along with all other improvements for a CSS box model API?
  401. # [10:48] <othermaciej> not sure what is in that category
  402. # [10:48] <annevk> i'm not sure either
  403. # [10:48] <othermaciej> it's not a problem for me but we may feel compelled to invent something ourselves due to high-priority developer requests
  404. # [10:49] <othermaciej> (specifically for hit testing to a character)
  405. # [10:49] <roc> RangeView is in that category too, getBCR and getCR for ranges
  406. # [10:49] <annevk> that'd be caretRangeFromPoint...
  407. # [10:49] <othermaciej> yeah
  408. # [10:49] <othermaciej> what is RangeView?
  409. # [10:50] <annevk> some additional features for Range
  410. # [10:50] <othermaciej> ah
  411. # [10:50] <annevk> to get the size of ranges
  412. # [10:50] <roc> it
  413. # [10:50] <annevk> ok, I suppose i can add caretRangeFromPoint and rangeFromPoint and have another WD first before going to Last Call
  414. # [10:51] <roc> the reverse of rangeFromPoint etc ... methods to give you the bounding boxes of text subranges
  415. # [10:51] <othermaciej> I'm still not sure what the regular rangeFromPoint is suposed to do
  416. # [10:51] <othermaciej> and how it is different
  417. # [10:51] <othermaciej> roc: yeah, that sounds useful
  418. # [10:51] <annevk> the regular rangeFromPoint is hit testing without layout calculations
  419. # [10:51] <annevk> so it would return an element range if you click in the margin
  420. # [10:51] <othermaciej> what does that mean?
  421. # [10:51] <roc> rangeFromPoint is like elementFromPoint
  422. # [10:51] <othermaciej> "without layout calculations"
  423. # [10:52] <roc> except that if you're over a text node, it can give you a particular character cell
  424. # [10:52] <othermaciej> all hit testing is based on layout
  425. # [10:52] <annevk> othermaciej, well, I mean you don't need to find the nearest text node, it just returns what's right under the cursor
  426. # [10:52] <othermaciej> what is the use case for that?
  427. # [10:52] <annevk> "cursor"
  428. # [10:52] <othermaciej> you still have to hit test line boxes if it is supposed to give character cells when you click the character
  429. # [10:53] * Joins: Lachy (n=Lachlan@pat-tdc.opera.com)
  430. # [10:53] <othermaciej> and you'd also have to define what happens when you click in the gap between lines
  431. # [10:53] <othermaciej> is that part of the line box?
  432. # [10:53] <roc> you can specify it in terms of event targeting
  433. # [10:53] <othermaciej> it sounds like it would actually be harder to implement, potentially
  434. # [10:54] <othermaciej> since every engine that supports editing must have the logic to do the equivalent of caretRangeFromPoint
  435. # [10:54] <othermaciej> mouse events don't target text nodes
  436. # [10:55] <roc> I'd argue that's a quirk of the DOM
  437. # [10:56] * Quits: Lachy (n=Lachlan@pat-tdc.opera.com) (Client Quit)
  438. # [10:56] <roc> you may be right, perhaps the use cases for rangeFromPoint are limited enough that authors should just use a combination of elementFromPoint and caretRangeFromPoint
  439. # [10:56] * Joins: Lachy (n=Lachlan@pat-tdc.opera.com)
  440. # [10:56] <othermaciej> I'm still not entirely sure what would be a use case for rangeFromPoint
  441. # [10:56] <roc> but hmm
  442. # [10:56] <othermaciej> not denying there is one
  443. # [10:56] <othermaciej> I just can't think of one off hand
  444. # [10:57] <roc> for example, people want to track the mouse cursor and show, say, the definition of the word that the mouse is hovering over
  445. # [10:57] <annevk> so if we let rangeFromPoint slide for the moment and only have caretRangeFromPoint, how would we define it?
  446. # [10:57] <roc> so if the cursor is in the padding of a block, you don't want to show anything
  447. # [10:57] <othermaciej> why isn't caretRangeFromPoint good enough?
  448. # [10:57] <othermaciej> presumbly you want to show only when you'd be between two chars of a word
  449. # [10:57] <othermaciej> not at the edge
  450. # [10:57] <roc> you don't want to return the character position for the start of the line
  451. # [10:58] <hsivonen> does XPatch context position count comment nodes and whitespace-only text nodes?
  452. # [10:58] <hsivonen> XPath
  453. # [10:58] <roc> suppose they want to show when the caret's at the start or end of a word
  454. # [10:59] <roc> or the mouse, I mean
  455. # [10:59] <roc> so the thing is, if the mouse is over the first character, you'd want to show the popup
  456. # [11:00] <roc> hmm
  457. # [11:00] <roc> I suppose if caretRangeFromPoint is defined so that when the mouse is in the padding, you get an empty range postiioned at the start of the line, but if it's over a character then you get the range containing the character
  458. # [11:00] <roc> then that case would be fine
  459. # [11:00] <othermaciej> annevk: well, I could look up what we do to implement hit testing to characters, but I am not sure if that will result in anything that gives a sane definition
  460. # [11:00] <othermaciej> roc: though, to be fair, I guess that would require you to slide partway over the first character to see it, which is annoying
  461. # [11:00] <othermaciej> you do want to be able to hit test to a glyph (and detect when you did not hit a glyph box at all)
  462. # [11:01] <othermaciej> yeah but that's not a caret range, so you'd have to change the name
  463. # [11:01] <roc> yeah
  464. # [11:01] <othermaciej> presumably for a multichar glyph you'd want to give the range of all contributing characters in such a case
  465. # [11:01] <roc> I think I agree that the "caret" range is going to be more useful than any alternative
  466. # [11:01] * Joins: maikmerten (n=merten@ls5laptop14.cs.uni-dortmund.de)
  467. # [11:01] <roc> yeah
  468. # [11:01] <othermaciej> so maybe glyphBoxRangeFromPoint
  469. # [11:01] <roc> no
  470. # [11:02] <roc> that would be confusing when dealing with ligatures
  471. # [11:02] <othermaciej> hmm yeah
  472. # [11:02] <othermaciej> you'd want to decide that some way through the ligature the chars split
  473. # [11:02] <roc> yeah
  474. # [11:02] <roc> the browser has to do that when selecting text containing ligatures, anyway
  475. # [11:04] <othermaciej> typography is hard
  476. # [11:04] <roc> tell me about it
  477. # [11:04] <othermaciej> I just did
  478. # [11:04] <othermaciej> :-)
  479. # [11:06] <roc> maybe something like selectionRangeFromPoint
  480. # [11:06] <othermaciej> a point doesn't really define a selection
  481. # [11:07] <Hixie> selectionRangeFromTwoPoints()? :-)
  482. # [11:07] <roc> where one end of the range is the nearest possible selection anchor "before" the given point, and the other end of the range is the nearest possible anchor "after" the given point
  483. # [11:07] <othermaciej> it is hard to think of a good name
  484. # [11:07] <othermaciej> Hixie: that would be redundant with getting the caret range for each point and using those as the endpoints
  485. # [11:07] <annevk> selectionRangeFromRect()
  486. # [11:07] <roc> I dunno
  487. # [11:07] <Hixie> true
  488. # [11:07] <roc> argh no
  489. # [11:07] * annevk was joking
  490. # [11:08] <annevk> othermaciej, it might help, dunno
  491. # [11:08] * Joins: webben (n=benh@nat/yahoo/x-d08f4a99f4149835)
  492. # [11:19] <annevk> roc, re: www-style, :)
  493. # [11:20] <roc> I have decided to be the bad cop
  494. # [11:20] <roc> on this issue
  495. # [11:20] * othermaciej guesses what the issue is before checking www-style
  496. # [11:21] <Hixie> what's going on in www-style these days
  497. # [11:21] * othermaciej guessed correctly
  498. # [11:21] <annevk> fonts and cssom-view rants
  499. # [11:21] <othermaciej> roc: I almost asked him if he could point to any font EULA that specifically allows use on the web in EOT form but not as regular OpenType, with specific wording
  500. # [11:22] <Hixie> seems i haven't looked at www-style for a month now
  501. # [11:22] <roc> othermaciej: that's more jdaggett's angle.
  502. # [11:22] <Hixie> oh has paul still not replied to my e-mail?
  503. # [11:22] <roc> too subtle for me
  504. # [11:22] * zcorpan hasn't looked at www-style for, uh, over a year probably
  505. # [11:22] <othermaciej> he says font vendors will sue you if you use WebFonts: http://lists.w3.org/Archives/Public/www-style/2008Apr/0372.html
  506. # [11:22] * hsivonen agree's with howcome's latest in that thread
  507. # [11:23] <hsivonen> agrees
  508. # [11:23] <hsivonen> the linguistic quality of my IRC output has gotten terrible lately
  509. # [11:23] <Hixie> http://lists.w3.org/Archives/Public/www-style/2007Nov/0263.html http://lists.w3.org/Archives/Public/www-style/2007Nov/0274.html http://lists.w3.org/Archives/Public/www-style/2007Dec/0084.html
  510. # [11:25] <annevk> hsivonen, it's not you, it's the medium
  511. # [11:25] <roc> font vendors are welcome to sue anyone they please
  512. # [11:25] <roc> as long as it's not our problem
  513. # [11:25] <hsivonen> jdaggett has a good point Re: Mac OS X fonts.
  514. # [11:25] <hsivonen> Mac OS X automates embedding the fonts Apple ships in PDFs all over. are those fonts fair game for CSS usage, too?
  515. # [11:25] <roc> whoever it was who pointed out that exactly the same issues apply to *images* was spot on
  516. # [11:26] <Hixie> not just images
  517. # [11:26] <roc> indeed, before the rise of HTML there were a lot of competing hypermedia platforms which invested heavily in strict DRM
  518. # [11:26] <Hixie> stylesheets too!
  519. # [11:26] <Hixie> and html!
  520. # [11:26] <Hixie> and scripts!
  521. # [11:26] <hsivonen> roc: it's this crazy idea that fonts, movies and music are holier than images and text
  522. # [11:26] <Hixie> in fact, fonts have _LESS_ copyright protection than anything else!
  523. # [11:27] <hsivonen> Hixie: bitmap fonts in the U.S. yes
  524. # [11:27] <roc> people went around saying that hypermedia can't be successful until we've solved the issues of making sure authors get paid
  525. # [11:27] <hsivonen> Hixie: Adobe has been pretty good at casting outline fonts as software
  526. # [11:27] <Hixie> font outlines aren't copyrightable. programs that define font hinting are, maybe.
  527. # [11:28] <Hixie> i dunno if that's ever been tested though.
  528. # [11:28] <Philip`> roc: Does that mean we needs fonts that have embedded adverts?
  529. # [11:28] <Philip`> *need
  530. # [11:28] <roc> they also made consistency requirements, so there are never broken links
  531. # [11:28] <othermaciej> I'm once again thinking of proposing my own idea for a secure font format
  532. # [11:28] <othermaciej> OpenType-rot13
  533. # [11:28] <roc> how's that different from EOT?
  534. # [11:28] <othermaciej> it would provide just as much security as EOT but it would be way easier to implement
  535. # [11:28] <roc> well yeah
  536. # [11:28] <roc> I think Paul might even argue that's actually good enough
  537. # [11:29] <hsivonen> Hixie: fortunately, people are arguing the legal angle from the U.S. point of view
  538. # [11:29] <othermaciej> roc: I admire your assumption of relative good faith on his part
  539. # [11:29] <roc> the only requirement seems to be that you can't grab a URL from somewhere, download the font in your browser and drop it into your fonts folder
  540. # [11:29] <Hixie> yeah i have to say, i'm at least as cynical as maciej at this point
  541. # [11:29] <roc> nobody out-paranoids me!
  542. # [11:30] <hsivonen> Hixie: over here, there's no exception for fonts, so per statute, the copyright situation of fonts is insane
  543. # [11:30] <othermaciej> I think Microsoft's main reason for pushing EOT is that they already have it implemented as a web font format
  544. # [11:30] * MacDome is now known as MacDomeSleep
  545. # [11:30] <hsivonen> Hixie: here the legal culture leaves lots of special cases undefined and relies on people having common sense
  546. # [11:30] <Hixie> hsivonen: ah
  547. # [11:30] <roc> but here there's nothing to lose from a good-faith assumption
  548. # [11:30] <annevk> for those who can read it, http://lists.w3.org/Archives/Member/w3c-css-wg/2008AprJun/0091.html has more information
  549. # [11:30] <othermaciej> Microsoft is a big fan of standardizing whatever they happen to have implemented already
  550. # [11:30] <roc> othermaciej: yeah
  551. # [11:30] <othermaciej> see OOXML
  552. # [11:30] <Hixie> the whole discussion is moot anyway
  553. # [11:31] <roc> hey man, Apple's a big fan of OOXML
  554. # [11:31] <Hixie> everyone (other than microsoft) should just implement TTF and move on
  555. # [11:31] <Hixie> and let IE linger in its obsolescence
  556. # [11:31] <roc> that's certainly what's going to happen
  557. # [11:31] <othermaciej> there's little chance of WebKit removing OpenType support
  558. # [11:31] <othermaciej> but we have gotten requests to also support EOT
  559. # [11:32] <Hixie> othermaciej: be strong!
  560. # [11:32] <othermaciej> Hixie: well, if some crazy bastard put it in an Acid test I might not say no
  561. # [11:32] <Hixie> hehe
  562. # [11:32] <roc> you need to be strong vs Hixie too
  563. # [11:33] * Joins: hasather_ (n=hasather@90-231-107-133-no62.tbcn.telia.com)
  564. # [11:33] <Hixie> i learnt a lot from acid3
  565. # [11:33] <Hixie> sadly my job means that my learning experiences get splattered across the web and affect a lot of engineers
  566. # [11:33] <othermaciej> acid3 didn't have any feature tested that we were truly deeply opposed to
  567. # [11:34] <Philip`> Acid3 shows that browser vendors are easily manipulated into implementing whatever you want
  568. # [11:34] <othermaciej> though some would have been much more on the back burner otherwise (mainly svg animation and fancy svg font stuff)
  569. # [11:34] <roc> I have a linger resentment over SMIL
  570. # [11:34] <roc> but I'll get over it
  571. # [11:34] <Hixie> Philip`: not really, i always got a majority agreement from the vendors before adding anything to the test
  572. # [11:34] <Hixie> roc: yeah, one of the things i learnt is that i should not have pushed for 100 tests
  573. # [11:35] <Hixie> roc: when i ran out of thigns to test, i should have stopped, not gotten other people to submit their pet peeves
  574. # [11:35] <othermaciej> I think the third-party submissions should have been reviewed more carefully
  575. # [11:35] <roc> I learned that I should have submitted *my* pet peeves
  576. # [11:35] <othermaciej> some of the submitted tests were good
  577. # [11:35] <othermaciej> the svg ones were kinda crazy
  578. # [11:35] <othermaciej> even heycam's test which I respect the thoroughness of
  579. # [11:36] <othermaciej> I thought about submitting tests but I felt it would be a bit dodgy to do so as a browser vendor
  580. # [11:36] <othermaciej> (maybe unless webkit failed them too)
  581. # [11:38] <Philip`> Hixie: I wouldn't worry about the damaging splatters of your learning experiences (/mistakes) in Acid3 - they'll be dwarfed by the problems caused by HTML5
  582. # [11:40] <othermaciej> Acid3 highlighted for me how much critical web application functionality lacks a proper spec
  583. # [11:40] <othermaciej> (many now in progress though)
  584. # [11:41] <Hixie> Philip`: oh i was thinking of html5 too when i said that
  585. # [11:43] <hsivonen> is Silverlight already in a standards pipeline at ECMA or somewhere?
  586. # [11:44] <othermaciej> not that I'm aware of
  587. # [11:44] <othermaciej> though Microsoft has let Novell clone it
  588. # [11:44] <Hixie> parts of it are already standardised
  589. # [11:44] <Hixie> dunno about the silverlight-specific APIs
  590. # [11:45] <othermaciej> C# and its standard library are standardized
  591. # [11:45] * Joins: qwert666 (n=qwert666@acbd33.neoplus.adsl.tpnet.pl)
  592. # [11:45] <othermaciej> well, insofar as an ECMA rubber stamp means anything
  593. # [11:47] * Hixie throws his lot into the webfonts debate
  594. # [11:48] * Philip` wonders if the criticisms of the OOXML-in-ECMA process apply at all to ECMAScript
  595. # [11:48] <othermaciej> ECMAScript is its own kind of hot mess
  596. # [11:48] <othermaciej> not a lotta rubber stamping happening though
  597. # [11:52] <othermaciej> ironically WebKit now has (I think) code to convert OpenType files to EOT to support OpenType WebFonts with GDI text
  598. # [11:52] <Hixie> that's fucked up
  599. # [11:52] <othermaciej> (since that is the only format that has a GDI API for in-memory activation)
  600. # [11:55] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  601. # [11:57] <roc> it is?
  602. # [11:57] <roc> bah
  603. # [11:57] * Philip` got worried by how many people use @font-face, until realising that @font-face{src} was the interesting thing, and not many (~0.03%) use that
  604. # [11:58] <Philip`> (or at least use it in inline <style> in their HTML file)
  605. # [12:02] <krijnh> MikeSmith: is http://michaelwsmithfans.org/ yours? :)
  606. # [12:04] <roc> no
  607. # [12:04] <roc> I doubt it :-)
  608. # [12:04] <MikeSmith> no
  609. # [12:04] <MikeSmith> I have no fans
  610. # [12:05] <MikeSmith> I have only a hate club
  611. # [12:05] <annevk> Hixie, document.createElement("meta") is non-conforming?!
  612. # [12:05] <krijnh> :)
  613. # [12:05] <Hixie> annevk: the meta element that comes out of it is, yes, until it has an attribute set
  614. # [12:05] * Joins: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  615. # [12:06] * Quits: shepazu (n=schepers@123.127.99.15)
  616. # [12:06] <annevk> that means it's impossible to insert elements without at some point being non-conforming
  617. # [12:07] <annevk> i'd like a way to be pedentically correct without having to resort to innerHTML tactics
  618. # [12:07] <Hixie> you know, this is pretty insane. i give all my wireless devices static IPs on my network, and my list of (actively used) static IPs now has nine separate devices on it.
  619. # [12:07] <Hixie> annevk: it doesn't matter if it's non-conforming while script is running
  620. # [12:07] <Hixie> annevk: just like it doesn't matter if the document is non-conforming while the parser is still parsing the file
  621. # [12:08] <annevk> that sounds reasonable
  622. # [12:08] <Hixie> wii, ps3, my three laptops, my girlfriend's laptop, my mac mini, my router, and my ipod
  623. # [12:09] <Lachy> Hixie, in 8.2.4 Tokenisation, the spec says "When a DOCTYPE token is created, its self-closing flag must be unset (its other state is that it be set), and its attributes list must be empty. Comment and character tokens have data." - I think that's supposed to say Start Tag token
  624. # [12:10] <Lachy> it's the end of the 3rd paragraph in that section.
  625. # [12:12] <hsivonen> speaking of Mac Mini, the rumors said there'd be a new one today.
  626. # [12:12] <hsivonen> is it really Apple announcement Tuesday today?
  627. # [12:12] <othermaciej> every Tuesday is Announcement Tuesday
  628. # [12:12] <othermaciej> well, almost every
  629. # [12:16] <Hixie> Lachy: looks like you're right. can you send mail?
  630. # [12:17] <Hixie> hsivonen: new mac minis? just refreshes, or apple awesome?
  631. # [12:17] <hsivonen> Hixie: the rumors did not say
  632. # [12:18] * hsivonen wants iMac internals without the integrated display
  633. # [12:18] <hsivonen> the 2GB RAM cap on Mini sucks
  634. # [12:19] <mpt> Is it appropriate to have multiple adjacent <nav> elements? The spec's not clear about that
  635. # [12:20] <annevk> it seems to be allowed
  636. # [12:23] <annevk> <abbr title> or <abbr aria-describedby=foo> <abbr title id=foo>
  637. # [12:24] <mpt> hmm
  638. # [12:24] <annevk> i'm joking
  639. # [12:24] <mpt> In Firefox 3 <nav> is rendered as inline
  640. # [12:24] <mpt> oh well, back to <div> :-)
  641. # [12:25] * mpt should have realized that earlier
  642. # [12:25] <Hixie> mpt: thought they'd fixed that
  643. # [12:25] <Hixie> did they only do <Section> or something?
  644. # [12:26] <mpt> (I mean, back to <nav><div>...</div><div>...</div></nav>, as opposed to <nav>...</nav><nav>...</nav>)
  645. # [12:26] <annevk> mpt, hmm, nav { display:block } ?
  646. # [12:26] <mpt> annevk, yeah, but we have can't-be-ignored text browser usage too
  647. # [12:26] <annevk> that should work fine in Firefox 3 / Opera 9.x / Safari 3.x
  648. # [12:26] <mpt> So Firefox's behavior was more of a cluestick for me, than an actual blocker
  649. # [12:28] <mpt> And then there's that pesky 4% of IE6 users
  650. # [12:28] <annevk> document.createElement('nav')
  651. # [12:28] <annevk> makes it work in Ie
  652. # [12:28] <annevk> IE, even
  653. # [12:28] <Lachy> Hixie, yeah, I'll send mail now
  654. # [12:28] <mpt> yeah, but I don't actually *need* <nav> for anything :-)
  655. # [12:28] <mpt> I was just using it because it was there
  656. # [12:28] <hsivonen> XPath is hard. Why am I not doing this in SAX/Java?
  657. # [12:29] <Hixie> Lachy: thanks!
  658. # [12:29] <annevk> mpt, now you're just making up random excuses :p
  659. # [12:29] <mpt> I need to use classes on them anyway, so <div class="foo"> is no worse than <nav class="foo">, and it works in more browsers, end of story
  660. # [12:31] <Hixie> the createElement hack is pretty freaky cool
  661. # [12:32] <hsivonen> what's the right way to check if the context node has following sibling elements or non-whitespace text nodes?
  662. # [12:33] <annevk> iterator
  663. # [12:33] <annevk> nextElementSibling doesn't actually barf if there's non whitespace text nodes
  664. # [12:33] <hsivonen> in XPath
  665. # [12:34] <annevk> dunno
  666. # [12:34] <annevk> #whatwg is the wrong place for such questions I'm afraid :)
  667. # [12:34] <hsivonen> following-sibling::node() seems to be it
  668. # [12:35] <hsivonen> for some weird reason following-sibling::* didn't work even for elements
  669. # [12:35] <krijnh> (A test for the IRC logs, like http://www.example.com/)
  670. # [12:36] <annevk> The coolest website is http://www.example.com/. I love it!
  671. # [12:36] <krijnh> :)
  672. # [12:36] <annevk> Do you know what the coolest website is (http://www.example.com/)?
  673. # [12:37] <Dashiva> hsivonen: odd, element should be default node type there...
  674. # [12:37] <annevk> In e-mails we write URLs like so: <http://www.example.com/>. Does it work?
  675. # [12:37] <Dashiva> annevk: I prefer www.example.com myself
  676. # [12:38] <annevk> krijnh, I hope no fix is deployed yet because it's a big multifail :)
  677. # [12:38] <krijnh> Not yet
  678. # [12:38] <krijnh> (^|[\\s.:;?\\-\\]<\\(])(http://[-\\w;/?:@&=+$.!~*\'()%,#]+[\\w/])(?=$|[\\s.:;?\\-\\[\\]>\\)])
  679. # [12:38] <Dashiva> Maybe he's bugtesting and not feature testing
  680. # [12:38] <krijnh> Damn nasty
  681. # [12:38] <Dashiva> My eyes
  682. # [12:39] * Joins: shepazu (n=schepers@218.246.74.90)
  683. # [12:39] <hsivonen> hrm. ::node() seems to select whitespace nodes, too
  684. # [12:39] <Dashiva> "A node test node() is true for any node of any type whatsoever."
  685. # [12:40] <hsivonen> I thought the XPath data model was supposed to omit whitespace-only nodes
  686. # [12:40] <annevk> ::following-sibling[node() != text()]
  687. # [12:41] <annevk> oh wait, whitespace
  688. # [12:42] <hsivonen> one would think that an XML-specific language made whitespace-only ignoring easy...
  689. # [12:42] * Quits: MikeSmith (n=MikeSmit@123.127.99.32) (Read error: 110 (Connection timed out))
  690. # [12:43] <krijnh> http://krijnhoetmer.nl/irc-logs/whatwg/20080422#l-669
  691. # [12:43] <krijnh> [link] or the plain uri?
  692. # [12:43] <Hixie> <link> didn't work
  693. # [12:43] <Hixie> i prefer the plain uri
  694. # [12:43] <Hixie> personally
  695. # [12:44] <Dashiva> I always figured xpath worked on a DOM, so the whitespace ignoring would take place during the parsing step instead
  696. # [12:44] <annevk> plain URI please
  697. # [12:44] <krijnh> Done
  698. # [12:44] <annevk> and you need to add > to the lits of characters
  699. # [12:44] <annevk> and < prolly
  700. # [12:45] * Joins: Camaban (n=alee@77-103-78-94.cable.ubr08.hawk.blueyonder.co.uk)
  701. # [12:45] <hsivonen> how can testing for following sibling presence be this hard?
  702. # [12:45] <annevk> also, some weird semi colon is added after the <> link
  703. # [12:45] <annevk> hmm
  704. # [12:45] <Hixie> hsivonen: what are you doing?
  705. # [12:45] <hsivonen> Hixie: testing if a first table child of datagrid has following siblings
  706. # [12:45] <krijnh> That's weird, does work on http://krijnhoetmer.nl/zooi/php/preg_replace_2.php
  707. # [12:46] <Hixie> hsivonen: in some schema language?
  708. # [12:46] <hsivonen> Hixie: yes
  709. # [12:46] <annevk> krijnh, is it some htmlentities cleanup weirdness later?
  710. # [12:46] <Hixie> hsivonen: sorry to hear that
  711. # [12:46] <annevk> krijnh, or maybe the htmlentities happens first which is what messes it up?
  712. # [12:46] <hsivonen> Hixie: I'm going to implement it in Java later anyway. This is supposed to be a rapid prototype
  713. # [12:47] <Hixie> heh
  714. # [12:47] <hsivonen> but XPath doesn't make this case exactly rapid
  715. # [12:47] <krijnh> Ah, doh
  716. # [12:47] <Hixie> rapid, you say :-)
  717. # [12:47] <Dashiva> Rapid descent into frustration
  718. # [12:47] <krijnh> Yeah, it's first htmlspecialchared
  719. # [12:47] <hsivonen> I mean, you'd think XPath could express this sort of thing!
  720. # [12:48] <annevk> krijnh, probably better to reverse that order
  721. # [12:48] <hsivonen> hmm. perhaps I should check that the context node is the last child of its parent
  722. # [12:48] <Dashiva> Or next-to-last with whitespace following
  723. # [12:48] <krijnh> annevk: then <a href="foo"> gets htmlspecialchared
  724. # [12:49] <annevk> krijnh, oops, duh
  725. # [12:49] <Dashiva> krijnh: urlencode it first then :)
  726. # [12:49] <krijnh> You guys just shouldn't use < and > around your links :)
  727. # [12:50] <krijnh> Or just str_replace('&gt</a>;', '</a>&gt;') :>
  728. # [12:51] <annevk> or include end at & but not at &amp;
  729. # [12:51] <annevk> s/include//
  730. # [12:51] <annevk> for the URI regexps
  731. # [12:51] <annevk> this might make it even more insane :)
  732. # [12:52] <Dashiva> How 'bout not inserting the URLs, but rather a placeholder, and doing a replace on the placeholders at the very end
  733. # [12:52] <Hixie> krijnh: while you're working on the logs, any chance i could get you to change the line counts on the front page to not count the lines that the log pages filter out?
  734. # [12:52] <Hixie> e.g. joins, parts
  735. # [12:54] <krijnh> I don't filter those on the homepage
  736. # [12:54] <krijnh> That's just a simple count on the array of all lines
  737. # [12:54] <Hixie> yeah
  738. # [12:54] <krijnh> What a mess
  739. # [12:54] <krijnh> :D
  740. # [12:54] <Hixie> sometimes i see a log has a lot of lines and i excitingly go to see what was said and i just see two lines, log started, log ended. :-)
  741. # [12:54] <Dashiva> Just make the filtering be off by default, then people won't notice :)
  742. # [12:56] <krijnh> <http://www.example.com/> works now
  743. # [12:57] * Joins: myakura (n=myakura@p1215-ipbf3008marunouchi.tokyo.ocn.ne.jp)
  744. # [12:58] <zcorpan> [http://www.example.com/] http://www.example.com/, {http://www.example.com/}
  745. # [12:59] <zcorpan> hmm opera includes } in the link
  746. # [12:59] <krijnh> What the
  747. # [13:01] <jwalden> by the way, so people know, I'm working on converting Mozilla's postMessage tests to work with an async postMessage, should that happen; it is an extremely painful process to do so
  748. # [13:01] <jwalden> converting http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/dom/tests/mochitest/whatwg/test_postMessage_origin.xhtml&rev=1.2&mark=412-432#388 took around three hours to do and get right, with multiply-nested setTimeouts in at least one place
  749. # [13:02] <jwalden> my conclusion is that sequential communication using postMessage is significantly harder when postMessage works async, as opposed to when it is sync
  750. # [13:03] <Hixie> jwalden :-/
  751. # [13:03] <Hixie> er, with fewer spaces
  752. # [13:03] <Hixie> on the long run we really want a pipe system link my endpoint proposal
  753. # [13:03] <Hixie> that would make it much easier i imagine
  754. # [13:04] <jwalden> I don't know how common back-and-forth will be as opposed to one-shotters, but I don't think it'll be fun when it happens
  755. # [13:04] <jwalden> some of the tests Just Worked, but those were the ones that tested one thing in isolation
  756. # [13:07] * Quits: qwert666 (n=qwert666@acbd33.neoplus.adsl.tpnet.pl) ("Leaving")
  757. # [13:10] <annevk> can Firefox still change?
  758. # [13:10] <annevk> for Firefox 3, that is
  759. # [13:10] <roc> probably
  760. # [13:10] <krijnh> Hixie: fixed
  761. # [13:10] <Philip`> Automated insertion of <abbr> is great when people use that kind of thing on blogs and it makes their XHTML examples print like <HTML xmlns="http://www.w3.org/1999/XHTML"> where the uppercase bits are in <acronym>s (and styled to uppercase)
  762. # [13:10] <krijnh> I think
  763. # [13:11] <Hixie> krijnh: thanks!
  764. # [13:11] <krijnh> It's pretty slow though :/
  765. # [13:12] <annevk> krijnh, could you also filter session start, session end and such?
  766. # [13:12] <annevk> krijnh, so that for effectively empty logs it says 0 rather than 4
  767. # [13:12] <Hixie> hm, entities allow one to include control characters and permanently undefined unicode characters
  768. # [13:13] <annevk> there are raised issues about that
  769. # [13:13] <annevk> in particular the way entities are locked to UTF-16 in some implementations is interesting (and potentially troublesome)
  770. # [13:15] <zcorpan> what alt text should the randomly selected image on http://ln.hixie.ch/ have? :) same as it has on Flickr?
  771. # [13:15] <Philip`> zcorpan: alt="" since it's decorative and doesn't otherwise enhance the value of the page
  772. # [13:15] <jwalden> I have async implemented; the patch is a bit complicated due to the way you have to split computation and use to avoid timing issues, but it's not bad
  773. # [13:16] <krijnh> annevk: done
  774. # [13:16] <jwalden> updating the tests will easily eclipse the time needed to change the implementation
  775. # [13:16] <annevk> krijnh, it still reports 1 for some reason...
  776. # [13:16] <annevk> weird
  777. # [13:16] <jwalden> I'm guessing at least a factor of three
  778. # [13:16] <krijnh> No it doesn't :)
  779. # [13:17] <annevk> no some logs report -1
  780. # [13:17] <annevk> :p
  781. # [13:17] <annevk> now*
  782. # [13:17] <annevk> i guess that's acceptable
  783. # [13:17] <krijnh> Yeah, that's only for 18 days
  784. # [13:17] <jwalden> right now I'm staring at http://mxr.mozilla.org/mozilla/source/dom/tests/mochitest/dom-level0/test_setting_document.domain_idn.html?force=1 and writhing in pain
  785. # [13:17] <jwalden> sequential city, there
  786. # [13:18] <krijnh> {http://example.com/}
  787. # [13:19] <krijnh> { http://example.com/ }
  788. # [13:19] <krijnh> <-- brain boiled
  789. # [13:19] <Philip`> http://sub1.exämple.test
  790. # [13:19] <Philip`> krijnh: ^ doesn't work :-(
  791. # [13:20] <annevk> krijnh, the regexp is now failing everywhere :(
  792. # [13:20] <krijnh> :/
  793. # [13:20] <annevk> "http://example.com/" is another one
  794. # [13:20] * Quits: roc (n=roc@121-72-181-158.dsl.telstraclear.net)
  795. # [13:22] <Hixie> krijnh: you now have plenty of cases to add to some smoketests :-)
  796. # [13:22] * Joins: qwert666 (n=qwert666@acbd33.neoplus.adsl.tpnet.pl)
  797. # [13:22] <Philip`> http://robert.accettura.com/blog/2008/04/15/shell-stats/ - auto-acronym failure
  798. # [13:23] <Hixie> do you think ben's recent e-mail is a request for someone to explain how we addressed that in wf2?
  799. # [13:24] * Quits: webben (n=benh@nat/yahoo/x-d08f4a99f4149835)
  800. # [13:24] <annevk> yes, and it also seems to be a request for XForms
  801. # [13:24] <annevk> Philip`, auto-acronym is a misfeature imo
  802. # [13:24] <Hixie> trying to work out if i should bother explaining wf2 in this case
  803. # [13:24] <Hixie> or let someone else do it
  804. # [13:25] * krijnh needs an IRClogger5
  805. # [13:25] <Hixie> ok bed time
  806. # [13:25] <Hixie> nn
  807. # [13:26] <Philip`> Is a required checkbox like on those forms with "I accept the terms and conditions that I didn't read: [x]" where you have to check it?
  808. # [13:27] <annevk> yes
  809. # [13:27] * Joins: webben (n=benh@nat/yahoo/x-ea49eb6dc1890532)
  810. # [13:27] <Philip`> A helpful UA should check that box automatically
  811. # [13:27] <annevk> that depends on the user
  812. # [13:28] * Quits: webben (n=benh@nat/yahoo/x-ea49eb6dc1890532) (Client Quit)
  813. # [13:28] <annevk> i would rather it did not check it automatically
  814. # [13:28] <Philip`> The only thing you're ever going to do with the checkbox is check it, so the UA might as well save you the effort
  815. # [13:28] * Philip` reads WF2
  816. # [13:28] <annevk> the checkbox also serves as a reminder that you have to check something else
  817. # [13:29] <Philip`> Oh, it sounds more useful when you have >1 checkbox with the same name
  818. # [13:29] <annevk> if the ua has already checked it you will not get that reminder when you submit the form
  819. # [13:38] * Philip` tries replying to explain what WF2 does
  820. # [13:55] * hsivonen expects a bikeshed about labeled vs. labelled
  821. # [13:56] <Lachy> hsivonen, why do you expect that to become a bikeshed?
  822. # [13:57] <hsivonen> oh dear :-)
  823. # [13:57] <Dashiva> We got through referrer without too many paint marks, didn't we?
  824. # [13:58] <hsivonen> ARIA even has a note about it
  825. # [13:58] <Philip`> The more common usage is "bike shed", not "bikeshed"
  826. # [13:58] <Philip`> Sadly the OED has neither :-(
  827. # [13:59] <Lachy> I expect the <abbr> vs. <abbr title=""> to become a bikeshed (or bike shed to keep Philip` happy)
  828. # [14:03] <Philip`> That's easy to solve by just making <abbr> conforming, because it already exists and it's at least useful as a style hook :-)
  829. # [14:05] * Philip` doesn't actually remember ever having seen a bike( )shed
  830. # [14:06] <Lachy> Philip`, exactly. It's for all those authors who want dotted borders rendered underneath all abbreviations in their page, without serving any other function :-)
  831. # [14:06] <Philip`> (I see bike racks everywhere, and sometimes covered ones, and one underground one, but that's all I can think of)
  832. # [14:07] <Philip`> Lachy: Firefox and Opera don't do dotted underlines (or any other styling) on title-less abbr
  833. # [14:08] <Philip`> which is good, because otherwise it would confuse users into looking for tooltips
  834. # [14:08] <Philip`> and authors can add small-caps styling to make their acronyms look nice
  835. # [14:08] <Lachy> Philip`, maybe you have seen a bike shed, but because you can't see through walls, you didn't realise there were bikes inside.
  836. # [14:09] <Lachy> has that behaviour changed? I thought older versions of FF used to underline them anyway
  837. # [14:09] <Philip`> Lachy: I would hope most bikesheds have doors, in which case there's a non-negligible probability that looking at one will reveal the contents
  838. # [14:09] <Lachy> yeah, most sheds have doors.
  839. # [14:09] <Philip`> Lachy: Not sure - I'm testing FF2
  840. # [14:10] <Lachy> When I was younger, our bikes were kept in a shed at home.
  841. # [14:10] <Philip`> Mine was kept in our garage
  842. # [14:10] <Philip`> Actually, it still is in there
  843. # [14:11] * Quits: jmb (n=jmb@login.ecs.soton.ac.uk) (Read error: 104 (Connection reset by peer))
  844. # [14:11] * Joins: jmb (n=jmb@login.ecs.soton.ac.uk)
  845. # [14:16] <jwalden> more on async postMessage, splitting up computations and object creation between at-time-postMessage-is-called and at-time-when-event-is-dispatched is a somewhat touchy business, in that there's a very specific way it has to be done to avoid time-of-check-to-time-of-use concerns
  846. # [14:17] <jwalden> gotta calculate the caller's origin at postMessage time, gotta compare the computed target origin against the target's origin at dispatch time, etc.
  847. # [14:18] <jwalden> I don't think you can just reuse generic async-event-dispatch code to implement this
  848. # [14:18] <jwalden> not safely, at least
  849. # [14:19] <zcorpan> Error: Required attributes missing on element script.
  850. # [14:19] <zcorpan> From line 19, column 3; to line 19, column 24
  851. # [14:19] <zcorpan> esheet>↩ <script src=status.js></scri
  852. # [14:19] <zcorpan> Error: Required children missing from element table.
  853. # [14:19] <zcorpan> From line 48180, column 4; to line 48180, column 11
  854. # [14:19] <zcorpan> </tr>↩ </table>↩ <!
  855. # [14:20] <zcorpan> hsivonen, Hixie: ^
  856. # [14:20] <zcorpan> which children are missing from table?
  857. # [14:23] <zcorpan> (Total execution time 282728 milliseconds, with image report, without show source)
  858. # [14:23] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) ("Ex-Chat")
  859. # [14:24] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  860. # [14:25] <hsivonen> zcorpan: are you validating the spec?
  861. # [14:25] * Joins: jgraham (n=james@81-86-217-60.dsl.pipex.com)
  862. # [14:26] <zcorpan> hsivonen: yeah, the whatwg version
  863. # [14:26] * Joins: webben (n=benh@nat/yahoo/x-5854e2d29421be5c)
  864. # [14:26] <hsivonen> zcorpan: I see only one message: legacy doctype
  865. # [14:27] <zcorpan> hsivonen: on validator.nu, not html5.validator.nu
  866. # [14:27] * Joins: aroben (n=aroben@unaffiliated/aroben)
  867. # [14:27] <hsivonen> oh
  868. # [14:28] <zcorpan> (i have 5 messages: text/html->html parser, doctype without SI, xhtml 1.0 schema, 2 errors)
  869. # [14:29] <hsivonen> it's indeed horribly slow
  870. # [14:29] <hsivonen> I think I should run it in a profiler locally
  871. # [14:29] * hsivonen suspects Schematron
  872. # [14:32] * Quits: jwalden (n=waldo@RANDOM-THREE-O-EIGHT.MIT.EDU) (Remote closed the connection)
  873. # [14:32] <zcorpan> HTTP ERROR: 500
  874. # [14:32] <zcorpan> Java heap space
  875. # [14:32] <zcorpan> RequestURI=/
  876. # [14:32] <zcorpan> Caused by:
  877. # [14:32] <zcorpan> java.lang.OutOfMemoryError: Java heap space
  878. # [14:32] <zcorpan> (trying to validate again without image report)
  879. # [14:36] * mpt scowls at elinks
  880. # [14:36] <mpt> elinks renders alt=" " as nothing, but alt="" as [IMG]
  881. # [14:37] <Philip`> Can you configure it to handle images differently?
  882. # [14:37] <Philip`> (I remember something like that in either Lynx or Links)
  883. # [14:37] <Philip`> (By the way, it's really very stupid to choose a name that's a homophone of a very similar project :-( )
  884. # [14:39] <mpt> In Lynx you can type "*" to show links to all images
  885. # [14:39] <mpt> There doesn't seem to be an equivalent option in elinks
  886. # [14:40] <Philip`> http://en.wikipedia.org/wiki/Links_(web_browser) - "The focus on intuitive usability makes it suitable as a web browser for low-end terminals in libraries, Internet cafes etc." - uh, if you're running an Internet cafe, your whole business revolves around giving people web access, so I'm not sure Links is the best idea
  887. # [14:41] * Quits: jgraham (n=james@81-86-217-60.dsl.pipex.com) ("I get eaten by the worms")
  888. # [14:41] <mpt> Lynx does the right thing with alt=""
  889. # [14:42] * mpt wonders whether to s/alt=\"\"/alt=\" \"/g
  890. # [14:42] <Philip`> alt=" " is non-conforming HTML5 in almost all cases
  891. # [14:43] <annevk> it should be conforming for decorative images...
  892. # [14:44] <mpt> "Focus on intuitive usability"? Who writes that crud?
  893. # [14:44] <Philip`> Do any UAs treat <a href=...><img alt=" "> Text</a> differently from <a href=...><img alt=""> Text</a> ?
  894. # [14:45] <Philip`> Actually, I can't remember what I was thinking of in that case
  895. # [14:45] <Philip`> so I'm not sure why it's relevant to anything at all, so please ignore me
  896. # [14:45] <mpt> darn
  897. # [14:46] <mpt> (the answer was "yes, elinks does")
  898. # [14:47] <Philip`> Maybe I was thinking about whether e.g. some AT might render it as "Linked Image Text" vs "Text", because it makes them think it's a significant image
  899. # [14:47] <Philip`> but I don't think that question makes sense anyway
  900. # [14:47] * Philip` gives up
  901. # [14:48] <hsivonen> whoa! Validator.nu just did something really weird and scary
  902. # [14:48] <zcorpan> hsivonen: did it steal a candy?
  903. # [14:49] <hsivonen> it's feeding my browser what looks like binary junk
  904. # [14:49] <zcorpan> ouch
  905. # [14:49] <hsivonen> I hope it's just gzip going wrong and not a privileged memory dump
  906. # [14:49] <Philip`> Easy way to find out: try compressing the output
  907. # [14:50] <Philip`> and if it compresses much, it's not gzip
  908. # [14:50] <zcorpan> can you take the junk through some content sniffing codepath and see if it's handled as something?
  909. # [14:50] <Philip`> Or just search for your password strings in there
  910. # [14:51] <hsivonen> how do I get the original bytes out of Firefox?
  911. # [14:52] * Philip` doesn't know if 'File / Save Page As / Web Page, HTML only' saves the raw data or tries fiddling with encodings
  912. # [14:52] <hsivonen> the schematron stuff I have for XHTML 1.0 is written really inefficiently
  913. # [14:52] <Philip`> but I'd tend to hope it's the raw data
  914. # [14:54] <hsivonen> going forward, I really need to get rid of the Schematron presets
  915. # [14:54] <hsivonen> and then isolate the custom schema stuff from what most people use
  916. # [14:54] <mpt> hsivonen, I think if Firefox had the original bytes, it wouldn't need to reload the page to change encodings
  917. # [14:55] <mpt> (which can be a dataloss problem)
  918. # [14:55] * Quits: Camaban (n=alee@77-103-78-94.cable.ubr08.hawk.blueyonder.co.uk) (Connection timed out)
  919. # [14:55] <hsivonen> custom schemas are a huge DoS attack vector
  920. # [14:55] <zcorpan> is "URL percentage escape non-unreserved characters in a string" defined somewhere?
  921. # [14:57] <hsivonen> $ file Downloads/validator.nu.html
  922. # [14:57] <hsivonen> Downloads/validator.nu.html: gzip compressed data, from FAT filesystem (MS-DOS, OS/2, NT)
  923. # [14:58] <hsivonen> I wonder why Firefox didn't decompress it
  924. # [15:00] <Philip`> Did it get sent with the right headers?
  925. # [15:03] <hsivonen> Philip`: I don't know how to tell after the fact
  926. # [15:04] <zcorpan> which unicode normalisation form should be used when percent-escaping URLs?
  927. # [15:05] <Philip`> hsivonen: Oh, good point
  928. # [15:07] <hsivonen> zcorpan: no normalization
  929. # [15:07] <hsivonen> zcorpan: but if you are minting a new IRI, you should use NFKC
  930. # [15:09] <zcorpan> i meant converting a random string to a percent-escaped URL
  931. # [15:09] <zcorpan> thanks
  932. # [15:09] <hsivonen> the Schematron that gets generated when Schematron is embedded in RELAX NG is so inefficient it isn't even funny
  933. # [15:10] * Joins: jgraham (n=james@81-86-217-60.dsl.pipex.com)
  934. # [15:17] * Quits: qwert666 (n=qwert666@acbd33.neoplus.adsl.tpnet.pl) ("Leaving")
  935. # [15:29] <hsivonen> even profiling this is insanely slow
  936. # [15:30] <hsivonen> I don't need a profiler to tell me that Schematron sucks
  937. # [15:31] <Philip`> Would you get the same results from profiling a smaller test case?
  938. # [15:31] <hsivonen> not necessarily
  939. # [15:36] <hsivonen> still slow but not insanely so...
  940. # [15:37] <hsivonen> local dev version that is
  941. # [15:38] <hsivonen> the schematron bit that check for id and name sharing the same namespace are bad for perf
  942. # [15:42] <hsivonen> I wonder if Saxon has a main loop somewhere, so that I could insert a wall clock test against runaway Schematron
  943. # [15:43] <hsivonen> though checking system clock and accessing a ThreadLocal in a hotspot would suck, too
  944. # [15:45] <Philip`> Is it bad in HotSpot to have a separate alarm timer thread, which sleeps then interrupts the useful thread, and the useful thread checks for interruptions occasionally?
  945. # [15:46] * Joins: csarven (i=csarven@on-irc.csarven.ca)
  946. # [15:46] <hsivonen> Philip`: killing a thread from the outside is dangerous in the general case
  947. # [15:47] <hsivonen> Philip`: and making the potential problem thread poll for a stop condition is problemtic as mentioned above
  948. # [15:48] <Philip`> But interrupt should be safe, since that only does anything when there's an explicit check and it won't clobber internal locks or do whatever other bad things there are
  949. # [15:49] <hsivonen> Philip`: to do it without a ThreadLocal, Saxon would need to pass the polling object around...
  950. # [15:49] <Philip`> I was thinking of Thread.interrupted()
  951. # [15:50] <hsivonen> oh.
  952. # [15:50] <Philip`> which doesn't need an object, and isn't explicitly ThreadLocal
  953. # [15:50] * hsivonen goes read JavaDoc
  954. # [15:50] <hsivonen> argh. looks like about.validator.nu just died
  955. # [15:51] <annevk> wfm
  956. # [15:51] <Philip`> (No idea how it's implemented in JVMs, though)
  957. # [15:51] <annevk> oh wait, about.validator.nu doesn't
  958. # [15:53] <hsivonen> Philip`: indeed it looks like interrupt() could work
  959. # [15:58] * Joins: phsiao (n=shawn@nat/ibm/x-7b6a324d41170fb8)
  960. # [16:00] <hsivonen> I wonder what's going on on the machine hosting about.validator.nu
  961. # [16:00] <hsivonen> the CPU is not pegged
  962. # [16:00] <hsivonen> I wonder if something is clogging the network
  963. # [16:01] * Joins: gsnedders (n=gsnedder@host217-44-37-113.range217-44.btcentralplus.com)
  964. # [16:01] <Philip`> ping seems to work fine, with constant low latency
  965. # [16:18] * Quits: jgraham (n=james@81-86-217-60.dsl.pipex.com) ("I get eaten by the worms")
  966. # [16:26] <hsivonen> looks like someone from China is leeching stuff from the server using a really impolite bot
  967. # [16:27] * Joins: jgraham (n=james@81-86-217-60.dsl.pipex.com)
  968. # [16:30] <zcorpan> wow, i thought html5 said that tabindex=-1 means "focusable but not in tab order"
  969. # [16:31] <annevk> the only problem with impl is the handling of invalid values it seems
  970. # [16:32] <annevk> HTML5 needs fixing anyhow
  971. # [16:32] <hsivonen> zcorpan: validating the spec as HTML 4 now works with reasonable performance
  972. # [16:33] <hsivonen> zcorpan: thanks
  973. # [16:34] <hsivonen> Hixie: the table error that zcorpan spotted is that the whole entity table is in thead
  974. # [16:38] * Quits: myakura (n=myakura@p1215-ipbf3008marunouchi.tokyo.ocn.ne.jp) ("Leaving...")
  975. # [16:38] <zcorpan> hsivonen: wow sweet. Total execution time 6310 milliseconds.
  976. # [16:38] <zcorpan> 5365 milliseconds without image report
  977. # [16:40] * Philip` wonders at the resolution of the clock used for those timings
  978. # [16:40] <zcorpan> pretty good compared to 282728 milliseconds and HTTP ERROR: 500, respectively :)
  979. # [16:41] <zcorpan> Philip`: well i counted to 6 for the first so it's accurate enough for me :)
  980. # [16:41] <hsivonen> Philip`: wouldn't badness happen if the thread was blocking on IO when a watchdog interrupted it?
  981. # [16:49] <Philip`> hsivonen: The blocking method would clean up after itself and throw an InterruptedException, and the caller should be expecting that exception and so nothing bad will happen
  982. # [16:49] * Quits: maikmerten (n=merten@ls5laptop14.cs.uni-dortmund.de) (Remote closed the connection)
  983. # [16:50] <Philip`> (assuming the blocking method is interruptible (and declares it throws InterruptedException), which is hopefully the case, because otherwise it'd get messier)
  984. # [16:54] <hsivonen> Philip`: it still seems like a bad idea to interrupt write to the ServletOutputStream
  985. # [16:55] <hsivonen> because if it breaks, the user will not get any feedback
  986. # [16:57] <Philip`> Oh, if that's what you mean by badness then it does sound like badness
  987. # [16:57] * Joins: andersca (n=andersca@c-71-198-2-225.hsd1.ca.comcast.net)
  988. # [16:57] <Philip`> (I was thinking more of the deadlock-the-entire-VM badness, like in Thread.destroy())
  989. # [16:59] <hsivonen> Philip`: I suppose I could wrap the ServletOutputStream in an object that raises a "don't inturrupt right now" flag when in servlet IO
  990. # [16:59] <Philip`> That sounds potentially delicate
  991. # [16:59] <hsivonen> the other potential problem is avoiding putting Commons HttpClient in a bad state
  992. # [17:08] * Joins: hsivonen_ (n=hsivonen@kekkonen.cs.hut.fi)
  993. # [17:12] * Quits: hsivonen (n=hsivonen@kekkonen.cs.hut.fi) (Nick collision from services.)
  994. # [17:13] * hsivonen_ is now known as hsivonen
  995. # [17:24] <annevk> in case it was missed somehow: http://intertwingly.net/blog/2008/04/19/Ingrates#c1208838277
  996. # [17:35] * Quits: sverrej (n=sverrej@pat-tdc.opera.com) (Remote closed the connection)
  997. # [17:35] * Quits: Lachy (n=Lachlan@pat-tdc.opera.com) ("This computer has gone to sleep")
  998. # [17:43] <hsivonen> annevk: I think that's different from general distributed extensibility.
  999. # [17:43] <hsivonen> annevk: it's just about using HTML to serve as an indirection mechanism to get a less pretty or less stable URI
  1000. # [17:44] <hsivonen> seems like a case for registering a rel value on the wiki
  1001. # [17:44] <annevk> You lost me.
  1002. # [17:44] <annevk> :)
  1003. # [17:45] <hsivonen> annevk: Re: what markp referred to Sam referring
  1004. # [17:46] <annevk> what does it have to do with URIs though?
  1005. # [17:46] <annevk> (rel values can be registered on a wiki)
  1006. # [17:50] * Quits: andersca (n=andersca@c-71-198-2-225.hsd1.ca.comcast.net)
  1007. # [17:55] * Joins: Lachy (n=Lachlan@ti200710a340-2662.bb.online.no)
  1008. # [17:58] * Joins: sverrej (n=sverrej@pat-tdc.opera.com)
  1009. # [17:58] <hsivonen> hmm am I misunderstanding the whole issue?
  1010. # [17:59] <hsivonen> X-XRDS-Location is an URI autodiscovery mechanism, no?
  1011. # [18:00] <hsivonen> just like feed autodiscovery, openid and pingback
  1012. # [18:01] * Quits: shepazu (n=schepers@218.246.74.90) (Read error: 110 (Connection timed out))
  1013. # [18:01] <annevk> Oh yes. The discussion is whether <meta http-equiv> shoud be extensible or not and Sam Ruby points to data- attributes as the supposedly provided alternative to confuse matters or something...
  1014. # [18:02] <annevk> Well, "discussion"
  1015. # [18:04] <Lachy> which thread are you referring to?
  1016. # [18:05] <hsivonen> Lachy: the one anne linked above
  1017. # [18:05] <hsivonen> http://intertwingly.net/blog/2008/04/19/Ingrates
  1018. # [18:06] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) (Read error: 110 (Connection timed out))
  1019. # [18:07] <hsivonen> Philip`: would I be crazy if I managed "don't kill thread" flags around IO and then used the dangerous thread stopping mechanism when the flag isn't set?
  1020. # [18:10] <Lachy> hsivonen, ok. I missed that earlier since I wasn't in the channel
  1021. # [18:10] <annevk> btw, it's almost certain I get a lightning talk spot at XTech on HTML 5
  1022. # [18:10] <annevk> if people have some input for that let me know
  1023. # [18:11] <hsivonen> annevk: did you see my three points?
  1024. # [18:15] <hsivonen> oops. ten points
  1025. # [18:15] <hsivonen> I wonder why I typed "three"
  1026. # [18:19] * Quits: KevinMarks (n=KevinMar@c-98-207-134-151.hsd1.ca.comcast.net) ("The computer fell asleep")
  1027. # [18:20] <hsivonen> http://pastebin.ca/992541
  1028. # [18:30] * Joins: andersca (n=andersca@nat/apple/x-a3e7dd9e5f97f5e1)
  1029. # [18:40] * Quits: jgraham (n=james@81-86-217-60.dsl.pipex.com) ("I get eaten by the worms")
  1030. # [18:41] * Quits: zcorpan (n=zcorpan@pat.se.opera.com) (Read error: 145 (Connection timed out))
  1031. # [18:44] * Quits: MacDomeSleep (n=eric@c-24-130-11-246.hsd1.ca.comcast.net)
  1032. # [18:46] * Joins: maikmerten (n=maikmert@Lae8f.l.pppool.de)
  1033. # [18:49] * Joins: weinig (n=weinig@adsl-75-36-142-105.dsl.pltn13.sbcglobal.net)
  1034. # [18:55] <gsnedders> Do you think someone should go and help cwilso find his keys?
  1035. # [19:00] * Joins: KevinMarks (n=KevinMar@nat/google/x-318c092a8538b00c)
  1036. # [19:01] * Quits: KevinMarks (n=KevinMar@nat/google/x-318c092a8538b00c) (Remote closed the connection)
  1037. # [19:13] * Quits: sverrej (n=sverrej@pat-tdc.opera.com) (Read error: 110 (Connection timed out))
  1038. # [19:15] * Quits: weinig (n=weinig@adsl-75-36-142-105.dsl.pltn13.sbcglobal.net)
  1039. # [19:20] * Joins: jgraham (n=james@81-86-217-60.dsl.pipex.com)
  1040. # [19:21] * Quits: maikmerten (n=maikmert@Lae8f.l.pppool.de) ("Leaving")
  1041. # [19:35] * aroben is now known as aroben|meeting
  1042. # [19:37] * Quits: jruderman (n=jruderma@c-67-180-174-213.hsd1.ca.comcast.net)
  1043. # [19:49] * Joins: KevinMarks (n=KevinMar@nat/google/x-8dae4e4625d301df)
  1044. # [19:54] * aroben|meeting is now known as aroben
  1045. # [20:05] * Joins: virtuelv (n=virtuelv@225.80-203-100.nextgentel.com)
  1046. # [20:07] * Quits: KevinMarks (n=KevinMar@nat/google/x-8dae4e4625d301df) ("The computer fell asleep")
  1047. # [20:07] * Joins: roc (n=roc@121-72-181-158.dsl.telstraclear.net)
  1048. # [20:09] * Joins: Camaban (n=alee@77-102-120-245.cable.ubr08.hawk.blueyonder.co.uk)
  1049. # [20:17] * Joins: Camaban_ (n=alee@77-103-78-94.cable.ubr08.hawk.blueyonder.co.uk)
  1050. # [20:28] * Quits: Camaban (n=alee@77-102-120-245.cable.ubr08.hawk.blueyonder.co.uk) (Read error: 110 (Connection timed out))
  1051. # [20:41] * Joins: KevinMarks (n=KevinMar@nat/google/x-dc60388f1a8144d7)
  1052. # [20:42] <Philip`> hsivonen: Hmm, that sounds a little bit crazy if it's using Thread.interrupt, since the interrupt mechanism isn't really meant to work that way
  1053. # [20:43] * Quits: jgraham (n=james@81-86-217-60.dsl.pipex.com) ("I get eaten by the worms")
  1054. # [20:43] <Philip`> (Not that I actually have any experience or knowledge in this area, other than attending some lectures and reading the documentation a bit, so I could be misrepresenting situations)
  1055. # [20:44] <Philip`> I can't think of a better way to do it, though
  1056. # [20:47] <Philip`> (at least not without having access to e.g. an object with a volatile boolean youGotInterrupted field which can be polled)
  1057. # [20:47] * Quits: phsiao (n=shawn@nat/ibm/x-7b6a324d41170fb8)
  1058. # [20:48] * Joins: starjive (i=beos@213-66-217-32-no30.tbcn.telia.com)
  1059. # [21:13] <blooberry> hixie: yt?
  1060. # [21:18] * Joins: sverrej (n=sverrej@89.10.27.86)
  1061. # [21:36] * Joins: weinig (n=weinig@17.203.15.172)
  1062. # [21:39] <hsivonen> Philip`: I was thinking about using Thread.stop()
  1063. # [21:39] <hsivonen> Philip`: as far as I can tell, the danger of Thread.stop() is that introducing an unexpected exception may leave objects that are shared between threads in an inconsistent state, because locks were opened and cleanup code didn't run
  1064. # [21:40] <Philip`> hsivonen: Oh, Thread.stop is evil and should never be used, from what I've heard
  1065. # [21:40] <hsivonen> Philip`: so if I make sure that I never call Thread.stop() when execution is in a shared object or call it only on lockless read-only shared objects, what's the harm?
  1066. # [21:40] <Philip`> It can do things like stop the thread while it's in the middle of a GC operation, and not release the locks, and deadlock the whole VM
  1067. # [21:41] <hsivonen> ah. I didn't know it can break GC
  1068. # [21:41] * mpt wonders if having two <footer>s is appropriate
  1069. # [21:41] <hsivonen> isn't it kinda silly that the VM lets you break GC? shouldn't the VM be able to defer Thread.stop() until GC isn't active?
  1070. # [21:42] <Philip`> Thread.interrupt is safe because it works like proper Java exceptions, but Thread.stop just makes everything abort uncleanly
  1071. # [21:44] <hsivonen> Philip`: documentation says the locks are released as ThreadDeath propagates through the stack.
  1072. # [21:44] <Philip`> Oh, indeed, I'm mixing things up with Thread.suspend
  1073. # [21:44] <Philip`> (looking at http://java.sun.com/j2se/1.5.0/docs/guide/misc/threadPrimitiveDeprecation.html )
  1074. # [21:45] <Philip`> and suspend seems to be the one that causes nasty interactions with GC and stuff
  1075. # [21:45] <Philip`> (unless I'm still remembering things wrong and/or making things up)
  1076. # [21:46] <hsivonen> Philip`: that's the document I'm reading. as far as I can tell, the approach I outlined addresses the issues recounted in that document
  1077. # [21:49] <hsivonen> ouch. I just realized that log4j is synchronized IO that is sprinkled around
  1078. # [21:49] <Philip`> hsivonen: It sounds like you'd have to make sure Thread.stop isn't called at any time while you're executing methods in objects that are shared between threads (else they might get stuck in an inconsistent state)
  1079. # [21:50] <Philip`> and I'd guess there's quite a lot of shared objects being accessed via libraries
  1080. # [21:50] <hsivonen> Philip`: unless the shared object is safe for concurrent reads by having immutable internal state, right?
  1081. # [21:51] <Philip`> If the objects aren't modified, it sounds like that'd probably be alright
  1082. # [21:51] <hsivonen> what library entry points do I have except servlet output, log4j, and http input?
  1083. # [21:52] <hsivonen> assuming that I replace JDK 1.1 Hashtable and friends in oNVDL with copies grabbed from Harmony and remove the locks
  1084. # [21:52] <Philip`> I imagine all the Java classes
  1085. # [21:52] <Philip`> Presumably there's all sorts of things like String.intern that share stuff between threads
  1086. # [21:52] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net) (Read error: 104 (Connection reset by peer))
  1087. # [21:52] <hsivonen> ah right
  1088. # [21:52] <hsivonen> there goes my cunning plan
  1089. # [21:53] * Joins: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  1090. # [21:53] * hsivonen forgot about String.intern()
  1091. # [21:53] <Philip`> I still have no practical knowledge or experience of anything to do with this, but it just looks like a kind of dodgy thing to do, particularly since it's been deprecated since 1995 :-)
  1092. # [21:55] <hsivonen> well, the documentation suggested that in special apps it could make sense when being careful, but String.intern() makes being careful too hard
  1093. # [21:56] <hsivonen> for example, Java 1.2 Collections are supposed to be safe for lockless concurrent reads, so they wouldn't have been a problem
  1094. # [21:56] <Philip`> In almost any practical code it seems impossible to be careful enough, since you can't possibly check what all the libraries are doing and what assumptions they're making
  1095. # [21:57] <Philip`> and it's not something you can test for, since the errors will only happen on one in 10^n occasions and will be impossible to debug
  1096. # [21:59] <hsivonen> Philip`: it's not impossible to consider all the code you don't see as dangerous edges, search all the code you do see for synchronized and assumed that promises about thread safety without using synchonized are clue-based and true
  1097. # [21:59] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  1098. # [21:59] <hsivonen> but the problem is that String.intern() is a dangerous edge that is too pervasive to protect on every call site
  1099. # [22:00] <hsivonen> the IO edges would have been reasonably protectable
  1100. # [22:00] <Philip`> hsivonen: That would be possible but it sounds insufficiently paranoid, and I always get scared when doing anything non-trivial with concurrency because it'll probably go wrong; but maybe that's just me :-)
  1101. # [22:01] <hsivonen> :-)
  1102. # [22:01] <hsivonen> it seems to me that even with interrupt(), I'd have to manually protect output generation
  1103. # [22:02] <Philip`> (I also have no idea how Thread.stop interacts with Java's consistency guarantees - it seems quite possible that it'd try to stop the thread in the middle of a code block that has been reordered by the optimiser, so the execution won't even correspond to the source code)
  1104. # [22:03] * Joins: Lachy_ (n=Lachlan@ti200710a340-3723.bb.online.no)
  1105. # [22:03] * Quits: Lachy_ (n=Lachlan@ti200710a340-3723.bb.online.no) (Client Quit)
  1106. # [22:05] * Joins: mcarter_ (n=mcarter@ip-12-22-56-126.hqglobal.net)
  1107. # [22:08] * Quits: mcarter (n=mcarter@ip-12-22-56-126.hqglobal.net) (Read error: 110 (Connection timed out))
  1108. # [22:08] <hsivonen> of course, all this could be solved by eliminating Schematron
  1109. # [22:08] <hsivonen> thereby making Validator.nu less generic
  1110. # [22:09] <hsivonen> or if someone wrote a zealously streaming Schematron implementation--possibly rejecting schemas that don't translate to reasonably streamable things
  1111. # [22:11] * Quits: Lachy (n=Lachlan@ti200710a340-2662.bb.online.no) (Read error: 110 (Connection timed out))
  1112. # [22:15] * Joins: qwert666 (n=qwert666@acdg71.neoplus.adsl.tpnet.pl)
  1113. # [22:43] * Quits: roc (n=roc@121-72-181-158.dsl.telstraclear.net)
  1114. # [22:49] <Philip`> "It should show up under http://canvex.lazyilluminati.com/misc/cgi/issues.cgi/folder/widgets-tabindex once Hixie has filed the email." - plus up to 24 hours for Hixie's database to get updated, plus up to 24 hours for my cached copy to expire - it's kind of sad that it takes half a second to transmit email anywhere in the world, but two days for my software to notice :-(
  1115. # [22:50] <Hixie> heh
  1116. # [22:51] * Joins: Lachy (n=Lachlan@ti200710a340-3723.bb.online.no)
  1117. # [22:52] * Joins: jruderman (n=jruderma@guest-226.mountainview.mozilla.com)
  1118. # [22:54] * Quits: ROBOd (n=robod@89.122.216.38) ("http://www.robodesign.ro")
  1119. # [23:00] * Quits: virtuelv (n=virtuelv@225.80-203-100.nextgentel.com) ("Ex-Chat")
  1120. # [23:03] <Hixie> hahaha
  1121. # [23:04] * Joins: othermaciej (n=mjs@17.255.100.27)
  1122. # [23:05] <Hixie> dude, krijnh, i'm so sorry about your experience with the csswg
  1123. # [23:06] <Hixie> man that's fucked up
  1124. # [23:06] <gavin_> ?
  1125. # [23:07] <Hixie> the csswg resolved to log their channel, so he set up his system to start logging it, and they got annoyed that it was being logged
  1126. # [23:07] <Hixie> "we resolve to be public... but not if it means people can see what we wrote"
  1127. # [23:08] <Hixie> way to build a community!
  1128. # [23:09] * Joins: othermaciej_ (n=mjs@17.203.15.181)
  1129. # [23:09] <gavin_> ah, heh
  1130. # [23:10] * Quits: othermaciej (n=mjs@17.255.100.27) (Nick collision from services.)
  1131. # [23:10] * othermaciej_ is now known as othermaciej
  1132. # [23:10] <othermaciej> do they want the ability to pre-censor the logs or something?
  1133. # [23:11] <Hixie> # [13:57] <krijnh> (In case anybody missed it, anne asked me to log this channel as well, on http://krijnhoetmer.nl/irc-logs/css/ )
  1134. # [23:11] <Hixie> # [13:57] <Bert> Yes, I noticed. I will be careful when I say something. Or I may leave completely, not sure yet.
  1135. # [23:11] <othermaciej> oh, Bert was against the logging in the first place
  1136. # [23:12] <Hixie> 14:01 < glazou> krijnh: I want the WG to agree on this logging
  1137. # [23:12] <Hixie> 14:02 < glazou> krijnh: anne never mentioned logging outside of w3c
  1138. # [23:13] <Philip`> The problem with public logging of IRC is that it allows discussions like this one to come into existence
  1139. # [23:13] <Hixie> 14:12 < glazou> a 3rd party then controls the log, it's a matter of trust, confidence, IPR
  1140. # [23:14] <Philip`> The W3C is a 3rd party in relation to me
  1141. # [23:14] <Philip`> and I don't particularly trust them to never edit the logs
  1142. # [23:15] <Lachy> wow, that's just crazy. The W3C should be logging all channels, even if some of them aren't public
  1143. # [23:15] <takkaria> it's already a public channel, which is what I don't understand
  1144. # [23:15] <Hixie> given that the w3c once censored me, and krijnh has never censored me, i trust krijnh a whole heck of a lot more than the w3c
  1145. # [23:16] <othermaciej> Hixie: what did they censor?
  1146. # [23:17] <Hixie> http://lists.w3.org/Archives/Public/www-archive/2007Nov/0104.html
  1147. # [23:17] <Hixie> i rearchived that post here: http://damowmow.com/playground/archives/reply-to-dean-edridge.html
  1148. # [23:18] <Philip`> The only sure thing you can trust is apathy, so make sure all logs and archives are held by someone who's never going to care enough to alter them
  1149. # [23:19] * othermaciej is now known as om_meet
  1150. # [23:19] <Hixie> annevk, annevk, annevk. you should have posted your e-mail to the public list!
  1151. # [23:20] * Joins: roc (n=roc@202.0.36.64)
  1152. # [23:38] * jgraham_ is somewhat bemused that "public" seems so hard to understand
  1153. # [23:40] * Joins: jgraham (n=james@81-86-217-60.dsl.pipex.com)
  1154. # [23:41] <Dashiva> jgraham: It's easy to understand, it's just easy to redefine too :P
  1155. # [23:42] <Philip`> jgraham: Beaches are public areas, but I imagine most people wouldn't like someone continually taking photos of them while they're there and sticking them all up on a wall
  1156. # [23:43] <Dashiva> Philip`: Well, the beach goers didn't resolve to have their beach going be an open activity, the state did
  1157. # [23:45] <Philip`> Dashiva: The beachgoers resolved in the morning that they'd like to go to the beach today, knowing that that would entail being in a public space
  1158. # [23:47] <Dashiva> A false choice, as all beaches were made open against their will
  1159. # [23:48] <roc> originally all beaches were private property that was then confiscated by the state? interesting
  1160. # [23:50] * om_meet is now known as othermaciej
  1161. # [23:51] <Philip`> Dashiva: There are plenty of non-public places the people could have gone, but they chose to go to a public one instead under reasonable expectations of publicness (e.g. they expect strangers might come up and say hello, but don't expect everything they say to be recorded and published for eternity)
  1162. # [23:51] <Philip`> So, uh, I think beaches are public IRC channels in this analogy, rather than being all IRC channels
  1163. # Session Close: Wed Apr 23 00:00:00 2008

The end :)