/irc-logs / freenode / #whatwg / 2007-03-25 / end

Options:

  1. # Session Start: Sun Mar 25 00:00:00 2007
  2. # Session Ident: #whatwg
  3. # [00:00] <tantek> othermaciej, it's a natural tendency to create as many complex layers as possible so that each member company that has a particular expertise can build and sell a horribly complex solution that is too hard/obtuse for individual developers to build on their own.
  4. # [00:01] <tantek> in otherwords, inverses of both the explicit (and implicit) principles behind URL, HTTP, HTML.
  5. # [00:02] <Dashiva> OT: Oh man, 6-player lggwg. This is going to take weeks.
  6. # [00:07] * Joins: mpt (n=mpt@121-72-132-150.dsl.telstraclear.net)
  7. # [00:09] * Joins: hasather (n=hasather@81-235-209-174-no62.tbcn.telia.com)
  8. # [00:13] <othermaciej> Dashiva: the behavior would be in SMIL of course
  9. # [00:13] <Dashiva> Oh, right. Silly me.
  10. # [00:14] <othermaciej> so the full stack would be to take your RDF and apply an XSLT transform to get XSL-FO + SMIL
  11. # [00:14] <Dashiva> Anyone know if there would be licencing issues in including, say, a SHA-1 function in the spec?
  12. # [00:16] <othermaciej> as in patent licensing?
  13. # [00:16] <othermaciej> I don't believe SHA-1 is patented
  14. # [00:16] <Dashiva> Any kind that would mean trouble for inclusion.
  15. # [00:17] <Dashiva> When doing web applications, having a built-in reliable hash function could be useful for some basic security without having to turn to https
  16. # [00:21] <Philip`> Would performance be the only benefit of it being built in, compared to using an implementation in JavaScript?
  17. # [00:23] * Quits: bzed (n=bzed@dslb-084-059-111-244.pools.arcor-ip.net) ("Leaving")
  18. # [00:23] <Dashiva> I was actually thinking convenience as the main benefit. And less to download for users, for that matter
  19. # [00:34] * Quits: hendry (n=hendry@91.84.53.136) ("leaving")
  20. # [00:38] <Hixie> SHA-1 isn't reliable is it? I thought it had been cracked.
  21. # [00:39] <Dashiva> It's cracked in the academic sense
  22. # [00:41] <othermaciej> is there a one-way hash that is well tested and doesn't have even theoretical flaws?
  23. # [00:42] <Philip`> It's weak enough for people to not recommend its use in the future - http://csrc.nist.gov/hash_standards_comments.pdf says NIST planned to phase out SHA-1 (and similar strength algorithms) by 2010
  24. # [00:44] * Joins: bzed (n=bzed@dslb-084-059-111-244.pools.arcor-ip.net)
  25. # [00:50] <Philip`> http://www.csrc.nist.gov/pki/HashWorkshop/ is still looking for a better hash function (to be standardised around 2012), but I assume they're still not expecting one with no theoretical flaws - the only known flawless algorithms are only usable in theory
  26. # [00:53] <othermaciej> why only usable in theory?
  27. # [00:53] <othermaciej> are they too slow to compute?
  28. # [00:56] <Philip`> They're ideas like having a man in a box with a lookup table of (message, hash) pairs, and some dice so he can generate hashes for any message you give him that he hasn't seen before
  29. # [00:56] <hasather> hehe
  30. # [00:57] <Philip`> (as an implementation of http://en.wikipedia.org/wiki/Random_oracle)
  31. # [00:59] <othermaciej> Philip`: so basically it depends on having a huge, constantly updated shared secret
  32. # [00:59] <Hixie> that's just a centralised dictionary service
  33. # [01:00] <othermaciej> Philip`: I was thinking of just strong in the collision resistance sense
  34. # [01:00] <othermaciej> Philip`: not the random oracle sense
  35. # [01:01] <othermaciej> SHA256 is believed to have good collision resistance still I think
  36. # [01:01] <nickshanks> hixie: do you know what percentage of IMG elements have a longdesc attribute ?
  37. # [01:02] <nickshanks> random oracle == http://en.wikipedia.org/wiki/Special:Random :-)
  38. # [01:03] <nickshanks> "The Outerbridge Crossing is a cantilever bridge over the Arthur Kill connecting Perth Amboy, New Jersey with Staten Island, New York." see, i learnt something new ;-)
  39. # [01:11] <Philip`> othermaciej: It seems the best existing hash functions are still only 'good enough' in terms of collision resistance, and nobody has come up with a theoretically perfect one that is still practical - SHA-256 is good enough for now, but it'll probably be warned against in ten years, and they'll have to come up with new ones to last a few more decades after that
  40. # [01:13] <Philip`> ...But I suppose I could be misreading "doesn't have even theoretical flaws" as being "doesn't have even the theoretical possibility of having any theoretical flaws", rather than "doesn't have any known theoretical flaws" (which current hash functions would satisfy)
  41. # [01:13] <othermaciej> yeah, I meant the latter
  42. # [01:14] <othermaciej> I am not sure it's possible to prove collision resistence in the sense that there is no way to beat the brute force attack
  43. # [01:14] <Dashiva> How about saying "Not flawed enough to be practically broken for the next five years"
  44. # [01:15] <othermaciej> that's impossible to predict
  45. # [01:16] <Dashiva> Well, assuming no quantum computers or other sudden major changes in computing power
  46. # [01:26] <Philip`> You could prove collision resistance in the sense that there's no better attack than brute force, and you can prove that for random oracles, and it seems to be a useful property (despite the unavoidable property that some inputs must collide); but no practical algorithm is (or ever will be?) that good, so it's not a very useful point :-)
  47. # [01:37] * Parts: hasather (n=hasather@81-235-209-174-no62.tbcn.telia.com)
  48. # [03:05] * Quits: Philip` (n=excors@zaynar.demon.co.uk)
  49. # [03:20] * Quits: tantek (n=tantek@c-67-174-230-58.hsd1.ca.comcast.net)
  50. # [03:35] * Quits: aroben (n=adamrobe@adsl-70-132-25-127.dsl.snfc21.sbcglobal.net)
  51. # [03:35] <Hixie> nickshanks: not many, and most that do have it have the blank value, iirc. but ask me again on friday if you want me to get you good numbers.
  52. # [03:36] <Lachy> good morning
  53. # [03:36] <Hixie> ih
  54. # [03:36] <Hixie> hi even
  55. # [03:36] <nickshanks> hixie: i will. what is happening between now and friday, another survey?
  56. # [03:38] <Lachy> Hixie, I found some broken things on your web site. These images are served as text/plain;charset=UTF-8, so not even content sniffing works
  57. # [03:38] <Lachy> http://ln.hixie.ch/media/diagrams/evolution/
  58. # [03:45] <Hixie> nickshanks: no, csswg meeting, i won't be in my office until then
  59. # [03:45] <Hixie> Lachy: oops
  60. # [03:46] <Hixie> fixed.
  61. # [03:46] <Lachy> cool
  62. # [03:46] <nickshanks> oh, shame. I'd love to see an update of code.google.com/webstats
  63. # [03:46] <Hixie> yeah
  64. # [03:46] <Hixie> so would i
  65. # [03:46] <Hixie> but i'm too busy with whatwg and htmlwg to do something like that now
  66. # [03:47] <nickshanks> can you not just re-run the scripts from the first time, on some machine you're not using?
  67. # [03:47] <nickshanks> i'm sure there's a few eight-core intel Core 3's lying around GoogleHQ :)
  68. # [03:49] <Lachy> does anyone know if, in gmail, there's a way to delete thousands of e-mails all at once, instead of 20 at a time?
  69. # [03:50] <othermaciej> hello Hixie
  70. # [03:50] <Hixie> nickshanks: um. try to estimate how much time it would take to run a survey on a few billion documents.
  71. # [03:50] <Hixie> othermaciej: hi
  72. # [03:51] <othermaciej> Hixie: hyatt is definitely coming to the CSSWG meeting, I could come to part of one day if you think it would be useful
  73. # [03:51] * Joins: aroben (n=adamrobe@adsl-70-132-25-127.dsl.snfc21.sbcglobal.net)
  74. # [03:51] <Hixie> it would be cool if you could come to hte tuesday dinner
  75. # [03:51] <Hixie> it's at zibibbo's, google is paying
  76. # [03:51] <nickshanks> hixie: yeah, i realise. maybe you could set up a CodeSurvey@Home project and farm it out to millions of internet zombies?
  77. # [03:51] <othermaciej> Hixie: I like free food
  78. # [03:52] <Hixie> nickshanks: be my guest :-)
  79. # [03:55] * moeffju[Away] is now known as moeffju
  80. # [03:57] <Hixie> i really don't understand what problem is being solved by the version="" crap
  81. # [03:58] <Lachy> Hixie, there isn't any problem being solved, it's just a way for people to indicate they're using the latest and greatest standard. It's absolute nonsense
  82. # [03:59] <webben> or a testament to people's belief that future specs will break previous specs
  83. # [03:59] <Lachy> yeah, that too
  84. # [04:00] <Lachy> I suppose, XHTML 1 technically did that to HTML4
  85. # [04:00] <webben> indeed
  86. # [04:00] <Lachy> and XHTML2 would have done that to XHTML1
  87. # [04:00] <othermaciej> might be worth comparing to other document and programming languages, and whether they have a self-identification token
  88. # [04:00] <othermaciej> and if so whether it has been valuable or not
  89. # [04:00] <webben> programming languages aren't relevant i don't think
  90. # [04:00] <webben> document languages are
  91. # [04:00] <Lachy> DocBook does, but it doesn't seem valuable
  92. # [04:01] <Hixie> let's see...
  93. # [04:01] <webben> Word seems to be able to tell what version is being used.
  94. # [04:01] <Hixie> C++: no. Java: no. C: no. Pascal: no. Perl: no. Python: no. CSS: no.
  95. # [04:01] <Hixie> Word has versioning specifically to achieve something we're trying to avoid, vendor lock-in
  96. # [04:01] <othermaciej> C and C++ have version-based #defines, so you can check for a version from code
  97. # [04:01] <Lachy> JavaScript 1.2 and 1.5 are slightly incompatible
  98. # [04:02] <othermaciej> but there is no need or ability for code to declare its version
  99. # [04:02] <webben> i can see why programming langs would have no versioning and document langs would
  100. # [04:02] <webben> especially long-lasting, widely-distributed document langs
  101. # [04:02] <Lachy> FF checks for <script language=javascript1.2>
  102. # [04:02] <Lachy> or something like that
  103. # [04:02] <Hixie> othermaciej: really? language version, as opposed to UA version?
  104. # [04:03] <othermaciej> Hixie: calling a compiler a UA is kind of funny, but yes
  105. # [04:03] <othermaciej> you can tell if you are compiling as C89 or C99
  106. # [04:03] <Hixie> Lachy: yeah and it's not in the script itself
  107. # [04:03] <Hixie> othermaciej: interesting. didn't know that. never seen anyone use it. (and yeah, a compiler is a user agent. :-) )
  108. # [04:03] * Joins: welly_ (n=welly@62-31-60-148.cable.ubr12.azte.blueyonder.co.uk)
  109. # [04:03] <Lachy> no, but it's in the HTML that uses the script, and there are many authors that don't know the differnece
  110. # [04:04] <webben> ODF has versioning
  111. # [04:04] <othermaciej> Hixie: if you want to analogize to the web architecture, it's more like a server-size processing step
  112. # [04:04] <webben> 2.1.2 of the ODF spec
  113. # [04:04] <Hixie> othermaciej: i guess
  114. # [04:04] <webben> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
  115. # [04:04] <Hixie> webben: i wouldn't use ODF as an example of a good spec either :-)
  116. # [04:05] <webben> rtf has versioning
  117. # [04:05] * Joins: csarven- (n=nevrasc@modemcable081.152-201-24.mc.videotron.ca)
  118. # [04:06] <nickshanks> hixie: do you at least have time to remove 'best viewed in FireFox 1.5' from code.google.com/webstats ?
  119. # [04:07] <Hixie> nickshanks: again, remind me friday
  120. # [04:07] <Hixie> (but doing that is a pain)
  121. # [04:07] <webben> i wish more of these specs were provided in a decent format like HTML
  122. # [04:08] <Lachy> does PDF have versions?
  123. # [04:08] <Lachy> I think it does, but not sure
  124. # [04:08] <nickshanks> SVG and XML have versions
  125. # [04:08] <nickshanks> as does apple PropertyList format
  126. # [04:08] <Lachy> XML shouldn't have versioning
  127. # [04:08] <Hixie> again, svg, not a language i'd use as an example of great design
  128. # [04:08] <Hixie> xml's versioning has already causd problems
  129. # [04:09] <webben> Lachy, I'm just downloading the giant PDF spec of PDF to check.
  130. # [04:09] <webben> (talk about putting the disadvantages of your format foot-forward)
  131. # [04:09] <Lachy> XML 1.1 is basically unusable, and future versions of XML should drop the version declaration
  132. # [04:09] <othermaciej> it's best to have a model for adding features in a backwards and forwards compatible way that does not require versioning
  133. # [04:10] <nickshanks> webben: that just shows up the UA's "download it all before you display the first page" lame PDF handling
  134. # [04:10] <Hixie> ok. looping. let's see.
  135. # [04:10] <webben> nickshanks, wouldn't be necessary if their plugin wasn't so crash-ready
  136. # [04:10] <webben> but i take your point
  137. # [04:11] <webben> othermaciej, Doing so is not necessarily incompatible with having versioning as a safeguard
  138. # [04:11] <webben> e.g. has any programming language managed to evolve in a 100% backwards compatible way?
  139. # [04:11] <nickshanks> if(random() < 5000) longjmp(NULL, 0);
  140. # [04:12] <webben> (VB until .NET maybe?)
  141. # [04:12] <Hixie> webben: pascal, through turbo pascal and then object pascal, did a pretty good job, 16bit to 32bit pointer migration notwithstanding
  142. # [04:13] <webben> Hixie, Ah. Neat. :)
  143. # [04:14] <Hixie> if current position=10, begin=5, end=9, loopbegin=6, loopend=8, and you call play(), what should happen?
  144. # [04:14] <Hixie> should it continue playing from t=10?
  145. # [04:14] <Hixie> seems like yes
  146. # [04:14] <Hixie> but then how do you start over at the start of the loop sequence?
  147. # [04:15] <Hixie> should we have a .restart() method or something?
  148. # [04:15] <Hixie> (called .loop() maybe?)
  149. # [04:15] <nickshanks> well in order to get to 10, it would have had to have received a seek()
  150. # [04:15] <othermaciej> Hixie: your position shouldn't be able to be outside the (begin, end) range
  151. # [04:15] <nickshanks> so it seems only reasonable that it would need another seek() to get abck
  152. # [04:16] <othermaciej> Hixie: think of it like clipping
  153. # [04:16] <Hixie> othermaciej: so if you dynamically set .end, and that puts .position outside the range, the playback has to stop and seek() to .end?
  154. # [04:16] * Quits: welly_ (n=welly@62-31-60-148.cable.ubr12.azte.blueyonder.co.uk)
  155. # [04:16] <othermaciej> Hixie: I think that's the only sensible thing
  156. # [04:17] * Joins: welly_ (n=welly@62-31-60-148.cable.ubr12.azte.blueyonder.co.uk)
  157. # [04:17] <Hixie> interesting
  158. # [04:17] <Hixie> still leaves the question of how you restart playback
  159. # [04:17] <Hixie> nickshanks: so you'd have media.seek(media.start); media.play();, with no shortcut for that?
  160. # [04:17] <webben> TEI has DTDs and so has versioning.
  161. # [04:18] <webben> Is there a document format without any versioning other than text/plain?
  162. # [04:18] <nickshanks> i don't think it really needs a shortcut, it's uite simple
  163. # [04:18] <nickshanks> *quite
  164. # [04:18] <Hixie> k
  165. # [04:18] <Hixie> webben: HTML5? :-)
  166. # [04:18] <othermaciej> Hixie: you would want to reset the current loop as well to totally restart playback
  167. # [04:18] <Hixie> yes
  168. # [04:19] * Joins: zcorpan (n=zcorpan@84-216-40-60.sprayadsl.telenor.se)
  169. # [04:19] <Hixie> media.currentLoop = 0; media.seek(media.start); media.play();
  170. # [04:19] <othermaciej> Hixie: a co-worker of mine read the #whatwg IRC logs and pointed out a use case where you would want a controller to join an existing video element in arbitrary state
  171. # [04:19] * moeffju is now known as moeffju[ZzZz]
  172. # [04:19] <Hixie> oh?
  173. # [04:19] <othermaciej> (wildly changing topic)
  174. # [04:20] <webben> yeah that download finished. PDF has versioning too.
  175. # [04:20] <othermaciej> consider something like Keynote, where you may have a presentation slide with possibly several video objects embedded, and a floating "video info" window
  176. # [04:20] <Hixie> oh and you want to attach it to see why it failed to play?
  177. # [04:20] <othermaciej> web presentation progragms are certainly an obvious use case to think about, even though they go beyond just simple playback
  178. # [04:20] <Hixie> hm
  179. # [04:20] <Hixie> yeah
  180. # [04:20] <Hixie> you'd want more than just an error state then though
  181. # [04:21] <Hixie> you'd need error data too
  182. # [04:21] <Hixie> .lastError kind of thing
  183. # [04:21] <othermaciej> probably, yes, if the error event carries useful info
  184. # [04:21] <Hixie> i'll bear that in mind
  185. # [04:22] * Quits: csarven (n=nevrasc@modemcable081.152-201-24.mc.videotron.ca) (Read error: 110 (Connection timed out))
  186. # [04:23] <nickshanks> it might be better to have a plugin that handles Content-URI: com.apple.keynote.presentation
  187. # [04:23] <nickshanks> rather than embedding it into HTML
  188. # [04:23] <nickshanks> oops, I mean UTI :-)
  189. # [04:24] <Hixie> he just meant if you implemented Keynote or something like that in HTML
  190. # [04:24] <Hixie> like s3
  191. # [04:24] <Hixie> or s5
  192. # [04:24] <nickshanks> oh right
  193. # [04:24] <Hixie> or whatever it's called
  194. # [04:24] <Hixie> othermaciej: so this makes updating these attributes difficult
  195. # [04:24] <nickshanks> meyerweb.com/eric/tools/s5/s5-intro.html
  196. # [04:25] <Hixie> othermaciej: you can't update all four of them at once if you're moving to a different part of the clip without checking which order to set them in
  197. # [04:25] <Hixie> othermaciej: unless we provide an interface for doing that
  198. # [04:25] <Hixie> like .setLoopParameters()
  199. # [04:25] <othermaciej> Hixie: ah, because end can't be before begin?
  200. # [04:25] <Hixie> yeah
  201. # [04:25] <othermaciej> you could allow that but treat it as an empty range
  202. # [04:26] <Hixie> hm, could do
  203. # [04:27] <nickshanks> what if i did seek(50); setEnd(30); setStart(10);
  204. # [04:27] <Hixie> you'd end up at position=30
  205. # [04:27] <Hixie> assuming they were unset before
  206. # [04:28] <othermaciej> why is there even a seek method instead of position being read/write?
  207. # [04:28] <nickshanks> and play() would not do anything ?
  208. # [04:28] <othermaciej> hmm, seek appears to be relative if I am intepreting "offset" right
  209. # [04:28] <Hixie> seek isn't relaive
  210. # [04:29] <Hixie> it exists because originally i was going to have position only update once the seek had completed
  211. # [04:29] <Hixie> but since i changed that i guess now we can just remove seek()
  212. # [04:29] <Hixie> still, that doesn't affect this discussion
  213. # [04:29] <othermaciej> yeah, was just an aside
  214. # [04:29] <nickshanks> om has a point, you could use setPosition(int) for absolute, and advance(±int) for relative
  215. # [04:30] <Hixie> let's concentrate on these loop variables first
  216. # [04:30] <Hixie> so if currentLoop = 0, start <= position < loopEnd
  217. # [04:30] <Hixie> if 0 < currentLoop < loopCount, loopStart <= position < loopEnd
  218. # [04:31] <Hixie> if currentLoop == loopCount, loopStart <= position <= end
  219. # [04:31] <Hixie> right?
  220. # [04:31] <othermaciej> sounds about right
  221. # [04:31] <Hixie> and this needs to apply when seeking and when playback is occuring
  222. # [04:32] <Hixie> do we clamp on seek, or raise an exception?
  223. # [04:33] <Hixie> oh that was the other reason i had a method instead of a setter
  224. # [04:33] <Hixie> i didn't like the idea of invoking an event handler while in a setter
  225. # [04:33] <Hixie> i don't like heavy duty setters generally
  226. # [04:40] * Quits: webben (n=benjamin@91.84.131.217) ("Leaving")
  227. # [04:46] <othermaciej> DOM is full of them though
  228. # [04:48] <Hixie> yeah
  229. # [04:48] <Hixie> i try to learn from past mistakes :-P
  230. # [04:49] <othermaciej> well, getter / setter vs function is just a matter of syntax
  231. # [04:50] <othermaciej> I tend to find 0-arg getter functions and 1-arg setter functions to be unidiomatic in JS
  232. # [04:50] <Hixie> yeah
  233. # [04:52] <othermaciej> nearly the same to implement though, at least in our engine
  234. # [04:56] <ericcarlson> rewinding back to the discussion about what to do with play() when currentTime == duration:
  235. # [04:56] <ericcarlson> one option is to seek(startTime), emitting a timechanged event, before setting the rate
  236. # [04:58] <ericcarlson> FWIW this is what QuickTime has done since the dark ages (1991)
  237. # [04:59] <nickshanks> i would concur
  238. # [04:59] <Hixie> could you elaborate?
  239. # [04:59] <Hixie> i don't understand the proposal as described
  240. # [05:00] <nickshanks> when you're at the ned and you click play, it should go to the start and begin playing again
  241. # [05:00] <nickshanks> *ned -> end
  242. # [05:00] <Hixie> should it reset the loop count?
  243. # [05:01] <ericcarlson> good question
  244. # [05:01] <Lachy> yes, that's the behaviour a user would expect.
  245. # [05:01] <nickshanks> yeah, because in all likelyhood the loop count is at loopMax by this point anyway
  246. # [05:01] <othermaciej> if it's hit the max loop count, that would probably make sense
  247. # [05:02] <Hixie> i guess we could have 'play' act differently when ended==true than when ended==false, which is basically what you propose, right?
  248. # [05:02] <Hixie> that would work
  249. # [05:02] <ericcarlson> Yes
  250. # [05:02] <Hixie> ok
  251. # [05:02] <othermaciej> there's another relevant question here, which is whether position (or currentTime, which I personally like better) goes from startTime to endTime, or from 0 to (endTime - startTime)
  252. # [05:02] <nickshanks> play shouldn't act differently, no
  253. # [05:03] <nickshanks> oh, i see what you mean. i wa=s thinking you meant "lets play the movie differently the second time around" :-)
  254. # [05:03] <ericcarlson> startTime -> endTime because setting startTime doesn't change the media time line,
  255. # [05:04] <ericcarlson> only the point at which playback starts.
  256. # [05:04] <nickshanks> anyway, 4am here, going to sleep
  257. # [05:04] <nickshanks> night all
  258. # [05:05] <othermaciej> g'night nickshanks
  259. # [05:05] <Hixie> do end and loopend default to +INF or .duration?
  260. # [05:06] <ericcarlson> +INF so it is possible to detect that it has never been set.
  261. # [05:06] <Hixie> k
  262. # [05:24] * othermaciej is now known as om_out
  263. # [05:49] * Joins: marcosc (n=chatzill@131.181.148.226)
  264. # [05:52] * Quits: bzed (n=bzed@dslb-084-059-111-244.pools.arcor-ip.net) ("Leaving")
  265. # [06:11] * Quits: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net)
  266. # [06:16] * Joins: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net)
  267. # [06:24] * Quits: csarven- (n=nevrasc@modemcable081.152-201-24.mc.videotron.ca)
  268. # [06:45] * Parts: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net)
  269. # [06:55] * Quits: zcorpan (n=zcorpan@84-216-40-60.sprayadsl.telenor.se) (Read error: 110 (Connection timed out))
  270. # [06:56] * Quits: aroben (n=adamrobe@adsl-70-132-25-127.dsl.snfc21.sbcglobal.net) (Read error: 104 (Connection reset by peer))
  271. # [06:57] * Joins: aroben (n=adamrobe@adsl-70-132-25-127.dsl.snfc21.sbcglobal.net)
  272. # [07:20] * Joins: h3h (n=w3rd@cpe-76-171-163-147.socal.res.rr.com)
  273. # [08:07] * Joins: aroben_ (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  274. # [08:08] * Quits: aroben_ (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net) (Remote closed the connection)
  275. # [08:08] * Quits: marcosc (n=chatzill@131.181.148.226) (Read error: 110 (Connection timed out))
  276. # [08:08] * Joins: aroben_ (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  277. # [08:16] * Quits: aroben_ (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  278. # [08:16] * Quits: aroben (n=adamrobe@adsl-70-132-25-127.dsl.snfc21.sbcglobal.net) (Operation timed out)
  279. # [08:28] * Joins: aroben (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  280. # [08:28] * Quits: aroben (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net) (Client Quit)
  281. # [08:28] * Joins: aroben (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  282. # [08:56] * Quits: h3h (n=w3rd@cpe-76-171-163-147.socal.res.rr.com)
  283. # [09:42] * Joins: met_ (n=Hassman@r5bx220.net.upc.cz)
  284. # [10:13] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  285. # [10:17] * Joins: marcosc (n=chatzill@131.181.148.226)
  286. # [11:19] * Joins: ROBOd (n=robod@86.34.246.154)
  287. # [11:39] * Joins: hasather (n=hasather@81-235-209-174-no62.tbcn.telia.com)
  288. # [12:09] * Joins: ravenn (n=ravenn@203-214-133-148.perm.iinet.net.au)
  289. # [12:23] * Joins: webben (n=benh@91.84.131.217)
  290. # [12:24] * Parts: hasather (n=hasather@81-235-209-174-no62.tbcn.telia.com)
  291. # [12:30] * Joins: hasather (n=hasather@81-235-209-174-no62.tbcn.telia.com)
  292. # [12:40] * Joins: hendry (n=hendry@91.84.53.136)
  293. # [13:05] * Quits: aroben (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  294. # [13:35] * Quits: met_ (n=Hassman@r5bx220.net.upc.cz) ("Chemists never die, they just stop reacting.")
  295. # [13:42] * Quits: marcosc (n=chatzill@131.181.148.226) (Read error: 110 (Connection timed out))
  296. # [13:43] * Quits: ravenn (n=ravenn@203-214-133-148.perm.iinet.net.au)
  297. # [14:03] * Quits: hendry (n=hendry@91.84.53.136) (orwell.freenode.net irc.freenode.net)
  298. # [14:03] * Quits: welly_ (n=welly@62-31-60-148.cable.ubr12.azte.blueyonder.co.uk) (orwell.freenode.net irc.freenode.net)
  299. # [14:03] * Quits: gsnedders (n=gsnedder@host86-139-123-225.range86-139.btcentralplus.com) (orwell.freenode.net irc.freenode.net)
  300. # [14:03] * Quits: laug (n=laug@poy.chewa.net) (orwell.freenode.net irc.freenode.net)
  301. # [14:03] * Quits: hsivonen (n=hsivonen@kekkonen.cs.hut.fi) (orwell.freenode.net irc.freenode.net)
  302. # [14:03] * Joins: hendry (n=hendry@91.84.53.136)
  303. # [14:03] * Joins: welly_ (n=welly@62-31-60-148.cable.ubr12.azte.blueyonder.co.uk)
  304. # [14:03] * Joins: gsnedders (n=gsnedder@host86-139-123-225.range86-139.btcentralplus.com)
  305. # [14:03] * Joins: laug (n=laug@poy.chewa.net)
  306. # [14:03] * Joins: hsivonen (n=hsivonen@kekkonen.cs.hut.fi)
  307. # [14:15] <hendry> Lachy: i mentioned the two irc channels knowing of course we have two mailing lists. :) i wonder if we'll all settle on one.
  308. # [14:19] <Lachy> I'm sure there are some on the list who don't realise we have 2 lists, we seem to have a lot of newbies
  309. # [15:09] * Joins: Philip` (n=excors@zaynar.demon.co.uk)
  310. # [15:29] * Joins: bzed (n=bzed@dslb-084-059-103-117.pools.arcor-ip.net)
  311. # [15:33] * Quits: Philip` (n=excors@zaynar.demon.co.uk) (Read error: 110 (Connection timed out))
  312. # [16:25] * Joins: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net)
  313. # [16:26] * Quits: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net) (Remote closed the connection)
  314. # [16:27] * Joins: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net)
  315. # [16:33] * Joins: met_ (n=Hassman@r5bx220.net.upc.cz)
  316. # [16:45] * moeffju[ZzZz] is now known as moeffju
  317. # [16:46] <nickshanks> hendry, Lachy: what is the other list and other channel?
  318. # [16:50] <Lachy> nickshanks, public-html and #html-wg on the W3C IRC server
  319. # [16:51] * Quits: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net)
  320. # [16:52] * Joins: Philip` (n=excors@zaynar.demon.co.uk)
  321. # [16:53] * Joins: annevk (n=annevk@5352CE6F.cable.casema.nl)
  322. # [16:53] <nickshanks> there's more than one IRC server? nooooo freenode rules all!
  323. # [16:53] <Lachy> nickshanks, haven't you joined the HTMLWG?
  324. # [16:54] <nickshanks> irc://irc.w3.org/#html-wg
  325. # [16:54] <Lachy> that's the one
  326. # [16:54] * Joins: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net)
  327. # [16:54] <nickshanks> yes,m i did
  328. # [16:54] <nickshanks> (and i was just typing the link so i could click it
  329. # [16:54] <nickshanks> hmm, doesn't want to connect
  330. # [16:55] <nickshanks> is the port different?
  331. # [16:55] <annevk> yes
  332. # [16:55] <annevk> 6665
  333. # [16:55] <annevk> iirc
  334. # [16:55] <Lachy> that's right
  335. # [16:55] <annevk> or just use 80
  336. # [16:55] <annevk> that works as well
  337. # [16:56] <Lachy> is 6667 for W3C members only?
  338. # [16:56] <annevk> for the Team
  339. # [17:03] <met_> http://dbaron.org/log/2007-03#e20070325a
  340. # [17:03] <annevk> heh, <acronym> bugs are marked as spam already
  341. # [17:03] <annevk> s/bugs/mails/
  342. # [17:04] <annevk> nickshanks, why bother implementing longdesc?
  343. # [17:04] <annevk> nickshanks, it's dropped from HTML5...
  344. # [17:05] * weinig|away is now known as weinig
  345. # [17:05] <webben> what's the barrier to implementing longdesc?
  346. # [17:05] <nickshanks> well, first i wanted to add img[longdesc]:after { content: "Description: " attr(longdesc); } to my default CSS
  347. # [17:05] <nickshanks> then i discovered that :before and :aftrer don't work for replaced elements
  348. # [17:05] <nickshanks> so i went to look why
  349. # [17:06] <webben> or is the idea that <a> is a better solution?
  350. # [17:06] <annevk> attr(longdesc) seems pretty wrong
  351. # [17:06] <webben> and if so, how is <a> linked to the image as a longdesc?
  352. # [17:06] <nickshanks> and spotted a bug that safari wasn't treating longdesc as a url (i.e. it ignored <base href> and other things)
  353. # [17:06] <annevk> (longdesc is a URI iirc)
  354. # [17:07] <nickshanks> so i fixed that, and went on to see if i could add a contextual menu item to open the description in a new tab
  355. # [17:07] <nickshanks> anne: yes it's not a good solution at all, but I use it for blockquote[cite] too
  356. # [17:08] <webben> nickshanks: while you're at it, maybe you could do the same for cite?
  357. # [17:08] <webben> (ins, del, q, blockquote)
  358. # [17:08] <nickshanks> webben: you mean contextual menus?
  359. # [17:08] * annevk thinks every browser should just drop support for longdesc
  360. # [17:08] <nickshanks> well i could, yes
  361. # [17:08] <webben> yeah, it works well as a context menu item
  362. # [17:08] <annevk> including the attribute etc.
  363. # [17:08] <nickshanks> anne: wikipedia uses it on every image
  364. # [17:08] <annevk> DOM attribute*
  365. # [17:09] <annevk> nickshanks, they also provide a link, no?
  366. # [17:09] <nickshanks> yep
  367. # [17:09] <annevk> which people actually use
  368. # [17:09] <annevk> as opposed to the longdesc thingie...
  369. # [17:09] <nickshanks> because longdesc is broken in 99% of UAs
  370. # [17:09] <webben> i wonder if Google indexes the longdesc links from Wikipedia for its image search
  371. # [17:09] <annevk> I don't think adding a contextmenu entry fixes it...
  372. # [17:10] <webben> annevk: Why?
  373. # [17:10] <webben> (well actually more important is exposing the longdesc to accessibility frameworks)
  374. # [17:10] <nickshanks> anne: the entry would only show up for images that had a description, it wouldn't be intrusive, and it would both improve accessibility and not harm backwards compatibility
  375. # [17:11] <nickshanks> webben: anything in the DOM is accessible to UI frameworks, is it not?
  376. # [17:12] <annevk> I don't think having hidden metadata improves the situation much.
  377. # [17:12] <nickshanks> my point is if it's there we might as well make use of it
  378. # [17:12] <webben> nickshanks: not really, no. A lot of the problems with screen readers relate to browsers exposing DOMs very partially to the accessibility frameworks.
  379. # [17:12] <annevk> we could add lots of attributes to elements that trigger contextmenu thingies, but I don't see that necessarily improving accessibility or something
  380. # [17:12] <nickshanks> whether it *ought* to be there or avaialble via another mechanism is a different discussian
  381. # [17:12] <nickshanks> on
  382. # [17:12] <webben> Mozilla is working on better exposure, which should translate into more advancing screen reading.
  383. # [17:13] <webben> (but even that is problematic; e.g. Mozilla dropping speech CSS so that Fire Vox has to reparse the CSS file to extract the relevant properties)
  384. # [17:15] <nickshanks> IIRC WebKit has to re-parse CSS for print and lay the page out again
  385. # [17:15] <nickshanks> even though it supports that nativly :(
  386. # [17:15] <webben> well that at least makes more sense
  387. # [17:16] <annevk> it doesn't
  388. # [17:16] * annevk wonders why Hixie introduced content attributes with uppercase letters
  389. # [17:16] <webben> window-eyes supports longdesc: http://www.gwmicro.com/window-eyes/manual/html/index.html?19_10longdesc.htm
  390. # [17:16] * annevk assumes it's an oversight
  391. # [17:17] <webben> JAWS supports longdesc: http://www.wats.ca/show.php?contentid=48
  392. # [17:17] <nickshanks> JAWS is horrible :)
  393. # [17:18] <webben> nickshanks: Well sure. But IE is horrible and we run circles round that.
  394. # [17:18] <annevk> IE is actually used
  395. # [17:18] <webben> JAWS is (probably) the most popular screen reader
  396. # [17:18] <nickshanks> Actually I think VoiceOver is shitty too, but then it's only a 1.0 product
  397. # [17:19] <nickshanks> s/popular/common/
  398. # [17:19] <webben> replacement accepted :)
  399. # [17:20] <webben> but i think we probably shouldn't ditch accessibility features supported by the most popular screen readers
  400. # [17:20] * annevk isn't sure DOM2HTML is internally consistent
  401. # [17:20] <webben> or the most common ones either
  402. # [17:20] <annevk> .hreflang for instance
  403. # [17:21] <annevk> or .className versus .htmlFor
  404. # [17:25] <nickshanks> anne: btw I apologise if my recent emails to you have seemed a bit strong or disrespectful, that was not intentional
  405. # [17:27] * annevk didn't really notice it...
  406. # [17:27] <nickshanks> cool :-)
  407. # [17:31] <webben> FS provide documentation in *.exe format. How very helpful.
  408. # [17:32] <nickshanks> heh: from the window-eyes web page on <abbr> and <acronym>:
  409. # [17:32] <nickshanks> <p><span style="font-family: 'Arial';">The Acronym and Abbreviation elements allow web page authors to indicate occurrences of abbreviations and acronyms. Acronyms are words formed from the first letters of each of the parts of the term (i.e. NATO, radar). Abbreviations are shortened forms of words (i.e. amt, lb).</span></p>
  410. # [17:33] <nickshanks> they don't even use the elements in the exact places they are supposed to be used :/
  411. # [17:34] <webben> heh
  412. # [17:35] <webben> have you seen FS's markup?
  413. # [17:35] <webben> it's something else...
  414. # [17:35] <nickshanks> fs?
  415. # [17:35] <webben> sorry Freedom Scientific
  416. # [17:35] <webben> (they make JAWS)
  417. # [17:36] <nickshanks> i won't comment on their use of span and font-family…
  418. # [17:44] * annevk wonders what the usecase is for loopStart
  419. # [17:44] * Quits: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net) (Remote closed the connection)
  420. # [17:44] <annevk> and if something like that is really needed, should it accept an array instead?
  421. # [17:45] * Joins: ericcarlson (n=ericcarl@adsl-67-115-144-162.dsl.snfc21.pacbell.net)
  422. # [17:46] <nickshanks> perhaps an int or array of length ≤ loopCount
  423. # [17:47] <annevk> if overloading works i suppose the feature isn't needed right away
  424. # [17:47] <annevk> also, I think it would be nice (as suggested in the minutes here) to replace .seek() with .position = x
  425. # [17:48] <annevk> that also allows you to skip with 20s using .position += 20
  426. # [18:47] * Joins: csarven (n=nevrasc@modemcable081.152-201-24.mc.videotron.ca)
  427. # [19:24] * Quits: annevk (n=annevk@5352CE6F.cable.casema.nl) (Read error: 110 (Connection timed out))
  428. # [19:30] <Hixie> can XSLT really not output arbitrary text?
  429. # [19:30] <Hixie> i thought it could
  430. # [19:42] * Joins: santek (n=st@ut-w-7bd6.mxs.adsl.euronet.nl)
  431. # [19:48] * Joins: zcorpan (n=zcorpan@84-216-41-105.sprayadsl.telenor.se)
  432. # [19:48] <zcorpan> <!doctype html public "html"> triggers quirks mode in at least gecko
  433. # [19:49] <hasather> Hixie: yes
  434. # [19:51] <zcorpan> <xsl:text disable-output-escaping="yes">&lt;doctype html></xsl:text> i think
  435. # [19:51] <hasather> yea, that should do it
  436. # [19:52] * zcorpan replies
  437. # [20:02] <Hixie> that's what i thought
  438. # [20:02] <Hixie> ok
  439. # [20:02] <Hixie> good
  440. # [20:02] <Hixie> glad we sorted that out
  441. # [20:02] <Hixie> http://www.w3.org/mid/A9925841-9449-4E5C-B149-EF07E1598735@iki.fi is the best anti-versioning e-mail i've seen this week
  442. # [20:03] <zcorpan> indeed
  443. # [20:03] <hasather> yep :)
  444. # [20:03] <zcorpan> i've del.icio.used it
  445. # [20:04] <hasather> BTW, I think Jirka meant that you can't output <!doctype html> with xsl:ouput, but that was not what he wrote
  446. # [20:04] <hasather> *xsl:output
  447. # [20:06] <zcorpan> then xslt should be updated so that it is possible to emit <!doctype html> with xsl:output. meanwhile there
  448. # [20:06] <zcorpan> 's a simple workaround
  449. # [20:06] <hasather> agreed
  450. # [20:06] <zcorpan> enter and ' are too close to eachother :(
  451. # [20:07] <hasather> agreed too
  452. # [20:17] <met_> tested <xsl:text disable-output-escaping="yes">&lt;doctype html></xsl:text> in Saxon it works, but is nasty in XSLT world
  453. # [20:19] <zcorpan> allowing a public identifier in html5 because of *some* xslt processors not being able to emit <!doctype html> is nasty in html world
  454. # [20:19] <met_> some or better say all?
  455. # [20:20] <zcorpan> you said it worked in Saxon. julian said it didn't work in all xslt processors (being an optional feature, apparently)
  456. # [20:20] * met_ oks
  457. # [20:22] <zcorpan> if you want to use xsl:output you can just emit the html4 strict doctype and be done with it
  458. # [20:27] <met_> but it's invalid HTML5, isn't? Although I suppose it will work in browsers.
  459. # [20:27] <zcorpan> yes and yes
  460. # [20:30] * moeffju is now known as moeffju[afk]
  461. # [20:31] * Parts: zcorpan (n=zcorpan@84-216-41-105.sprayadsl.telenor.se)
  462. # [20:34] * moeffju[afk] is now known as moeffju
  463. # [20:50] * Joins: zcorpan (n=zcorpan@84-216-41-105.sprayadsl.telenor.se)
  464. # [21:04] * moeffju is now known as moeffju[afk]
  465. # [21:34] * Quits: mw22 (n=chatzill@cc1057475-a.odz1.ov.home.nl) (Read error: 110 (Connection timed out))
  466. # [21:53] * Quits: ROBOd (n=robod@86.34.246.154) ("http://www.robodesign.ro")
  467. # [21:59] * Quits: met_ (n=Hassman@r5bx220.net.upc.cz) ("Chemists never die, they just stop reacting.")
  468. # [22:06] * Joins: aroben (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  469. # [22:07] * Quits: aroben (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net) (Remote closed the connection)
  470. # [22:08] * Joins: aroben (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  471. # [22:10] * Joins: met_ (n=Hassman@r5bx220.net.upc.cz)
  472. # [22:10] * Joins: aroben_ (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  473. # [22:10] * Quits: aroben_ (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net) (Read error: 104 (Connection reset by peer))
  474. # [22:11] * Joins: aroben_ (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net)
  475. # [22:20] * Quits: weinig (n=weinig@odin.landmark.edu)
  476. # [22:22] * Joins: weinig (n=weinig@odin.landmark.edu)
  477. # [22:26] * om_out is now known as othermaciej
  478. # [22:26] * Quits: aroben (n=adamrobe@adsl-70-231-241-194.dsl.snfc21.sbcglobal.net) (Read error: 110 (Connection timed out))
  479. # [22:31] * Quits: met_ (n=Hassman@r5bx220.net.upc.cz) ("Chemists never die, they just stop reacting.")
  480. # [23:05] * Quits: Lachy (n=Lachlan@210-84-40-143.dyn.iinet.net.au) (Read error: 104 (Connection reset by peer))
  481. # [23:06] * Joins: Lachy (n=Lachlan@210-84-40-143.dyn.iinet.net.au)
  482. # [23:12] * Joins: mw22____________ (n=chatzill@h8441169151.dsl.speedlinq.nl)
  483. # [23:12] * mw22____________ is now known as mw22
  484. # [23:26] * weinig is now known as weinig|bbl
  485. # Session Close: Mon Mar 26 00:00:00 2007

The end :)