| 00:01 | <Lachy> | that's what I thought, but I couldn't see anything in the spec that was the opposite of what I had suggested |
| 00:05 | <Facedown> | do you guys normally prefer validator.nu over w3? |
| 00:05 | <Facedown> | or do you use both? |
| 00:06 | Philip` | normally uses neither, and writes invalid code |
| 00:07 | <Facedown> | s/sarcasm//g |
| 00:08 | <Philip`> | (That is what I really do :-) ) |
| 00:08 | <jgraham> | Philip`: Knowing why it's non trivial to do doesn't make not having it any easier :) |
| 00:08 | <Lachy> | Facedown, if I'm writing HTML5, I use validator.nu. If I'm writing HTML4, I use w3 |
| 00:10 | <Facedown> | is there a disadvantage of validator.nu when in combo with html 4.01 strict? which i use |
| 00:10 | <Facedown> | theres no preset for html 4, but there is a parser |
| 00:12 | <Lachy> | The only issue is that validator.nu is still a work in progress, so it's possible that it won't be 100% accurate yet. Though, these days, it could probably be considered reliable enough |
| 00:12 | <Philip`> | jgraham: You could easily write an HTML preprocessor, and do all the non-trivial stuff before publishing since it'll be trivial when you don't have to worry about browsers doing it |
| 00:13 | <Philip`> | validator.w3.org isn't 100% accurate either, so it's more useful to compare their actual accuracy and not just the boolean of whether they're at 100% |
| 00:13 | <Lachy> | Facedown, hsivonen would be the best person to ask about it |
| 00:13 | <Philip`> | (but I have no idea how you would quantify their accuracy, so that's a bit useless) |
| 00:14 | <Facedown> | I just wish it was illegal for having optional end tags on elements that need end tags in html 4.01 strict |
| 00:14 | <Facedown> | in other words, i would want it to give me an error for missing an end tag since its still 'Strict' |
| 00:14 | <Lachy> | Facedown, what? |
| 00:14 | <jgraham> | Philip`: By coming up with a large testsuite of docs with errors and seeing what fraction of the errors they identify |
| 00:14 | <Facedown> | <p>test |
| 00:14 | <Lachy> | The <p> element doesn't need an end tag in HTML 4.01 though, so what you said didn't make sense |
| 00:15 | <Facedown> | that's what i'm talking about |
| 00:15 | <Facedown> | the spec/rules themselves for html 4 |
| 00:15 | <Facedown> | at least, 4.01 strict |
| 00:15 | <Lachy> | but what advantage is there? |
| 00:15 | <jgraham> | Facedown: That sounds more like a lint or something to enforce a set of style guidelines |
| 00:15 | <Facedown> | it would make sense to make <p>foo legal in 4.01 transitional, and <p>foo illegal in 4.01 strict imo |
| 00:16 | <Lachy> | the rules for implying an end tag are well defined and implemented (at least for <p>) |
| 00:17 | <Lachy> | but you're ignoring the reasons for why it was made optional to begin with: convenience for authors |
| 00:17 | <Facedown> | oh it's just p.. i assumed it was the majority of block level elements |
| 00:17 | <Lachy> | there are several elements with optional tags |
| 00:17 | <Lachy> | thead, tbody, tfoot, p, html, head, body |
| 00:18 | <Philip`> | http://www.whatwg.org/specs/web-apps/current-work/multipage/section-writing0.html#optional probably mostly matches HTML4 |
| 00:19 | <Lachy> | here's a more convenient reference for HTML4's optional tags http://www.w3.org/TR/html401/index/elements.html |
| 00:19 | <Facedown> | ah ty, Lachy.. i was going through elementby element |
| 00:20 | <Lachy> | LOL |
| 00:20 | <Facedown> | lol. |
| 00:21 | <Hixie> | Lachy: "An a element that links to a dfn element represents an instance of the term defined by the dfn element. |
| 00:21 | <Facedown> | what text editors do you guys use? |
| 00:22 | <Hixie> | " |
| 00:22 | <Facedown> | i've moved from dw8 to vim like 6 months ago, glad i did |
| 00:22 | <Facedown> | can't live without vim now |
| 00:23 | <Hixie> | emacs baby |
| 00:24 | <Facedown> | were you ever at one time a vi user? |
| 00:24 | <Hixie> | no |
| 00:24 | <Facedown> | i haven't tried emacs |
| 00:24 | <Lachy> | I use TextMate now |
| 00:24 | <Lachy> | emacs, vi and vim are for crazy people |
| 00:24 | <Facedown> | heh |
| 00:25 | <Facedown> | lachy - if you had 20 lines of text that you had to make a list items out of , how would you do it? |
| 00:25 | <Philip`> | I mostly use the default KDE text editor KPart which doesn't seem to even have a real name |
| 00:25 | <Facedown> | assuming we were on line 5 |
| 00:25 | <Facedown> | assuming there are <ul> and </ul> at the top and bottom |
| 00:25 | <Facedown> | of these 20 lines of text |
| 00:26 | <Hixie> | esc-ctrl-s ^\(.+\)$ ENTER <li>\1</li> ENTER ! |
| 00:26 | <Philip`> | Facedown: Copy-and-paste, which would take about ten seconds and zero brainpower |
| 00:26 | <Facedown> | the copy is not the same for each of the lines |
| 00:27 | <Facedown> | its unique copy |
| 00:27 | <Facedown> | if you're saying copy the same thing over and over |
| 00:27 | <Philip`> | I mean I'd copy the "<li>" and paste it on each line |
| 00:27 | <Facedown> | ah |
| 00:27 | <Facedown> | 10 seconds? would seem like 15 to me |
| 00:27 | <Facedown> | we're tabbing at least once, right? |
| 00:28 | <Philip`> | Brainpower should be expended on content, not on writing one-off scripts for your text editor :-) |
| 00:28 | <Facedown> | but what if you don't have to think about it |
| 00:28 | <Facedown> | if you're used to it |
| 00:28 | <Facedown> | i'm a beginner in vim so i still have to think about it for now |
| 00:29 | <Facedown> | qaI<li><esc>A</li><esc>j@20 i think is how it would work in vim |
| 00:29 | <Facedown> | i would record myself going to the start of the line, before the very first character and typing <li> then going to the end of the string and typing </li> and repeat that 19 more times |
| 00:29 | <Facedown> | i just dont see how id survive on a normal text editor now |
| 00:29 | <Facedown> | using a mouse you'd have to make sure you point it before the first character for every line and the end |
| 00:30 | <Philip`> | Instead of remembering all the Vim commands, I'd remember that </li> was optional so I could save time by omitting it :-) |
| 00:30 | <Facedown> | hah |
| 00:30 | <heycam> | :.,+19s/.*/<li>&<\/li>/ |
| 00:30 | <Facedown> | oh.. an alternative to recording it? mm |
| 00:30 | <Philip`> | Write "<li>", shift-home, ctrl-c, down-arrow, {ctrl-v, down-arrow, home}+ |
| 00:31 | <heycam> | yeah, run that substitution from the currently line to 19 lines down |
| 00:31 | <Facedown> | Philip` - i used to do it exactly the same way. |
| 00:31 | <Facedown> | EXACTLy that way.. wow |
| 00:31 | <Facedown> | but if you had to include the end tag, it'd be more of a hassle |
| 00:32 | <Philip`> | Then just do exactly the same, with 'end' instead of 'home' |
| 00:32 | <Facedown> | since you have to reach the first character of the line and thats a little harer than if you dont have to worry about the end tag |
| 00:32 | <Facedown> | right but like |
| 00:32 | <Facedown> | going to and fro |
| 00:32 | <Facedown> | unless you do all the beginning tags first |
| 00:32 | <Facedown> | you'd only have one of them to paste |
| 00:32 | <Facedown> | i might have just pasted the <li> and insert the / at the end for end tags |
| 00:33 | <Facedown> | so paste the <li> before and after, and manually insert the '/' when i'm done |
| 00:33 | <Lachy> | Facedown, I select all the lines, and use the option to wrap each line in an open/close tag (which defaults to li) |
| 00:33 | <Facedown> | doh, heh;) |
| 00:33 | <Philip`> | Do all the <li> first, then all the </li>, since it's much easier to repeat short actions lots of times than a longer action fewer times |
| 00:34 | <Facedown> | so <li>shift home ctrl c down arrow ctrl v for the next 19 lines and go to the first <li> and ctrl end, </li> and paste the '</li>' with ctrl end and ctrl v |
| 00:34 | <Facedown> | that's how i would have done it in dreamweaver |
| 00:35 | <Facedown> | down arrow, ctrl end, ctrl v |
| 00:35 | <Lachy> | in Dreamweaver, I switch to WYSIWYG mode, highlight the text, click the UL button, and then move the cursor to the beginning of each new point and press enter |
| 00:36 | <Philip`> | If I was lazy and there were lots of lines, I'd probably do perl -ne'print "<li>$_</li>\n"' and copy/paste the text through that |
| 00:36 | <Lachy> | but TextMate's Cmd+Ctrl+Shift+W is easier |
| 00:36 | <Philip`> | (and then I'd probably do it again with chomp) |
| 00:44 | <Lachy> | Hixie, in what way were people confused about the name <meter>? |
| 00:46 | <Hixie> | people keep thinking it means "number and unit" |
| 00:46 | <Hixie> | they think you can do <meter>5cm</meter> |
| 00:47 | <Lachy> | oh, stupid people. |
| 00:48 | <Facedown> | do pseudo-classes such as :link :visited and :active still have no effect on anything but anchors? (not talking about :hover since i know that can go for any element) |
| 00:48 | <Lachy> | <indicator> wouldn't be too bad, but it's a bit long. |
| 00:49 | <Lachy> | I think the problems with the name <meter> will subside once we get an actual implementation and people see what it does |
| 00:49 | <Lachy> | I mean, it's no where near as confusing as, for example, <address> has been over the years. |
| 00:50 | <Facedown> | oh man.. i'm still confused on address |
| 00:50 | <Lachy> | Facedown, just remember that <address> is not to be used for marking up addresses, and you'll be fine. |
| 00:50 | <Facedown> | that was sarcastic, right? heh.. |
| 00:51 | <Facedown> | i know theres a w3 definition that says it should only be used to markup the address of the author of the page or something |
| 00:51 | <Lachy> | sort of |
| 00:51 | <Facedown> | and if you have like lists of houses you shouldn't mark the addresses up with <address> |
| 00:51 | <Lachy> | yeah, a better name for it would have been <contact> |
| 00:51 | <Facedown> | if its a hotel site and an address for the hotel, im using <address> |
| 00:52 | <Facedown> | to contact the hotel that is |
| 00:55 | <Philip`> | I don't like <indicator> since it's not at all obvious what it's indicating |
| 00:55 | <Philip`> | and also "indicator" makes me think of flashing orange lights on cars |
| 00:55 | <Lachy> | Philip`, no, that's what <blink> is for |
| 00:56 | <Facedown> | haha |
| 00:56 | <Philip`> | Lachy: In that specific case, I think I'd be happier in a car that's made of steel rather than HTML |
| 00:57 | <Philip`> | Web browsers have a habit of crashing every few days |
| 00:58 | <Lachy> | ok. I'm happy with my HTML-mobile. |
| 00:58 | <Lachy> | it drives me around the web quite well |
| 00:59 | <Lachy> | of course, my preferred HTML-mobile is the Lynx. :-) |
| 01:01 | <Philip`> | Why not just use <gauge>, and define <guage> as a synonym? |
| 01:01 | <Lachy> | because gauge is a terrible name |
| 01:01 | <Philip`> | (assuming that's the misspelling that people will make) |
| 01:02 | <Lachy> | Philip`, it will be common, just like people misspell language as langauge |
| 01:03 | <Philip`> | http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/attr/langauge vs http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/attr/language - it's not that common an error |
| 01:03 | <Lachy> | hmm. I thought Hixie's stats had shown it was a bit more common |
| 01:04 | <Lachy> | but maybe I remmber incorrectly |
| 01:04 | <Philip`> | Fortunately his stats are unverifiable, so you can just ignore them as being bad science |
| 01:05 | <Lachy> | LOL |
| 01:12 | Philip` | still really needs to find a way to scale that analyse.cgi to sixteen times as much data, and preferably with more ways of looking at the data (e.g. seeing common attribute values) |
| 01:14 | <Lachy> | Philip`, if I ran your scripts on my computer and send you the results, would that help? |
| 01:15 | <Hixie> | the language thing i found was that there were many many many misspellings of language="" |
| 01:16 | <Philip`> | Lachy: The problem is doing the real-time web interface to the data, since it tends to require some tradeoff of disk space and processing time and cleverness |
| 01:18 | <Philip`> | Ah, http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/tag/script does have quite a few different errors |
| 01:18 | <Philip`> | (languaje, langage, maybe lang, ...) |
| 01:18 | <Hixie> | yeah people just can't spell that attribute to save their life |
| 01:18 | <Philip`> | Is it worse than any other attribute? |
| 01:19 | <Hixie> | yes |
| 01:19 | <Hixie> | far worse |
| 01:19 | <Hixie> | width and height get a few misspellings |
| 01:19 | <Hixie> | but e.g. type doesn't get many at all |
| 01:19 | <Hixie> | at least iirc |
| 01:19 | <Hixie> | bbiab food |
| 01:57 | <takkaria> | CSS3 columns are pretty useless for real content |
| 01:57 | <takkaria> | orphaned headings are a real no-no |
| 01:59 | <takkaria> | oh, it does have them now |
| 02:01 | <takkaria> | how useful. :) |
| 02:07 | <takkaria> | shame gecko doesn't implement them, though |
| 02:14 | <jruderman> | takkaria: gecko sorta implements parts (-moz-column-count, -moz-column-width |
| 02:14 | <jruderman> | takkaria: i'm not a big fan of the implementation, as roc or dbaron can attest ;) |
| 02:18 | <Facedown> | anyone experienced with inline-block layouts? |
| 02:19 | <Facedown> | if so, how are they compared to floats? of course, on any browser other than gecko based |
| 02:19 | <jruderman> | of course? |
| 02:19 | <Facedown> | since ff2 doesnt support inline-block |
| 02:19 | <Facedown> | not the proprietary property -moz-inline-box or whatever they have |
| 02:19 | <jruderman> | ff3 does |
| 02:19 | <Facedown> | your point? |
| 02:20 | <Facedown> | ff3 hasn't been released and ff2 is the most popular gecko browser |
| 02:20 | <Facedown> | or are you going to tell me to get the beta 5 |
| 02:20 | <jruderman> | beta 5? no, that's old, get a nightly :P |
| 02:20 | <jruderman> | j/k, beta 5 is fine |
| 02:21 | <Facedown> | but really, gecko doesnt support it.. as in, the majority of gecko browsers in use on earth |
| 02:21 | <Facedown> | that's what i meant |
| 02:21 | <jruderman> | ok |
| 02:21 | <takkaria> | jruderman: yeah it seems to work almost well enough, just not quite actually well enough. :) |
| 02:22 | <jruderman> | i don't see how an older version of gecko not supporting inline-block is relevant to answering the question "how are they compared to floats", but i guess i don't really understand the question anyway, since i mostly use CSS to crash things rather than build web pages with pretty layout |
| 02:24 | <jruderman> | inline-block can go anywhere in a line whereas floats can only go at the left or right, correct? |
| 02:33 | <othermaciej> | floats don't really go in a line per se |
| 02:33 | <othermaciej> | I mean |
| 02:34 | <othermaciej> | they intrude into several lines but are really owned by the containing block |
| 02:34 | <othermaciej> | an inline-block is in a specific place on the line |
| 02:35 | <othermaciej> | I don't think there are many places where they are interchangeabe |
| 04:29 | <MikeSmith> | Hixie, does the spec yet define what a "browsing context keyword" is? |
| 04:31 | <Hixie> | yes |
| 04:31 | <Hixie> | or rather |
| 04:31 | <Hixie> | no |
| 04:31 | <Hixie> | because that term is never used |
| 04:32 | <Hixie> | but the term "browsing context name or keyword" is defined |
| 04:36 | <MikeSmith> | Hixie, OK, I see now, "A valid browsing context name or keyword is any string that is either a valid browsing context name or that case-insensitively matches one of: _self, _parent, or _top." |
| 04:36 | <MikeSmith> | so that seems to implicitly define a keyword as "_self, _parent, or _top" |
| 04:36 | <MikeSmith> | is that right? |
| 04:38 | <Hixie> | i guess |
| 04:39 | <Hixie> | the two terms are "browsing context name" and "browsing context name or keyword", i didn't intent there to be a "browsing context keyword" term |
| 04:39 | <MikeSmith> | yeah, I realize that now |
| 04:59 | <MikeSmith> | Hixie, fwiw, it seem like the sentence "The rules for chosing a browsing context given a browsing context name are as follows." should be "The rules for chosing a browsing context given a browsing context name or keyword are as follows." |
| 04:59 | <Hixie> | hm yeah |
| 04:59 | <Hixie> | probably |
| 04:59 | <Hixie> | not a big deal |
| 05:00 | <Hixie> | it reads better the way it's written now |
| 05:00 | <Hixie> | what i really should do is find a word that means "name or keyword" |
| 05:01 | <MikeSmith> | yeah, that would be better |
| 05:01 | <MikeSmith> | "browsing context identifier"? |
| 05:04 | <Hixie> | maybe |
| 05:05 | <Hixie> | mail the list (or ian⊙hc) :-) |
| 07:32 | <hsivonen> | all caps headlines should be CSS |
| 07:32 | <hsivonen> | Hixie: And I don't like making title required, either |
| 07:33 | <Hixie> | all caps headliens should indeed be css, hence why people who have all caps headlines in the source are the least likely to be giving <abbr> elements |
| 07:33 | <Hixie> | what's the use case for <abbr> without title="", and why is it going to be important enough for us to not help authors using <abbr> to give abbreviation expansions? |
| 07:40 | <hsivonen> | Hixie: abbr itself is relatively unimportant compared to other HTML elements, so it shouldn't as for special attention |
| 07:41 | <Hixie> | i love all my children equally |
| 07:41 | <hsivonen> | as for use case, I'd need to research what UAs actually do with it |
| 07:41 | <hsivonen> | annevk seems to believe it is good for something |
| 07:42 | <hsivonen> | by using it |
| 07:42 | <hsivonen> | unless it's just a talisman use |
| 07:43 | <jwalden> | abbr? |
| 07:43 | <jwalden> | I thought some screen readers expanded it |
| 07:44 | <jwalden> | at least the first time they encountered it in a document |
| 07:44 | <MikeSmith> | jwalden, issue is whether abbr without a title attr is useful or now |
| 07:44 | <MikeSmith> | or not |
| 07:44 | <MikeSmith> | as far as screen-reader use, without title, nothing to expand |
| 07:45 | <jwalden> | I also seem to remember seeing at least one tutorial at some point which suggested using title the first time you had the abbr and then only marking up with <abbr></abbr> the remaining times |
| 07:45 | <hsivonen> | MikeSmith: unless the title is picked up from the first instance as suggested in the IRC log |
| 07:45 | <jwalden> | bingo |
| 07:45 | <hsivonen> | which I doubt considering how AT generally suck |
| 07:45 | <MikeSmith> | hsivonen, jwalden - ah, OK, I see |
| 07:46 | <jwalden> | it's convenient for authors, that's for sure |
| 07:46 | <jwalden> | easy for editors to support, too, I think |
| 07:47 | <jwalden> | saves space at the edges |
| 07:47 | <Hixie> | there are lots of people who suggest not giving the title="" |
| 07:47 | <MikeSmith> | yep. also addresses case that mpt mentioned where you don't want to AT app reading the expansion every single time the abbr appears |
| 07:47 | <Hixie> | as far as i can tell, that's just a talisman |
| 07:47 | MikeSmith | yep'ing what jwalden said earlier |
| 07:51 | <hsivonen> | Hixie: by that logic we should me <cite>, <em> and <var> non-conforming. They are only talisman versions of <i>. |
| 07:51 | <hsivonen> | but probably I shouldn't paint this bikeshed |
| 07:51 | <hsivonen> | since I really don't know about UA support or non-talisman use cases |
| 07:52 | <hsivonen> | s/me/make/ |
| 07:53 | <Hixie> | hsivonen: not all all, those have different styling in different contexts |
| 07:54 | <hsivonen> | Hixie: in that case, there's the use case of styling <abbr>s with small caps without caring about expansion |
| 08:03 | <Hixie> | does that use case happen enough that it outweighs the benefit of helping people using it to show the expansions? |
| 08:05 | <hsivonen> | I don't know |
| 08:06 | <hsivonen> | I guess we'll have to try changing the validator and see if anne et al change their markup to more useful as a result |
| 08:13 | <mpt> | Are you proposing making title= compulsory for <abbr>? |
| 08:14 | mpt | reads the logs |
| 08:15 | <Hixie> | read your mail :-) |
| 08:15 | <mpt> | ah |
| 08:16 | <mpt> | Your message shows up as blank for me |
| 08:16 | <Hixie> | ? |
| 08:16 | <Hixie> | odd |
| 08:16 | <mpt> | but I can see the message using View Source |
| 08:16 | mpt | kicks Thunderbird in the goolies |
| 08:16 | <Hixie> | that makes no sense to me |
| 08:21 | <mpt> | Same problem in Evolution |
| 08:21 | <mpt> | The message headers show, but no body |
| 08:23 | <mpt> | Same problem in Claws Mail |
| 08:24 | <jwalden> | which particular message? wfm in Thunderbird if I'm looking at the same one as you |
| 08:25 | <mpt> | <Pine.LNX.4.62.0804200415040.14701⊙hdc> |
| 08:25 | <mpt> | ("Feeedback on <dfn>, <abbr>, and other elements related to cross-references") |
| 08:25 | <jwalden> | shows up for me in... |
| 08:25 | <jwalden> | version 2.0.0.12 (20080213) |
| 08:25 | <mpt> | and the "[whatwg] Feeedback on <dfn>, <abbr>, and other elements related to cross-references" mailing list copy |
| 08:28 | <mpt> | Works in Apple Mail, though |
| 08:28 | <mpt> | Hixie has discovered a way to send e-mail messages that are readable only with proprietary software ;-) |
| 08:28 | <hsivonen> | mpt: oh are you still a closet OS X user? :-) |
| 08:29 | <Hixie> | it's just a text/plain message, no? |
| 08:30 | <mpt> | (though in Apple Mail it has the usual 'This message is in MIME format' and '=20' and '=3D""' poop) |
| 08:30 | <Hixie> | really? |
| 08:31 | <Hixie> | how did it end up in mime format |
| 08:31 | <mpt> | Your starts of threads usually are |
| 08:31 | <mpt> | Your responses usually aren't |
| 08:32 | <mpt> | It purports to be multipart/mixed |
| 08:32 | <mpt> | Do you start threads using different software? |
| 08:32 | <hsivonen> | mpt: does your IMAP server take liberties with the format? |
| 08:33 | <mpt> | Not that I know of |
| 08:33 | <mpt> | ah, I think I've found the problem |
| 08:33 | <mpt> | The message claims multipart/mixed, but then doesn't start with the segment boundary |
| 08:34 | <mpt> | whereas other multipart/mixed messages you send do start with one |
| 08:34 | <Hixie> | all pine |
| 08:35 | <Hixie> | so i guess we've found a pine bug |
| 08:38 | <mpt> | I have thought it strange before that you send a mixture of multipart/mixed and text/plain messages, but I just assumed that you were using your issue tracker software to start the threads or something |
| 08:39 | <Hixie> | i am |
| 08:39 | <Hixie> | but since my issues tracking software is pine |
| 08:39 | <Hixie> | that doesn't mean much |
| 08:39 | <Hixie> | :-) |
| 08:40 | <Hixie> | what do people think of footnotes? |
| 08:40 | <Hixie> | should we add markup for them? |
| 08:40 | <Hixie> | or just use internal links? |
| 08:41 | <hsivonen> | does anyone know of a servlet holder implementation that reads from System.in and writes to System.out? |
| 08:44 | <mpt> | Hixie, how about a special value for target=? |
| 08:44 | <mpt> | Then they can behave just like open-in-another-window links in legacy UAs |
| 08:45 | <hsivonen> | Hixie: I think footnotes suck on continuous media |
| 08:45 | <mpt> | but in UAs that recognize the value, they can open in a Footnote pane at the bottom of the window. |
| 08:45 | <hsivonen> | Hixie: I think the solution should render as margin notes on continuous media (<aside>?) and footnotes on paged media |
| 08:46 | <Hixie> | hmm |
| 08:46 | <mpt> | Hixie, and then authors could choose either internal or external links as convenient for them -- they'd work the same way. |
| 08:47 | <mpt> | (That doesn't solve the problem of how, for example, a speech browser should know when to stop when it starts reading a footnote.) |
| 08:49 | <virtuelv> | Hixie: what markup did you have in mind? |
| 08:49 | <mpt> | (But it does avoid solving the problem for footnotes but not for endnotes, or vice versa.) |
| 08:52 | <virtuelv> | I'm not entirely certain I mean what I'm saying now, but: Aren't footnotes in continuous media a disease? |
| 08:53 | <virtuelv> | Wasn't the the hyperlink invented to avoid having to do hacks like footnotes are? |
| 08:55 | <mpt> | Sure, but, but, but |
| 08:55 | <mpt> | hyperlinks are "heavy" |
| 08:55 | <mpt> | in that they take you out of your context |
| 08:55 | <mpt> | e.g. to a completely different page |
| 08:56 | <mpt> | You can have internal links, but then it's not obvious how to get back to where you were |
| 08:56 | <mpt> | (you can click Back, but many if not most people assume that Back means "the page I was on previously", because that's what it usually does) |
| 08:57 | <mpt> | So people insert special links to go back from a footnote <http://daringfireball.net/2005/07/footnotes>; |
| 08:58 | <hsivonen> | in addition to Gruber, Distler uses footnotes in blogging |
| 08:58 | <mpt> | and they do this in ways that might be obvious to sighted humans using graphical browsers, but not in other situations. |
| 08:59 | <hsivonen> | and the footnotes are de facto emphasis, because reading them requires special scrolling effort |
| 08:59 | <Hixie> | i have no opinion at the moment |
| 08:59 | <Hixie> | i'm trying to work out what to do |
| 09:00 | <mpt> | (see also <http://daringfireball.net/2005/08/notes_on_notes>;) |
| 09:02 | <zcorpan> | Hixie: <map> really needs name='', though i think you still have more feedback on that on your pile (from me and hsivonen) |
| 09:03 | <Hixie> | yeah |
| 09:03 | <Hixie> | i do |
| 09:03 | <Lachy> | Hixie, re your comment about data templates and wf2 repetition in the target attr mail, I agree with removing Data Templates, cause they're overly complicated and confusing, but WF2's repetition model should stay |
| 09:03 | <Hixie> | it's all going |
| 09:04 | <Hixie> | the repetition model sucks, and there's a bazillion ways of doing things like those, all of which have their own good points |
| 09:04 | <mpt> | An <a ... target="_note"> attribute, plus markup to specify where a footnote starts and ends, would give Prince enough information to print footnotes as footnotes (or even sidenotes!) rather than endnotes. |
| 09:04 | <Hixie> | the templates things is better than repetition blocks, anyway, it was designed to replace them |
| 09:05 | <Lachy> | I know it was designed to replace them, but it sucked cause no-one but you could ever understand it |
| 09:05 | <annevk> | Philip` got some of the details too, iirc |
| 09:05 | <annevk> | But yeah, data templates were complicated |
| 09:07 | <Lachy> | annevk, my theory is that's because Philip` and Hixie are the same person. :-) |
| 09:07 | <Philip`> | ( http://philip.html5.org/demos/datatemplate/experimental/002.html ) |
| 09:08 | <Hixie> | data templates are simple, they just needed explaining |
| 09:08 | <Hixie> | they're basically xul templates done right |
| 09:08 | <Hixie> | mpt: with an element for the endpoint of the footnote? |
| 09:09 | <Hixie> | mpt: as in, <a href="#f1" target="footnote">1</a> ... <footnote id=f1>...</footnote> ? |
| 09:09 | <mpt> | Hixie, it wouldn't need to be <footnote>, it could be <div> or <aside> or whatever suited them |
| 09:10 | <mpt> | but otherwise, yes |
| 09:10 | <hsivonen> | Hixie: huh? why are repetition templates going? |
| 09:10 | <Hixie> | that seems... not especially awesome |
| 09:10 | <Hixie> | hsivonen: because they're just one way of many ways to solve the problem, and not an especially good way at that |
| 09:10 | <Hixie> | hsivonen: better to leave that stuff up to the script authors |
| 09:10 | <Lachy> | I would prefer to combine the good parts of data templates (assuming there are any) with the simplicity of repetition templates |
| 09:11 | <Lachy> | doing such stuff with script is difficult to do efficiently |
| 09:11 | <Hixie> | then we should fix that |
| 09:11 | <Hixie> | and put in the infrastructure to allow all the various ways to do this to be done |
| 09:11 | <Hixie> | i've spoken with people who have so many different ways to solve this problem |
| 09:11 | <hsivonen> | Hixie: are we now expecting thin-client distributed mobile browsers to keep enough DOM around on the server to do scripted repetition? |
| 09:12 | <Hixie> | and their solutions are not worse than the specs' |
| 09:12 | <hsivonen> | does Opera Mini handle that already? |
| 09:12 | <Hixie> | hsivonen: if the client doesn't keep enough of the DOM around for this kind of thing, it's not conforming anyway |
| 09:13 | <hsivonen> | Hixie: so we're abandoning the noscript case? |
| 09:13 | <othermaciej> | do any distributed mobile browsers handle script running after the initial page load? |
| 09:13 | <hsivonen> | othermaciej: yes |
| 09:13 | <othermaciej> | then they'd better keep DOM around |
| 09:13 | <hsivonen> | othermaciej: the Validator.nu field inter-dependencies work in Mini |
| 09:14 | <Hixie> | hsivonen: for interactive things like that? yes, you need scripting for the more complicated parts anyway |
| 09:14 | hsivonen | wonders what the RAM footprint of the entire Opera Mini server farm is |
| 09:15 | <hsivonen> | Hixie: but yeah, I can see that the repetition model would be too simple for many things and authors would easily get into situations that need scripting anyway |
| 09:15 | <hsivonen> | Hixie: I'd be happy not to have data templates |
| 09:16 | <annevk> | I think the repetition model gives a very easy way for authors to duplicate form fields. Something that's currently quite tricky to script. (Tricky enough for me to just use 5 rows instead when I first encountered the issue.) |
| 09:16 | <mpt> | Hixie, I'm not claiming awesomeness, I'm just thinking of my ideal GUI for footnotes and working backwards :-) There might be other markup for implementing the same thing. |
| 09:16 | <annevk> | Now if data templates are effectively the same (I couldn't figure that out) that might be acceptable too... |
| 09:17 | <Hixie> | annevk: the repetition model isn't easy in real scenarios |
| 09:17 | <Hixie> | annevk: in fact it gets really freaking messy |
| 09:17 | <Hixie> | it was the result of my trying to address xforms' use cases instead of the web's |
| 09:17 | <othermaciej> | I never understood what the use case for the repetition model is |
| 09:17 | <hsivonen> | annevk: I think the repetition model is acceptable in the spec. data templates aren't, because if all people on this channel don't grok it, it's not going to fly |
| 09:17 | <othermaciej> | people have tried to claim it is good for shopping carts, but that does not make sense to me |
| 09:18 | <Hixie> | the data templates would be easy to understand if they were explained |
| 09:18 | <Hixie> | it's just that the spec is basically an english translation of code |
| 09:18 | <Philip`> | hsivonen: http://www.esato.com/archive/t.php/t-162718,1.html seems to have some information about Opera Mini servers |
| 09:18 | <annevk> | hsivonen, it might be that I wouldn't have understood repetition templates without the introduction section, so I'm willing to give data templates a chance |
| 09:18 | <Hixie> | without any exposition |
| 09:18 | <Hixie> | not that i'm arguing in favour of them, they're gonna be chopped out too |
| 09:18 | <Hixie> | we should work out what is needed to make scripting these things easier though |
| 09:18 | <hsivonen> | I still think data templates would be easier by going fully to script |
| 09:19 | <Hixie> | e.g. maybe we need some sort of search-and-replace API for attribute values and text content |
| 09:20 | <annevk> | othermaciej, it's for cases where you need to fill in a set of data n times |
| 09:21 | <othermaciej> | I don't recall having encountered a form like that |
| 09:21 | <othermaciej> | maybe it comes up more in corporate settings? |
| 09:21 | <Hixie> | it's pretty rare |
| 09:21 | <Hixie> | like i said |
| 09:21 | <Lachy> | I build a site a few years ago that used repeating form fields. Unfortunately, the site seems to have been rebuilt quite recently |
| 09:21 | <Hixie> | it was the result of my trying to address xforms' use cases instead of the web's |
| 09:21 | <othermaciej> | does any of you know of a form on a public web site where repetition model can apply? |
| 09:21 | <hsivonen> | Hixie: I think the preferrable way for bridging model and view is putting JS closures into the view onchange handlers so that the closures capture the model references appropriately |
| 09:22 | <hsivonen> | Hixie: if that's non-performant, I'd prefer JS engine improvement over HTML complexity |
| 09:22 | <annevk> | othermaciej, the form I had is gone, besides that I know it would be useful in PHPMyAdmin |
| 09:23 | <roc> | othermaciej: tag fields in the code.google.com bug tracker |
| 09:23 | <othermaciej> | roc: got a specific page example? |
| 09:23 | <hsivonen> | I developed an app with repeating forms three years ago for behind-the-firewall enterprise use |
| 09:24 | <hsivonen> | and it had more than one type of repeating block in one item list, so WF2 repetitions wouldn't have worked |
| 09:24 | <annevk> | othermaciej, http://code.google.com/p/html5lib/issues/entry |
| 09:24 | <annevk> | "Add a row" |
| 09:24 | <roc> | http://code.google.com/p/chronicle-recorder/issues/detail?id=4#makechanges |
| 09:25 | <Hixie> | hsivonen: i have no idea what you're proposing :-) |
| 09:25 | <othermaciej> | I must be slow because I don't see what you guys are referring to on either of those pages |
| 09:25 | <roc> | although I'm not a proponent of declarative repetition, myself |
| 09:25 | <annevk> | othermaciej, maybe you need to be logged in |
| 09:25 | <othermaciej> | I'm logged in with my google account |
| 09:25 | <othermaciej> | but I don't belong to either of those projects |
| 09:25 | <Hixie> | The "Add a row" link at the bottom of anne's page |
| 09:26 | <hsivonen> | Hixie: suppose you have a form field in the view and you want the data in it to be reflected to an XML tree load/saved using XHR |
| 09:26 | <Hixie> | or the "Attach a file" link on roc's |
| 09:26 | <Hixie> | also at the bottom |
| 09:26 | <hsivonen> | Hixie: so when you initialize the binding, you copy the value from the XML tree to the view and install closures as onchange handlers in the view |
| 09:26 | <Hixie> | hsivonen: "in the view"? |
| 09:27 | <hsivonen> | Hixie: so that the right model node gets captured into each onchange closure copy |
| 09:27 | <hsivonen> | Hixie: the form field |
| 09:27 | <othermaciej> | I don't see an "add a row" link on anne's or an "attach a file" link on roc's |
| 09:27 | <Philip`> | othermaciej: Maybe you're using an unsupported browser? |
| 09:27 | <hsivonen> | Hixie: I'm assuming that the data template thing was about binding an HTML view to an XML model |
| 09:28 | <hsivonen> | Hixie: like XUL templates bind a XUL view to an RDF model |
| 09:28 | <Hixie> | hsivonen: i don't really understand all the fancy terms in your description :-) |
| 09:28 | <roc> | othermaciej: try clicking on the link "Add a comment and make changes below" on the LHS |
| 09:28 | <Hixie> | hsivonen: i mean, i understand them in isolation, but strung together like that i don't follow :-) |
| 09:29 | <othermaciej> | ok when I click the "add a comment |
| 09:29 | <Hixie> | hsivonen: what would it look like to the author? |
| 09:29 | <roc> | we have XML and SQL model support now |
| 09:29 | <roc> | no nasty RDF |
| 09:29 | <othermaciej> | "" link I see the attach a file link |
| 09:29 | <othermaciej> | I'll buy that as straight-up repetition |
| 09:29 | <othermaciej> | (though multi-file selection in <input type="file"> might be a better solution for that use case) |
| 09:30 | <roc> | yeah |
| 09:30 | <roc> | we need that |
| 09:30 | <hsivonen> | Hixie: viewfield.value = modelelement.textContent; viewfield.onchange = function () { modelelement.textContent = this.value; } |
| 09:31 | <zcorpan> | hmm i almost replied to an email in the alt thread |
| 09:31 | <zcorpan> | i figure that's not really needed |
| 09:32 | <Hixie> | zcorpan: feel free to reply to the one on the whatwg, that one's actually making some (minor) progress |
| 09:32 | <Hixie> | hsivonen: isn't that possible already then? |
| 09:32 | <hsivonen> | Hixie: yes. that's the point :-) |
| 09:32 | <annevk> | i tried replying to the alt thread a few times, it resulted in n^2 of collateral damage |
| 09:32 | <annevk> | so I guess I learned my lesson :D |
| 09:33 | <hsivonen> | Hixie: the only problem is that browser developers tell me it doesn't have nice memory footprint |
| 09:33 | <Hixie> | hsivonen: "waah" |
| 09:34 | <Hixie> | my ipod has hundreds of megabytes of memory |
| 09:34 | <hsivonen> | Hixie: so I would rather see work go into making the memory situation less of an issue than trying to work around it by adding complexity to HTML |
| 09:34 | <Hixie> | by the time html5 is done... |
| 09:35 | <zcorpan> | Hixie: ok, sent it |
| 09:38 | <hsivonen> | Hixie: well, unless I remember incorrectly, hyatt's argument against JS closures and for data templates was about perf/memory characteristics, so if you can convince him about the future iPod memory... :-) |
| 09:40 | <Hixie> | if we keep either of the current templating things, i'm also adding the ~4 other templating ideas that people have discussed with me that are at least as good and all different |
| 09:40 | <Hixie> | such as daniel's html overlays, and the system google maps uses for business information page generation |
| 09:48 | <Philip`> | Hixie: So HTML5 should add a <media> element for playing video-audio content, because that's at least as good a name as <video>? |
| 09:49 | <Hixie> | it's a matter of functonality, not names |
| 09:50 | <Philip`> | It seems a more general issue that sometimes you have to choose between equally-good options, because making any choice is better than making no choice |
| 09:50 | Lachy | agrees with hsivonen that "User agents are encouraged to default to being configured to always reuse the current browsing context, or to at least provide that option to the user." should be dropped from the spec. |
| 09:50 | <Hixie> | these aren't equally good options |
| 09:50 | <Hixie> | they're different options that solve different but equally important use cases |
| 09:51 | <Hixie> | Lachy: send feedback to the list please :-) |
| 09:51 | <Lachy> | Hixie, if I sent it to the list, it would just be a "+1" |
| 09:51 | <Hixie> | oh wait, crap, that's what henri was talking about? |
| 09:51 | <Hixie> | i just deleted that message because it looked like it was about alt stuff again and it was just a public-html message |
| 09:52 | <Lachy> | LOL |
| 09:52 | <Philip`> | Adding all the different options would be too complex for implementors and authors, so that's never going to work, and supporting the use cases for one of the options (which probably overlaps partially with those of the other options') seems more useful than supporting none |
| 09:52 | <Lachy> | so you didn't actually read it? |
| 09:52 | <Philip`> | s/'// |
| 09:52 | <Hixie> | i read it, but apparently not in enough detail to determine what it was about |
| 09:53 | <hsivonen> | alt collateral damage... |
| 09:53 | <Hixie> | Philip`: i'm saying we should support all of them, by providing necessary plumbing to enable all of them to be implemented easily from script |
| 09:54 | <Philip`> | Hixie: Okay, that sounds like a good thing to say :-) |
| 09:54 | <Hixie> | Philip`: i'm just not sure what that plumbing is :-) |
| 09:54 | <Hixie> | hsivonen: oh, i see what happened |
| 09:55 | <Hixie> | hsivonen: i read the subject line and everything you wrote |
| 09:55 | <othermaciej> | failing to open a new window/tab for _blank will just encourage authors to use window.open for that purpose |
| 09:55 | <Hixie> | hsivonen: and didn't read what you were quoting |
| 09:55 | <Hixie> | hsivonen: and i agreed with everything you wrote, so i assumed you were replying to the alt text debate |
| 09:55 | <othermaciej> | or target="randomname" which just introduces opportunity for conflicts if there is no need to reuse the window by name |
| 09:55 | <Hixie> | and nothing in the subject line or the body of your text actually requested a change to the spec |
| 09:55 | <Hixie> | so i ignored it :-) |
| 09:56 | <Hixie> | (and since it wasn't sent to whatwg, i didn't file it to get a reply) |
| 09:56 | <Hixie> | Lachy: so please do reply, but in your text say what should change, so i can file it :-D |
| 09:57 | <Hixie> | othermaciej: the way the spec is written, the code that would fail to open a window for _blank would be the same code that would fail to open a window for window.open |
| 09:57 | <Hixie> | othermaciej: and also target=randomname |
| 09:57 | <Hixie> | othermaciej: all of those hook into the same algorithm, and it's that algorithm that says that UAs are encouraged to just reuse the current window |
| 09:58 | <othermaciej> | then I guess the terrifying next-best alternative is in-window DOM popovers |
| 09:58 | <othermaciej> | which I hate much much more than actual separate windows |
| 09:59 | <Hixie> | those are fine, they just make me close the page without any further damage |
| 09:59 | <jgraham_> | The choice of preferring the user v preferring authors for browser defaults is kind of complex to summarise in a single sentence |
| 09:59 | <jgraham_> | and I don't think generally works as "always prefer X" |
| 10:00 | <othermaciej> | it depends on whether the author has a more-evil workaround, and how evil the original feature is |
| 10:01 | <othermaciej> | for example I think Safari's default cookie policy (which effectively prevents most cookie-based cross-site tracking) is good despite being less author-friendly then always accepting and sending all cookies |
| 10:01 | <jgraham_> | and how evil the workaround is |
| 10:01 | <Philip`> | If window.open reused the current window (in a new tab), hopefully it'd be like Opera (at least on Linux) where you still get a thing that looks like a window with the right size, instead of being a full-screen tab and destroying the layout |
| 10:02 | <jgraham_> | Philip`: I have never found that I really missed explicit window sizes |
| 10:06 | <Lachy> | Hixie, I replied to the thread. But I thought hsivonen's email clearly implied that the recommendation should be removed. |
| 10:07 | <Hixie> | yeah see my comments above -- the only part of his mail that mentioend what he was talking about what hte part where he quoted a (poorly wrapped) diff, which i skipped over when reading his mail, since it wasn't from him |
| 10:09 | <Hixie> | and since i sent the e-mail where i mentioned this to whatwg, i assumed that since his mail was to public-html it was about something else :-) |
| 10:09 | <Hixie> | anyway, replied |
| 10:09 | <Lachy> | ok, well I didn't suggest an explicit change. But I explained why making that the default is a bad idea, from which you should be able to determine an appropriate change |
| 10:18 | <Hixie> | yeah |
| 10:18 | <Hixie> | i explained why you were wrong :-) |
| 10:19 | <Philip`> | "it's the only part of the spec that creates a new window." - that just means people will use other specs to create a new window |
| 10:19 | <Lachy> | Hixie, and I'm responding to explain why you're wrong :-) |
| 10:20 | <annevk> | Philip`, it's the only spec that defines windows :) |
| 10:20 | <Hixie> | i think i'm just going to not add new footnote markup |
| 10:20 | <Philip`> | annevk: Other specs can reference it (maybe implicitly), and define some API that actually really opens windows |
| 10:21 | <Philip`> | Presumably Flash is one of those things |
| 10:21 | <Hixie> | i can't really come up with a good way of doing them |
| 10:21 | <othermaciej> | Flash and Java can open windows |
| 10:21 | <Hixie> | Philip`: i would recommend that UAs make these prefs apply to those too |
| 10:22 | <Philip`> | Eventually people will find a plugin that simulates sending Ctrl+N keystrokes to the browser to open a new window |
| 10:22 | <Hixie> | i'm ok with that |
| 10:22 | <Hixie> | since i won't have that plugin running |
| 10:22 | <othermaciej> | opening windows in the current browsing context will probably be extra annoying in the JAaa and Flash cases |
| 10:22 | <othermaciej> | *Java |
| 10:22 | <Hixie> | i have java disabled |
| 10:22 | <Philip`> | Hixie: Then all the links will be broken and you won't be able to browse the web |
| 10:22 | Lachy | never thought he would be defending the default behaviour of opening popus :-/ |
| 10:22 | <othermaciej> | probably pretty annoying when you click a help link that is meant to open in a help window |
| 10:23 | <othermaciej> | Hixie: it's not a very good argument to say that default UA settings should cater to your customized UA settings |
| 10:23 | <Hixie> | Philip`: like i said earlier, if a page starts screwing around like that, i just close the tab and go elsewhere |
| 10:23 | <annevk> | yeah, you don't want those help popups in the same window |
| 10:23 | <annevk> | that would be a disaster |
| 10:23 | <othermaciej> | I don't think the encouragement is very relevant anyway |
| 10:23 | <Hixie> | Philip`: the problem i have with new windows is that there the annoyance happens before i can close the window and causes extra damage to closing the window |
| 10:23 | <annevk> | the encouragement leads to advocacy in browser bug databases |
| 10:23 | <othermaciej> | it's not even a real conformance requirement |
| 10:23 | <Philip`> | Oh, reusing the current browsing context instead of just the current window? That sounds like it'd never work, because someone would fill in a complex form and click the 'help' popup link and lose all their data and cry and switch browser |
| 10:23 | <Hixie> | othermaciej: if i want a help link in another window, i command-click it |
| 10:24 | <annevk> | Hixie, i don't |
| 10:24 | <annevk> | my parents don't |
| 10:24 | <annevk> | my friends don't |
| 10:24 | <annevk> | etc. |
| 10:24 | <othermaciej> | Hixie: you are using "I" an awful lot in this discussion about what UA settings are appropriate defaults |
| 10:24 | <Hixie> | annevk: hey! |
| 10:24 | <annevk> | well, apart from you :p |
| 10:24 | <Hixie> | othermaciej: yup :-) |
| 10:25 | <Hixie> | Philip`: that's what the "open link in new tab" ui and the back button are for |
| 10:25 | <othermaciej> | defaults should be set to be right for the typical user |
| 10:26 | <othermaciej> | and none of us here is a very good model of the typical user |
| 10:27 | <othermaciej> | though at least using oneself as an example is more honest than the "my grandmother would..." argument |
| 10:27 | <Hixie> | fine fine, changed it to be a recommendation to provider a pref instead of a recommendation for the default |
| 10:31 | <Lachy> | Hixie, thanks. |
| 10:37 | <Hixie> | dbaron: (discussion on the matter can be found above) |
| 10:41 | <jwalden> | othermaciej: another repetition use case is at the bottom of the advanced search page in bugzilla |
| 10:41 | <jwalden> | where you want and/or with <something> <relationship> <textfield> |
| 11:31 | <Lachy> | I just read Microsoft's XDR proposal for the first time. It really doesn't seem to offer any advantages over XHR and AccessControl. I don't get why they proposed it. |
| 11:32 | <annevk> | they believe it's more secure |
| 11:34 | <Hixie> | it's less secure |
| 11:38 | <Lachy> | yeah, I'm looking for the explanations on how it's less secure. |
| 11:38 | <Philip`> | Maybe implementations of XDR would be more secure, since it's simpler and it doesn't have to interact with all the existing complex XHR code and so there's significantly less chance of bugs |
| 11:42 | <annevk> | xhr code is not complex |
| 11:42 | <annevk> | or does not have to be anyway |
| 11:43 | <Philip`> | 'Doesn't have to be complex' != 'Isn't complex' |
| 11:44 | <Philip`> | particularly for people like Microsoft who had to implement it before there was a spec |
| 11:44 | <annevk> | Lachy, xdr encourages a design where people have to share their login code of their gmail account for instance, it encourages content sniffing, |
| 11:44 | <Philip`> | (and hence might have an architecture that is incompatible with what the spec is based on, so small changes in the spec require significant changes in the implementation) |
| 11:44 | <annevk> | Philip`, everyone had to implement it before there was a spec, from public available source code webkit shows it does not have to be complex |
| 11:45 | <annevk> | (is this one of your truth finding games again? :) ) |
| 11:47 | <Philip`> | (I never know the truth, so everything is trying to find it :-) ) |
| 11:47 | Philip` | tries to find the appropriate bit of WebKit... |
| 11:47 | <annevk> | it's in the xml folder iirc |
| 11:48 | <annevk> | WebCore/xml |
| 11:48 | <Philip`> | http://trac.webkit.org/projects/webkit/browser/trunk/WebCore/xml/XMLHttpRequest.cpp - that looks like it |
| 11:50 | <Lachy> | annevk, I don't see how it encourages such a design, and can't find any mail in the archive that describes anything like that. |
| 11:51 | <Philip`> | I suppose 800 lines of code and ~200 revisions doesn't seem especially complex |
| 11:52 | <annevk> | Lachy, you're not trying very hard then :) |
| 11:52 | <Philip`> | http://mxr.mozilla.org/seamonkey/source/content/base/src/nsXMLHttpRequest.cpp has ~3 times as much code and a similar number of revisions |
| 11:53 | <annevk> | Gecko isn't know for its pretty source code :) |
| 11:53 | <annevk> | known, even |
| 11:53 | <annevk> | I find the Gecko code quite hard to grasp |
| 11:54 | <Philip`> | About the only Gecko code I've looked at in any detail is the canvas implementation, and that's mostly interfacing with Cairo rather than with Mozilla |
| 11:54 | <Lachy> | annevk, I know. I only skimmed the archives. I will have a better look later when I have time |
| 11:54 | <Philip`> | (or at least I can ignore (or copy-and-paste) the Mozilla-interfacing code without understanding it) |
| 11:56 | <Philip`> | s/Mozilla/Gecko/ or whatever |
| 11:56 | Philip` | isn't very good at keeping all the terms straight |
| 13:13 | <krijnh> | Lachy: okay if I stop logging #xhtml ? ;) |
| 13:13 | <annevk> | could you log #css perhaps? |
| 13:13 | <krijnh> | Here? |
| 13:13 | <annevk> | no, on irc.w3.org:80 |
| 13:14 | <krijnh> | I think so |
| 13:14 | <annevk> | it's resolved to be a public channel, but nobody is logging... |
| 13:14 | <Hixie> | i like the #xhtml logs |
| 13:14 | <krijnh> | Hixie: you do at the moment? :) |
| 13:14 | <Hixie> | though nothing exciting has happened recently |
| 13:15 | <Hixie> | i check them occasionally |
| 13:15 | <Hixie> | nothing has happened of interest in months though |
| 13:15 | <Hixie> | partially because they know it's logged |
| 13:15 | <krijnh> | Hmm |
| 13:18 | <Hixie> | bed time |
| 13:18 | <Hixie> | nn |
| 13:18 | <krijnh> | :w |
| 13:20 | <annevk> | just log it |
| 13:20 | <annevk> | make it less prominent on the logging page maybe because it's far less relevant |
| 13:28 | <krijnh> | Done |
| 13:28 | <krijnh> | http://krijnhoetmer.nl/irc-logs/css/20080421 |
| 13:44 | <Philip`> | The #css log is boring |
| 13:45 | <Philip`> | Someone needs to do some trolling in there |
| 13:46 | <krijnh> | :) |
| 13:47 | <Lachy> | krijnh, I left #xhtml today cause I got tired of oedipus telling me he was away |
| 13:47 | <krijnh> | Lachy: Yeah, I logged that |
| 13:50 | <Lachy> | #webapi might be interesting too, though it's quite low traffic |
| 13:50 | <annevk> | same for #wai-aria |
| 13:50 | <krijnh> | -_- |
| 13:50 | <annevk> | #webapi is not a public channel |
| 13:50 | <Lachy> | really? |
| 13:50 | <annevk> | yes |
| 13:50 | <annevk> | though #webapi on freenode might be, not sure if anyone is still there though |
| 13:51 | <Lachy> | yeah, Hixie, othermaciej, deltab and myself are in there. Nothing is ever discussed in there though |
| 13:52 | <Philip`> | Looks like he was emitting an away message every 16 minutes 40 seconds, which is a slightly peculiar timing |
| 13:52 | <annevk> | it's American for 15 minutes |
| 13:52 | <Lachy> | Philip` that's every 1000 seconds |
| 13:53 | <Philip`> | Ah, that makes it sound less peculiar |
| 13:53 | <Lachy> | or 10 minutes in metric time :-) |
| 13:54 | <Philip`> | If we have to call megabytes "mebibytes" because they're based on binary counting, metric time has to use "deminutes" and "dehours" |
| 13:55 | <Philip`> | otherwise there will be horrible confusion |
| 13:56 | <annevk> | dinutes and dours |
| 13:57 | <Lachy> | it depends what's considered to be the base unit |
| 13:58 | <Lachy> | if the day is the base unit, then we would have milliday, deciday, megaday, etc. |
| 13:59 | <Philip`> | A day is a silly unit |
| 13:59 | <Philip`> | It doesn't correspond exactly to anything physically existent or useful |
| 13:59 | <Lachy> | of course, if star trek is true, we'll all be using star date in the 24th century, so we may aswell switch to that now. |
| 14:00 | krijnh | thinks about not logging #whatwg anymore either.. |
| 14:00 | <Philip`> | Relativity makes time measurement hard |
| 14:00 | <krijnh> | Silly topics in here |
| 14:00 | <Philip`> | We have a hard enough time coping with timezones and leap seconds |
| 14:01 | <Philip`> | (Uh, maybe "hard ... time" wasn't the most appropriate phrase there) |
| 14:01 | <Philip`> | krijnh: They're important topics relating to the standardisation of all aspects of the future world |
| 14:02 | <Lachy> | we should just abolish leap years and leap seconds, by adjusting the rotation of the earth and the orbit of the sun, so that each day is exactly 10 hours, and each year is exactly 100 days. |
| 14:02 | <Lachy> | but then an hour would be ~2.4 times longer than it is now |
| 14:03 | <Philip`> | If you make the Earth spin at 2.4 times its current speed, wouldn't that mean hours would still be the same length? |
| 14:04 | <Philip`> | As a bonus, geosynchronous orbit wouldn't be so far out |
| 14:05 | <Lachy> | no, I meant to adjust the rotation slightly so that a day is exactly 24 hours (current time scale), and then redefine the hour to be 1/10th of a day |
| 14:05 | <Philip`> | Hmm, insufficiently ambitious |
| 14:07 | <Lachy> | then move the earth's orbit away from the sun about 20,000km (which will help with global warming), then speed make it orbit faster (taking relativity into account) so that each year is 100 days. |
| 14:08 | <Lachy> | since we'll be moving faster, time will move slower, and everyone will live longer :-) |
| 14:08 | <Philip`> | If you move it further away and speed it up, it'll end up with a horribly elliptic orbit |
| 14:10 | <Philip`> | ("speed up" in the sense of "radians per second", not "metres per second") |
| 14:10 | <Lachy> | not if we increase the mass of the sun, which will increase its gravity, and thus make the planet orbit faster |
| 14:11 | <Philip`> | Good point |
| 14:11 | <Lachy> | we've got 7 other planets we can throw into it to do that |
| 14:12 | <Philip`> | They have pretty negligible mass |
| 14:12 | <Lachy> | jupiter is significant |
| 14:12 | <Philip`> | Not compared to the Sun |
| 14:12 | <Lachy> | is it enough to increase the sun's mass by the necessary amount? |
| 14:14 | <Philip`> | Jupiter: 1.8986×10^27 kg |
| 14:14 | <Philip`> | Sun: 1.9891×10^30 kg |
| 14:14 | <Philip`> | 0.1% isn't going to do very much at all |
| 14:16 | <Lachy> | maybe we just wait till Andromeda collides with the Milky Way, and one of those stars will merge with the sun to make it big enough. |
| 14:18 | <Philip`> | Stars don't just merge - the momentum needs to go somewhere |
| 14:18 | <Lachy> | hmm. true |
| 14:19 | <Philip`> | If you make a little man out of plasticine and stand him on a wall, and shoot him with a rifle with a plasticine bullet, they don't merge into a slightly larger man standing on the wall |
| 14:19 | <Lachy> | what about just moving earth to a larger star? |
| 14:20 | <krijnh> | annevk: can't you change the topic in #css ? :) |
| 14:21 | <mpt> | Philip`, that's because the difference between the bullet's force and the gravitational force is big enough. But that's nothing to do with why stars don't merge when galaxies do. |
| 14:22 | <Lachy> | what would really happen if two stars got close enough, is that they would begin to orbit each other forming a binary system, and gradually get closer and closer. |
| 14:22 | <Philip`> | mpt: Sorry, logical arguments are not allowed in here |
| 14:22 | <Lachy> | I'm not sure what effect the gravitational waves would have upon the earth then, it might tear it apart. |
| 14:23 | <mpt> | Philip`, pants. |
| 14:24 | <Philip`> | Lachy: Depends on their initial relative velocities |
| 14:24 | <Philip`> | They usually wouldn't just happily fall into a circular orbit for no reason |
| 14:25 | <Lachy> | and would also depend on their individual mass too |
| 14:25 | <Philip`> | and I have no idea what conditions would be needed for them to orbit at all, instead of just swinging past each other |
| 14:25 | <Philip`> | mpt: Okay, you win that argument :-( |
| 14:29 | <annevk> | krijnh, everyone can as far as I can tell |
| 14:30 | <annevk> | krijnh, though I made the change I guess you were hinting at... |
| 14:53 | <krijnh> | Thanks, wouldn't be nice if I were logging without anybody knowing :) |
| 15:26 | <hendry> | anyone know of a good CJK test suite? testing shiftjis, euc-jp character encodings? |
| 16:12 | hendry | discovers dns under Standard metadata names |
| 16:12 | <hendry> | I wonder if that will help my browser stop acting stupid when DNS drops or my net connection is a little unstable |
| 17:20 | <zcorpan_> | Hixie: <object> doesn't list name='' as its attributes and name is missing in the idl |
| 17:32 | zcorpan_ | updated html5-elements |
| 18:10 | annevk | should update html5-diff |
| 18:19 | <hsivonen_> | krijnh: logging #xhtml is useful |
| 18:21 | <Dashiva> | Maybe the bot should filter away messages :) |
| 18:22 | <hsivonen_> | krijnh: and logging #wai-aria on w3.org would be useful, too |
| 18:23 | <BenMillard> | hsivonen_, +1 |
| 18:25 | <Dashiva> | Pretty warlike convo in xhtml: "our position seems to be getting stronger; TBL seemed to lean our way; think we are winning" |
| 18:26 | <Philip`> | I'd like a war in which you could win by having someone lean at you, instead of having to bomb and shoot tens of thousands of people |
| 18:27 | <Dashiva> | Play board games :) |
| 18:27 | Philip` | dislikes cross-posting public-html and whatwg combined with whatwg's member-only posting and his different email addresses used for each list |
| 18:31 | <annevk> | maybe you should use a single e-mail address :) |
| 18:31 | <Philip`> | That would be too convenient |
| 18:32 | <Philip`> | and I don't want to change any of the ones that I use, for legacy compatibility |
| 18:32 | <Philip`> | (and because I'm lazy) |
| 18:33 | <Dashiva> | I like being able to sort by email address |
| 18:35 | <annevk> | hmm, xtech.org is hit by encoding errors |
| 18:35 | <annevk> | it also uses some weird ass html |
| 18:36 | <Lachy> | I tried filtering by haing different email addresses once. I find it mostly ineffective and useless. Filtering on list-id is better |
| 18:38 | <Dashiva> | Well, it saves you from having to configure the client every time you join a new list |
| 18:38 | <Dashiva> | And it works for non-list mail too :) |
| 18:39 | <BenMillard> | annevk, I noticed lots of <a href="foo" title=""> on there some time ago. But that's really good for accessibility; it uses the title attribute. |
| 18:39 | <Philip`> | In theory, having multiple email addresses lets you work out where spammers are finding your address from |
| 18:40 | <BenMillard> | annevk, having their homepage at http://2008.xtech.org/public/news is weird, though |
| 18:40 | <Dashiva> | Philip`: Yeah. Like I get a lot more spam on my w3c sub than the whatwg one. Odd |
| 18:42 | <Philip`> | I suppose the actual result is that you get all the spam sent to one address, plus all the spam sent to the other address, so you end up with twice as much spam |
| 18:42 | <Dashiva> | Yeah, makes it much easier for the filter to catch it |
| 18:42 | <Lachy> | Before I disabled it, I use to get spam sent to email addresses like [message-id]@lachy.id.au, where they got that from the w3 archives |
| 18:44 | <Lachy> | Dashiva, how does using mutliple email addresses save you from having to configure the client for every new list? Don't you get a new email address for each list? |
| 18:44 | <Lachy> | or do you use each email for a group of lists? |
| 18:45 | <annevk> | BenMillard, setting title to the empty string is good for access? |
| 18:45 | annevk | isn't sure he got the point |
| 18:45 | <Dashiva> | Lachy: Groups |
| 18:45 | <Dashiva> | Like I have one for all the whatwg lists and non-list whatwg correspondence |
| 18:45 | <BenMillard> | annevk, :D |
| 18:47 | <Lachy> | ok. I use procmail to filter all my mail into appropriate folders on the server side now, typically based on list-id, and most other things go into the inbox |
| 18:48 | <BenMillard> | annevk, it was a joke: the authors or their authoring tool probably think generting title on every <a href> is a good thing, even though it is nearly always the empty string on that site |
| 18:48 | <annevk> | ah :) |
| 18:48 | <annevk> | I mostly use the title attribute if the contents of the <a> element are not clear enough or quite different from the title of the page I'm pointing at |
| 18:48 | <annevk> | of course, given that the Web can always change it's not guaranteed to be accurate :) |
| 18:49 | Dashiva | used <abbr @title> today |
| 18:49 | <BenMillard> | annevk, it's surprising how many sites I've built where the client has added title="foo" where the link text already said "foo" |
| 18:50 | <Philip`> | Dashiva: Did you use it for writing human/machine-readable dates? |
| 18:50 | <annevk> | that seems kind of pointless :) |
| 18:50 | <Dashiva> | Philip`: No, for the ACM ICPC |
| 18:50 | <BenMillard> | annevk, my suspicion is there's some bullshit SEO crooks making a living from coning clients who don't know better into paying for it |
| 18:50 | <Philip`> | Dashiva: Ah, sounds like you're in the minority then |
| 18:50 | <BenMillard> | making websites is pretty sad at times |
| 18:50 | <BenMillard> | s/coning/conning |
| 18:50 | <annevk> | nah, making web sites is cool |
| 18:51 | <Philip`> | Making people visit your web site is the sad part |
| 18:51 | <Philip`> | particularly when it's someone else's site, and it's really boring, but they want lots of visitors anyway |
| 18:51 | <BenMillard> | you need to hire an SEO crook! |
| 18:51 | <Dashiva> | Philip`: That sounds like a potential analogy for too many current events |
| 18:53 | Philip` | fails to understand the reference :-( |
| 18:53 | <Dashiva> | Maybe I should have included an alternate non-subtle representation of the reference |
| 18:55 | <Philip`> | Ah |
| 18:55 | Philip` | goes home |
| 18:59 | <Philip`> | (but not before noting that http://www.w3.org/Consortium/sup is still an amusing example of SEO) |
| 19:00 | <annevk> | '<meta name="ROBOTS" content="INDEX, NOFOLLOW" />' |
| 19:07 | <annevk> | To keep the WHATWG blog active and useful should we try to post an update of what's going on every two weeks or every week or so? |
| 19:08 | <annevk> | I'm willing to put some effort behind doing that, though I'm pretty sure my writings will be biased. I guess I'm asking the rest of you to be editor for corrections, etc. Either by comments or modifications to the post directly... |
| 19:10 | <BenMillard> | that blog is a soapbox so, bias seems fine to me |
| 19:10 | <annevk> | I'm assuming lots of people will take it as authorative for one reason or another so keeping it as accurate and objective as possible would be good :) |
| 19:11 | <BenMillard> | a summary of what's gone on every 2 weeks sounds great, though |
| 19:12 | <BenMillard> | CSSWG's blog have little messages with resolutions and stuff quite regularly these days |
| 19:46 | <Philip`> | We should get two very differently biased people, and they can write summaries of alternate weeks, so the biases cancel out |
| 19:48 | <hsivonen> | http://krijnhoetmer.nl/irc-logs/xhtml/20080416#l-156 |
| 20:21 | <webben> | BenMillard: Have you considered setting up a paypal donate button or something else that would make it easy to send you money, btw? |
| 20:25 | <BenMillard> | webben, considered it but sustainable funding can't be a few people sending a dollar each week |
| 20:25 | <BenMillard> | which, for a niche subject like this, is probably all that would retrieve |
| 20:25 | <BenMillard> | electronic banking (such as BACS) is convenient once you exchange details |
| 20:26 | <BenMillard> | why do you ask? feel like giving me £1,000? :) |
| 20:31 | <webben> | BenMillard: I wish. Just thinking about Clark's patronage drive for a similar niche thing. |
| 20:31 | <webben> | (not quite as niche, admittedly) |
| 20:31 | <webben> | BenMillard: It might also help if you gave some indication of how much you think would pay for what? |
| 20:32 | <webben> | how much more will accessible with TABLE be if we were to give you £100? Or £500? Or £1,000? Or £10,000? |
| 20:33 | <webben> | granted it's hard to know |
| 20:44 | <gsnedders> | Error: obsolete example. BAR no longer exist as an F1 team :P |
| 20:45 | hsivonen | tries to stay out of the abbr thread; writes software instead |
| 20:46 | <BenMillard> | webben, people I've spoken to about sponsorship generally seem unwilling to talk money in public |
| 20:46 | <BenMillard> | webben, but I'm fine with doing so |
| 20:46 | <BenMillard> | webben, I'm pricing the research at £10 as it's just about livable (although drastically less than I can earn making websites) |
| 20:46 | <BenMillard> | £10 per hour, I mean |
| 20:48 | <BenMillard> | measuring the cost-effectiveness in terms of how many times a user no longer experiences a problem with a table when they would have previously is beyond me |
| 20:48 | <webben> | yeah, I was being a bit flippant |
| 20:48 | <BenMillard> | I think it's a valid question, though :) |
| 20:48 | <webben> | you might try estimating how long you think a given task might take |
| 20:48 | <webben> | in days/weeks |
| 20:48 | <webben> | and costing that way |
| 20:49 | <BenMillard> | Collections of Interesting Data Tables was about 100 hours (somewhere in that order of magnitude) |
| 20:50 | <BenMillard> | that was spread over several months as it wasn't sponsored |
| 20:50 | <BenMillard> | changes to the spec came several months after that |
| 20:51 | <BenMillard> | (they aren't my work, though) |
| 20:51 | <webben> | I wonder if there's a tenured academic who might be interested in some of these tasks. |
| 20:51 | <webben> | they might find it more affordable |
| 20:51 | <BenMillard> | I think having an actual professional content author who is involved with accessibility and standards work brings a lot of benefits...namely realism |
| 20:52 | <BenMillard> | but the more research the merrier |
| 20:52 | <BenMillard> | Philip`'s statistics are fabulous...someone needs to give him a big pile of cash |
| 20:54 | gsnedders | has been using Philip` to get HTTP headers, seeming he's been making plenty of requests :P |
| 20:58 | <BenMillard> | I've spammed WAI IG about funding and to raise awareness about the work http://lists.w3.org/Archives/Public/w3c-wai-ig/2008AprJun/0021.html |
| 20:58 | <BenMillard> | MikeSmith suggested I send something their way; Shawn Henry pointed me to exactly where |
| 20:59 | <BenMillard> | off for dinner now, then hibernation. bye all! |
| 21:09 | <Philip`> | I approve of the idea of giving me a big pile of cash |
| 21:10 | Philip` | transfers £1000 from his bank account to himself |
| 21:12 | <Philip`> | Actually, that's a bad idea since I need that money to pay for accommodation... |
| 21:19 | <gsnedders> | annevk: ping (molly wants to know if you're around) |
| 21:19 | <annevk> | i am |
| 21:20 | gsnedders | passes message on |
| 21:20 | <gsnedders> | everything thing I say is bullshit, and I'm just a messenger boy :P |
| 21:22 | <annevk> | hi Molly_ |
| 21:22 | <Molly_> | hey anne! |
| 21:22 | <Philip`> | gsnedders: You should get a job as an offline message service for MSN, so someone can give you a message to pass onto their friend once they come online |
| 21:22 | <annevk> | so i guess you saw my twitter :) |
| 21:22 | <Molly_> | Anne: It was your Twitter ping that inspired my visit |
| 21:23 | <annevk> | hehe |
| 21:23 | <Molly_> | Annevk: Yes |
| 21:23 | <gsnedders> | hah. |
| 21:23 | <Philip`> | (Or does MSN do that yet? ICQ has had that for decades...) |
| 21:23 | <gsnedders> | Philip`: MSN doesn't. |
| 21:23 | <gsnedders> | It's what my school uses :( |
| 21:23 | <gsnedders> | (well, everyone at my school) |
| 21:23 | <Molly_> | So here's the thing, I have done NO organization or promotion of this thing |
| 21:23 | <annevk> | Molly_, from all WHATWG fanboys, I believe only Henri and myself will show up |
| 21:23 | <gsnedders> | annevk: not fanbois? |
| 21:23 | <Molly_> | but if we get something out there, we can do something |
| 21:23 | <gsnedders> | :P |
| 21:23 | <Molly_> | you mean to xTech itself? |
| 21:23 | <annevk> | yeah |
| 21:24 | <annevk> | oh right |
| 21:24 | <annevk> | it could be promoted separate from XTech |
| 21:24 | <Molly_> | annevk: it can be, yes, and we can also directly ask people we know will be there |
| 21:24 | <tomg> | er MSN has offline messaging |
| 21:24 | <gsnedders> | Have it on the biggest island of the British Isles! |
| 21:24 | <gsnedders> | tomg: since when? :\ |
| 21:24 | <Molly_> | annevk: Something where everyone gets a chance to talk about the Open Web as they see it. They would get a certain amount of time |
| 21:25 | <tomg> | with the official client |
| 21:25 | <Molly_> | that sort of thing? We need to do something with the room |
| 21:25 | <gsnedders> | tomg: Peh! Who uses that!? :P |
| 21:25 | <tomg> | gsnedders: few years? |
| 21:25 | <tomg> | not I |
| 21:25 | <gsnedders> | tomg: the Messenger for Mac doesn't support it |
| 21:25 | <tomg> | not entirely sure why Adium and co don't do it though |
| 21:25 | <Molly_> | annevk: The other thought I had was to do that and/or have a "sandbox" room - informal for people to hang out, maybe a planned "open Mike" or something |
| 21:25 | <annevk> | Molly_, yeah, everyone is required to do their 1 minute pitch and then we go out for a beer |
| 21:25 | <gsnedders> | tomg: So only the official Windows one does. |
| 21:26 | <tomg> | Messenger for Mac barely does anything as it is :) |
| 21:26 | <Molly_> | annevk: I like the way you think LOL |
| 21:26 | <gsnedders> | tomg: next version of the Mac one is meant to have feature parity with the next version of the Windows one, though |
| 21:26 | <Molly_> | annevk: and if only you, Henri, and I show up it'll be three minutes and then off to the pub. |
| 21:26 | Philip` | likes BitlBee + irssi + screen as an MSN/etc client, though that might be partly because he never talks to anyone and he's happy it sits unobtrusively in the background |
| 21:26 | <gsnedders> | (but likely will still have a horrid UI) |
| 21:26 | <annevk> | Molly_, hehe |
| 21:27 | <Molly_> | annevk: What about David Storey? |
| 21:27 | <annevk> | Molly_, just having an informal chat on where everyone wants to go would be cool |
| 21:27 | <annevk> | i've actually no idea if david will shop up |
| 21:27 | <annevk> | i suppose he might :) |
| 21:27 | <Molly_> | hahaha |
| 21:27 | <Molly_> | if there's beer! |
| 21:27 | <annevk> | and a room to crash in :p |
| 21:27 | <gsnedders> | :P |
| 21:27 | <tomg> | gsnedders: there's not much point in them bothering with Adium around :) |
| 21:28 | <gsnedders> | I tell you, you're as bad as my friends, Molly_ :) |
| 21:28 | Molly_ | rolls eyes at both annevk and gsnedders |
| 21:28 | <tomg> | I'm so glad this train has automated stop announcements it's so easy to get wrapped up in IRC |
| 21:28 | <gsnedders> | tomg: Until a year or so ago, I would have now bitched about the horridness of its UI :) |
| 21:28 | <tomg> | skins! |
| 21:28 | <gsnedders> | tomg: Proteus looks good out of the box, though. I don't want to spend ten hours making an IM client usable :) |
| 21:29 | <gsnedders> | Or just fit into Aqua at all. |
| 21:29 | <tomg> | well, ok :) |
| 21:29 | <hsivonen> | Molly_: HTML5 side event at XTech? |
| 21:30 | <annevk> | that'd be cool too |
| 21:30 | <Molly_> | hsivonen: Ooh, that could be very cool |
| 21:30 | <annevk> | especially if we can get lots of developers and designers to show up |
| 21:30 | <hsivonen> | were you talking about something else? |
| 21:30 | <Molly_> | hsivonen: what do you think about you and Anne doing a presentation about key topics in HTML5? |
| 21:30 | <annevk> | we weren't really sure yet |
| 21:30 | <Molly_> | that would be awesome! |
| 21:31 | <Molly_> | hell, I'd go to that just as an attendee myself |
| 21:31 | <annevk> | Molly_, you have the room on May 6? |
| 21:32 | annevk | arrives evening May 4 |
| 21:32 | <Molly_> | is that the workshop day? |
| 21:32 | <hsivonen> | I suppose I could say a word or two |
| 21:32 | <annevk> | i believe so, yes |
| 21:32 | <annevk> | yeah, May 6 is tutorial/workshop |
| 21:32 | <annevk> | May 7-9 is the conference |
| 21:32 | <Molly_> | yep that's the day |
| 21:32 | <Molly_> | we have it the entire day |
| 21:33 | <annevk> | nice |
| 21:33 | <hsivonen> | I arrive on May 5th, so May 6th works for me |
| 21:33 | <annevk> | now the question is how we reach developers etc. in Dublin |
| 21:34 | <annevk> | Molly_, I guess your blog would work best for that ;) |
| 21:34 | <Molly_> | that's not the problem at all, really - we can all blog it once we agree what we're doing and then get it out on upcoming and facebook |
| 21:35 | <tomg> | Dublin? |
| 21:35 | <gsnedders> | And pay for me to come to Dublin :P |
| 21:35 | <gsnedders> | And get me off school :P |
| 21:35 | <annevk> | tomg, http://2008.xtech.org/ |
| 21:35 | <tomg> | ah |
| 21:35 | <annevk> | gsnedders, getting to Dublin is cheap using Ryanair or something |
| 21:35 | <Molly_> | tomg: sorry! |
| 21:35 | <annevk> | I got a 35 EUR ticket from Madrid |
| 21:36 | <Molly_> | tomg: I should have explained myself better |
| 21:36 | <gsnedders> | annevk: true. But school. :( |
| 21:36 | <tomg> | urm. if my 3G will work. which it isn't |
| 21:36 | <jgraham_> | If you could insert an extra week into the year so that I can come too, it would be much appreciated :) |
| 21:36 | <annevk> | 35 EUR is 25 EUR cheaper than a supposedly _free_ ticket from Flying Blue (Air France / KLM "fame") |
| 21:36 | Molly_ | can write a letter "dear snedds' school, please let him come to Dublin with us. We promise to leave him outside the pub" |
| 21:37 | <gsnedders> | :D |
| 21:37 | <tomg> | dodgy dodgy connection. :( |
| 21:37 | <gsnedders> | I'll probably make it to the TP if there's an HTML WG meeting again |
| 21:40 | <jgraham_> | Molly_: I think you're OK to take gsnedders _into_ the pub, he just can't have alcohol |
| 21:40 | <gsnedders> | jgraham_: I dunno about Irish law. It's different within the union, yet alone outwith it. |
| 21:40 | <Molly_> | okay, how about this. We'll start at 10, and have an "Open the Web" session which I'll do (I'll get videos and fun stuff from lots of people who can't be there - let me know if you want to do that) . That'll be an hour. Then an HTML5 session with Anne and Henri? Then, lunch on our own, back by 13:30 for "Open the Web" open discussion 'til tea-time around 3pm, then how about an "open mike" style lightening talk where anyone can get up and do 2 |
| 21:41 | <gsnedders> | "get up and do 2" (it cut off there) |
| 21:41 | <jgraham_> | gsnedders: Well I found a very non-authoritative looking website that said that |
| 21:41 | <tomg> | ouch |
| 21:41 | <gsnedders> | jgraham_: heh. |
| 21:41 | <tomg> | these conferences are expensive |
| 21:41 | <Molly_> | this day is free |
| 21:41 | <Molly_> | that's the other point btw |
| 21:41 | <gsnedders> | jgraham_: Need to get me out of school first, though, and to Erie |
| 21:41 | <Molly_> | this is open to the public (first come first serve in terms of space) but free |
| 21:41 | <Molly_> | as I'm the one buying the room, not the conference |
| 21:42 | <gsnedders> | Well, I of course have a place if I'm there, but I'm special :P |
| 21:42 | Molly_ | wonders if gsnedders means special as in "short bus" special or something else? |
| 21:42 | <jgraham_> | gsnedders: I would be more sympathetic if I could make it :) |
| 21:42 | <hsivonen> | Molly_: seems OK |
| 21:43 | <gsnedders> | Molly_: special as in knowing the organiser :) |
| 21:43 | <Molly_> | anyone else have any ideas? All ideas welcome! |
| 21:43 | <gsnedders> | Give me money? |
| 21:43 | <Molly_> | and if you happen to be in Dublin, come! |
| 21:43 | <Molly_> | gsnedders: why would I give you money, even if I had it to give? |
| 21:44 | <gsnedders> | Molly_: Because I'm lovesick (though you don't know that :P) and awesome. |
| 21:44 | <annevk> | Molly_, sounds good to me |
| 21:44 | <annevk> | tomg, you don't have to come to the conference |
| 21:45 | <Molly_> | tomg: that's the point, if you can come along to Dublin you can join us for the conf |
| 21:45 | <Molly_> | er, the day |
| 21:45 | <annevk> | tomg, the place we have on May 6 is paid for by Molly Inc. |
| 21:45 | <tomg> | nice |
| 21:45 | <Philip`> | annevk: You could probably reply to Smylers' "Can you link to examples of such webpages, which have <abbr> elements without title attibutes? What does that mark-up currently achieve?" |
| 21:45 | <tomg> | ohh. get to get off train. |
| 21:45 | <tomg> | er, got |
| 21:45 | <Philip`> | since http://www.w3.org/TR/XMLHttpRequest/ has <abbr>e.g.</abbr> |
| 21:45 | <tomg> | bye! |
| 21:45 | <Molly_> | I just expect everyone to be paying for my beers at the pub. And I'm not a cheap drunk :D |
| 21:45 | <annevk> | see you |
| 21:46 | Molly_ | waves by to tomg |
| 21:46 | <Philip`> | (although "could" probably doesn't mean "should") |
| 21:46 | gsnedders | actually marks up e.g. as <i lang="la"><abbr title="exempli gratia">e.g.</abbr></i> |
| 21:46 | <annevk> | Philip`, I think I was just in a marking up phase... |
| 21:46 | <annevk> | Molly_, hah |
| 21:46 | <hsivonen> | Molly_: that would break the pattern :-) |
| 21:47 | <gsnedders> | Molly_: you know I wouldn't :) |
| 21:47 | Molly_ | is laughing so hard she needs to get a glass of water |
| 21:47 | <gsnedders> | Molly_: Well, at least I'm not making you snort up Pepsi through your nose again :) |
| 21:48 | <Molly_> | the things some people know about me. sheesh. Well, at least I know I've made a mark in this world, however infamous rather than famous it might be |
| 21:48 | <gsnedders> | :P |
| 21:48 | <jgraham_> | gsnedders: OOI it was the 9th May that you wanted to meet up in Cambridge, not the 10th, right? |
| 21:48 | <gsnedders> | jgraham_: Friday. |
| 21:48 | jgraham_ | needs to avoid double booking himself |
| 21:48 | <gsnedders> | Don't ask me the date! |
| 21:49 | <Philip`> | Friday is the 9th |
| 21:49 | <jgraham_> | gsnedders: Friday is good :) |
| 21:49 | <gsnedders> | Assuming Philip` is right, the 9th therefore. |
| 21:49 | <Philip`> | unless my calendar is lying |
| 21:49 | <Philip`> | or unless my calendar is correct but my clock is lying |
| 21:49 | <gsnedders> | My calendar agrees, FWIW |
| 21:50 | <Philip`> | Ah, so that answer wins best out of three |
| 21:50 | <jgraham_> | Yeah, I knew the 9th was the Friday |
| 21:54 | <hsivonen> | I deployed the new iframe/object browsing context stuff and the abbr-title thing |
| 21:54 | <gsnedders> | jgraham_: <http://flickr.com/photos/gsnedders/2427943333/sizes/o/in/set-72157604643134411/>; — that shows the distortion of the lens quite well, FWIW |
| 21:55 | <gsnedders> | (i.e., the tower should be straight) |
| 22:01 | <Molly_> | @hsivonen: Henri, how do you best like to present? Just talk w/ slides? On a panel? Interview? |
| 22:01 | <Molly_> | I'm thinking it might be fun to do at least part of the HTML5 as an interview |
| 22:02 | <Molly_> | so some "hot topic" questions can be asked |
| 22:02 | <Molly_> | etc. |
| 22:02 | <Molly_> | sorry, I'm twittering too much. everything is now @nick etc. |
| 22:02 | <Molly_> | that would be: |
| 22:03 | <Molly_> | hsivonen: please see above :) |
| 22:19 | <hsivonen> | hmm. panel/interview means less work for me but also means inconvenient questions. hmm. |
| 22:20 | <hsivonen> | Molly_: I think I'd like to say a something prepared briefly first and then open the mic for questions |
| 22:20 | <Molly_> | hsivonen: Henri, that sounds good. But you'll have to be prepared for some "inconvenience" of course ;) |
| 22:21 | <hsivonen> | yeah :-) |
| 22:21 | Molly_ | waves at KevinMarks |
| 22:21 | <hsivonen> | Molly_: specifically, I'd like to replay the TPAC bit about commoditizing HTML parsing |
| 22:22 | <Molly_> | hsivonen: One thing that occurs to me is that some people who might show up in the early part of the day won't know too much about HTML5 itself. I want your or Anne or someone to do a "10 things you must know" kind of talk to start off. Then open to questions |
| 22:23 | <Molly_> | hsivonen: then in the afternoon there's room for detailed presentations |
| 22:23 | <Molly_> | hsivonen: what do you think? |
| 22:23 | <Molly_> | all? Anyone? We're putting together a free day of material on HTML5, browsers, open web ideas - free to the public in Dublin on 6 May |
| 22:23 | <Molly_> | help out! |
| 22:24 | <hsivonen> | Molly_: I believe Anne already has a practical "HTML5 in a few slides" presentation |
| 22:24 | <Molly_> | hsivonen: that sounds perfect |
| 22:26 | <Molly_> | last year I called it "Blue Sky" and referred to it as a "Browser Summit" |
| 22:26 | <Molly_> | we should do something with the name |
| 22:27 | <Molly_> | and do them elsewhere too |
| 22:27 | <Molly_> | FutureWeb! |
| 22:28 | <Molly_> | we could go with a FutureShock theme |
| 22:31 | Philip` | is more interested in LegacyWeb |
| 22:32 | <Philip`> | which I suppose is basically the same thing, since the future is just a continuation of the past |
| 22:32 | <Philip`> | except that in the future we'll have accumulated more mistakes |
| 22:33 | <Philip`> | (Maybe I'm just being pessimistic) |
| 22:37 | <annevk> | Molly_, FutureWeb! sounds good |
| 22:37 | <annevk> | maybe have a subtitle with HTML5, etc. in it |
| 22:38 | <Molly_> | annevk: I looked up the domain and it isn't available. the .net version is for 3.5k USD |
| 22:38 | <Molly_> | annevk: I'm thinking for future events, etc. |
| 22:39 | <Molly_> | annevk: This is something I want to keep going, and encourage others to do where/when/how they can |
| 22:39 | <Molly_> | hmmmm |
| 22:39 | <hsivonen> | annevk: did your HTML5 intro slides have strategy/economics/anti-lock-in stuff on them or just examples of new features? |
| 22:40 | <annevk> | i had several |
| 22:40 | <annevk> | some talked about design principles and such |
| 22:41 | <hsivonen> | ok |
| 22:41 | <Molly_> | we need a very basic top 10 things you (devs/designers) need to know about HTML5 |
| 22:41 | <Molly_> | then anything branching from that is good |
| 22:41 | <Molly_> | I just think that's really important to start with |
| 22:41 | <Molly_> | that, and q&a |
| 22:42 | <annevk> | Molly_, there's a similar domain name available but if I mention it here it might get squatted... |
| 22:42 | <annevk> | Molly_, yeah, i can give such a high level intro to HTML5 |
| 22:42 | <Molly_> | annevk: send 'em to me private I'll immediately register whatever is yummy :) |
| 22:42 | <Molly_> | annevk: Perfect |
| 22:42 | <annevk> | are you registered on freenode? |
| 22:43 | <annevk> | private messaging on freenode sucks :( |
| 22:44 | <hsivonen> | Molly_: I think the top 10 need to know things do include design principle stuff and evangelism about off-the-shelf parsing |
| 22:45 | <annevk> | Molly_, e-mailed |
| 22:45 | <Molly_> | hsivonen: I understand and agree. Of course, remember that our audience will be very mixed |
| 22:45 | <Molly_> | so we need a variety of topics from what will seem very basic to you |
| 22:45 | <Molly_> | to more detailed, no? |
| 22:45 | <hsivonen> | yeah |
| 22:46 | <Molly_> | annevk: got it, thx |
| 22:51 | <Molly_> | annevk: I pwn both .com and .org of that lovely domain now! |
| 22:51 | <Molly_> | now we have to do something with it :) |
| 22:54 | <Molly_> | I'm going to work on some text about the event |
| 22:56 | <Lachy> | what's the new domain name? |
| 22:56 | <hsivonen> | Molly_, annevk: 10 points: http://pastebin.ca/992541 |
| 22:56 | <Molly_> | Lachy: Hey Lachlan! |
| 22:57 | <Molly_> | the new domain names are futurewebevent.com and futurewebevent.org |
| 22:57 | <Molly_> | I like the singularity of the name :D |
| 22:57 | <Molly_> | we can have one event, or many |
| 22:58 | <Molly_> | and of course, it could happen at /any/ time |
| 22:58 | <Molly_> | it's totally asynchronous |
| 23:01 | <Lachy> | hi Molly! |
| 23:05 | <Molly_> | Lachy: Nice to "see" you :D |