| 00:02 | <Hixie> | i have no more outstanding feedback on the sql apis to reply to! |
| 00:03 | kingryan | tries to think of some feedback for the sql api |
| 00:03 | <kingryan> | :) |
| 00:06 | <Hixie> | please do |
| 00:06 | <Hixie> | the next thing on my list is video |
| 00:07 | <Hixie> | which is far less fun :-P |
| 00:08 | <kingryan> | I was just kidding. I don't really have any insight on, nor plans to use the sql api |
| 00:08 | <Hixie> | aw |
| 00:10 | <kingryan> | given that I work for a search engine, my mind is rather focused on the parsing part of the spec |
| 00:52 | <Hixie> | jgraham_: yt? |
| 00:53 | <Hixie> | jgraham_: we should make the link to http://code.google.com/p/html5lib/wiki/UserDocumentation more prominent on the html5lib homepage |
| 08:43 | <hsivonen> | Hixie: I got the first validation support question about HTML5 not having <applet> |
| 09:17 | <Lachy> | oh wow! There are still people that use java applets?! |
| 09:27 | <hsivonen> | Lachy: yeah. for example Opera. :-) |
| 09:32 | <Lachy> | hsivonen, where does Opera use java applets? |
| 13:55 | <hsivonen> | Hixie: <code title=attr-hyperlink-rel> what's the deal with having id-like data in the title attribute? |
| 13:57 | <zcorpan> | hsivonen: the spec post processor uses title="" |
| 13:57 | <zcorpan> | to automate the xrefs |
| 13:57 | <zcorpan> | it could use id="" instead, but now it doesn't :) |
| 13:58 | <hsivonen> | zcorpan: my sense of theoretical purity and elegance says those should be id attributes and the post processor should be smart enough not to collide with author-entered ids |
| 13:58 | <zcorpan> | indeed |
| 13:58 | <hsivonen> | also, from a usability point of view, it sucks to have machine ids in human readable content |
| 13:58 | <zcorpan> | although what would you use for the links? you can't use id="" there |
| 14:01 | <hsivonen> | zcorpan: the links? |
| 14:01 | <zcorpan> | yeah, the actual xrefs, not the definition |
| 14:02 | <zcorpan> | <dfn>foo</dfn> ... <span>foo</span> turns into <dfn id=...>foo</dfn> ... <a href=...>foo</a> |
| 14:02 | <hsivonen> | <a>foo</a>? |
| 14:03 | <zcorpan> | that could work, but what about when you want to use different text (which is when title currently is used)? |
| 14:03 | <zcorpan> | i.e. <span title=foo>bar</span> |
| 14:07 | <hsivonen> | <a href='#foo'>bar</a> |
| 14:07 | <hsivonen> | or <a r=foo>bar</a> |
| 14:07 | <hsivonen> | or [foo|bar] |
| 14:11 | <Lachy> | there's some documentation for the spec generator somewhere that explains how it works, somewhere in a W3C member only section |
| 14:35 | <hsivonen> | I wonder how many hours in my life has been wasted looking up namespace URIs for copying and pasting |
| 17:52 | <tantek> | hsivonen - if you do estimate the number of hours wasted, I'd love to quote you on it. |
| 17:52 | <tantek> | re: "hsivonen: I wonder how many hours in my life has been wasted looking up namespace URIs for copying and pasting" |
| 19:35 | <jacobolus> | does the <meta charset="utf-8"> thing work in all modern browsers? |
| 19:37 | <jacobolus> | or should I stick to <meta http-equiv="Content-type" content="text/html; charset=utf-8"> for the time being? |
| 19:43 | <virtuelv> | jacobolus: I was under the impression that <meta charset="utf-8"> got in to the specification because it actually works |
| 19:43 | <jacobolus> | okay. just wondering which browsers it works in |
| 19:44 | <jacobolus> | virtuelv: that was my impression as well, but want to be sure :) |
| 19:46 | <Philip`> | If you want to be surer that it'll work, why not use the HTTP Content-Type instead? :-) |
| 19:48 | <jacobolus> | Philip`: I plan on it :) |
| 19:48 | <jacobolus> | just wondering :) |
| 19:48 | <virtuelv> | Philip`: doesn't always work well when the delivery protocol is file:// |
| 19:48 | <kingryan> | why not use both? |
| 19:48 | <jacobolus> | yes, that's the plan. |
| 19:49 | <jacobolus> | i'm just wondering which browsers (if any) <meta charset="utf-8"> doesn't work for |
| 19:53 | <jacobolus> | well, I guess I'll just assume it's okay then :) |
| 19:54 | <jacobolus> | and if it breaks, I'll blame the whatwg |
| 19:54 | <jacobolus> | :P |
| 19:56 | <Philip`> | I don't remember anyone having mentioned a browser that it doesn't work in |
| 19:57 | <Philip`> | but presumably there's some level of obscurity at which you could find one |
| 19:57 | <jacobolus> | well that's fine |
| 19:57 | <jacobolus> | thanks :) |
| 23:40 | <jacobolus> | putting type="text/javascript" in <script …> is redundant and unnecessary, correct? |
| 23:41 | <Philip`> | Yes, since everyone defaults to JS |
| 23:44 | <jacobolus> | thx |
| 23:45 | <jacobolus> | it's very nice when writing tutorials to be able to drop all the BS extra voodoo characters normally used |
| 23:48 | <Philip`> | (<style type> is the same - it's really not useful to explicitly tell the browser that you want the same stylesheet language as 100% of other web pages) |
| 23:49 | <jacobolus> | ah, hadn't thought of that one. thanks :) |
| 23:51 | <Philip`> | http://www.centralfloridaregional.com/ - that has a strangely excessive use of 'xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:ehcCopyright="http://www.ehc.com"; xmlns:ehcOpenCube="http://www.ehc.com"; xmlns:ehcSiteSearch="http://www.ehc.com"'; |
| 23:52 | <jacobolus> | good god |
| 23:53 | <jacobolus> | does that do anything at all? |
| 23:53 | <jacobolus> | maybe it helps their back-end tools? |
| 23:55 | <Philip`> | The output isn't trying to be XML, so I expect they're not intending to read it back in and process it, and it looks like it's just leaking out of whatever backend tools they're using |
| 23:55 | <jacobolus> | right |
| 23:56 | <Philip`> | so I think it doesn't help anything, and it just looks really ugly :-) |
| 23:58 | <jacobolus> | so should type="text/css" be dropped from <link rel="stylesheet" …> as well then? |