| 00:02 | <roc> | Anne's right of course, but this situation is a bit different from line breaking in that with line breaking, there often is no clearly "right" algorithm, but it's pretty clear that shaping across element boundaries *should* work |
| 00:09 | <mercator> | That might not always be the case, either, if, say, you float one part of the ligature or something... (But that is decidedly CSS.) |
| 00:11 | <roc> | sure there are edge cases, but when it's obvious that it should work, it should work :-) |
| 00:14 | <annevk> | I wish writing specs worked like that |
| 00:14 | <annevk> | Invoking X must do what is obvious for Y |
| 00:15 | <zewt> | step 1: just do it |
| 00:23 | <roc> | I'm not suggesting specs should be written like that, of course. Just that implementation quality should be judged that way when specs are silent |
| 00:35 | <mercator> | Thanks for the insights! |
| 03:09 | <boblet> | foolip: know when microdata will be in a public (non-dev) release of Opera? I’m guessing Opera 12, but not sure if that’s imminent or a wee way off yet… (and yes that does mean I’m updating a certain article ;) |
| 03:12 | <boblet> | also, any Moz ppl know about the progress of microdata ref: https://bugzilla.mozilla.org/show_bug.cgi?id=591467 ? also guessing WIP and not imminent… |
| 04:03 | <roc> | boblet: looks like it just needs review ... that could happen anytime, and then it would show up in nightlies within a day or three |
| 04:04 | <boblet> | roc: thanks for the explanation |
| 09:57 | <smaug____> | and yet another wontfix/reopen/wontfix/reopen cycle coming... |
| 10:02 | <janv_> | you mean bug 12945 ? |
| 10:03 | <janv_> | ah |
| 10:03 | <janv_> | I see |
| 10:03 | <janv_> | just got the bugmail |
| 10:04 | <smaug____> | janv_: yep |
| 10:05 | <annevk> | prolly more productive to try to get input from other implementors than argue in that bug |
| 10:06 | <smaug____> | yeah, getting input from implementors would be great |
| 10:06 | <smaug____> | randomly just wontfixing bugs isn't very productive |
| 10:07 | <annevk> | I meant that as advice to you |
| 10:07 | <smaug____> | :) |
| 10:07 | <annevk> | he's not randomly wontfixing, he believes that design is appropriate |
| 10:07 | <annevk> | if you can find several implementors that disagree you can resolve it towards a design you find appropriate |
| 10:25 | <foolip> | boblet, it ought to be in the next stable release, yes |
| 10:26 | <Ms2ger> | AryehGregor, you know why ranges' offsets are signed? |
| 10:29 | <annevk> | are they in browsers? |
| 14:47 | <AryehGregor> | annevk, the charter says the WebApps WG can take on stuff spun off from HTML5 without rechartering, if I read correctly. |
| 14:48 | <AryehGregor> | Ms2ger, I have no idea. Do you mean specifically .startOffset and .endOffset, or also parameters to various methods like setStart()? |
| 14:48 | <AryehGregor> | I can't see how it would be black-box detectable for .startOffset or .endOffset. |
| 14:49 | jgraham | really thinks the WebApps charter should read "any DOM API that two or more browser vendors are interested in implementing" |
| 14:49 | <AryehGregor> | Actually, I don't see how it would be black-box detectable for .setStart() either, unless you have a node with about 2G children or character elements. |
| 14:50 | <AryehGregor> | Because if it were unsigned, a negative number would wrap around to a large positive number, which winds up being INDEX_SIZE_ERR either way. |
| 14:50 | <AryehGregor> | So how about we just make them all unsigned? |
| 14:50 | <AryehGregor> | jgraham, I really think there shouldn't be working groups and charters. :) |
| 14:51 | <jgraham> | Well yes, taht would be fine too |
| 14:52 | <jgraham> | But seems less likely in the short term |
| 14:52 | <AryehGregor> | Sadly. |
| 14:53 | <annevk> | does seem like there needs to be AC review |
| 14:53 | <annevk> | at the very least |
| 14:54 | <annevk> | anyway, all that does not matter that much long term |
| 14:54 | <AryehGregor> | Why not? |
| 14:55 | <annevk> | well it's annoying, but mostly to people who actually have to sit through it |
| 14:55 | <annevk> | it just delays publishing a WD |
| 14:56 | <annevk> | http://www.w3.org/QA/2011/08/subject_from_innovation_to_sta.html |
| 14:57 | <smaug____> | AryehGregor: in which way should the standards be written if not in some kind of WGs |
| 14:57 | <smaug____> | (just curious) |
| 14:57 | <annevk> | community groups have better patent protection (at until REC, which hardly any spec reaches these days) and better licensing... |
| 14:58 | <AryehGregor> | smaug____, in some format where there's no formal organization or membership at all. I mean, you'd want separate mailing lists and Bugzilla components and such, but no actual organization divisions are needed. |
| 14:59 | <AryehGregor> | annevk, but will real specs be accepted as community groups? Worth trying . . . |
| 14:59 | <smaug____> | AryehGregor: might work, or might not |
| 15:00 | <annevk> | AryehGregor, as far as I know moving specs from WGs to CGs is somewhat problematic (though might be possible) |
| 15:00 | <AryehGregor> | smaug____, the WHATWG seems to have worked pretty well so far. We probably wouldn't even have to deal with the W3C at all if not for patent policies. |
| 15:00 | <annevk> | AryehGregor, new specs such as DOM Parsing should be fairly trivial however |
| 15:00 | <smaug____> | AryehGregor: WhatWG is a WG ;) |
| 15:00 | <AryehGregor> | annevk, but what's the point? Is it going to make Apple or Microsoft happier to have it in a community group instead of some random website? If so, okay. |
| 15:01 | <AryehGregor> | I'm game then. |
| 15:01 | <smaug____> | in whatever form the standardization happens, there is always the problem what to do when there are conflicting opinions/interest |
| 15:01 | <AryehGregor> | smaug____, not in the sense I was talking about -- there's no charter or membership or anything like that. |
| 15:01 | <AryehGregor> | If there are conflicting opinions on implementer requirements, implementers can work it out and specs will follow if they're being written sanely, because people want interop. |
| 15:01 | <annevk> | AryehGregor, a) you have more patent protection than when you publish it as W3C WD; b) makes it easier to move it to REC within a WG when finished as I understand it |
| 15:02 | <AryehGregor> | If the implementers can't work it out, like storage mutex or whatever, leave it undefined. |
| 15:02 | <AryehGregor> | None of this chartering stuff is needed. |
| 15:02 | <annevk> | WHATWG has a charter |
| 15:02 | <AryehGregor> | annevk, okay, I'll be sure to run that by everyone. I don't mind having it at the W3C as long as it's in some place where I don't have to deal with the bureaucracy. |
| 15:02 | <annevk> | and has some kind of committee |
| 15:02 | <AryehGregor> | Not in practice. |
| 15:03 | <annevk> | also in practice, just not that visible |
| 15:05 | <AryehGregor> | Not in practice, insofar as no one pays any attention to them and most people who participate heavily in the WHATWG haven't even heard of their existence. |
| 15:05 | <AryehGregor> | If they have any significance, it's as documentation of what we'd all do anyway even if it weren't officially written down anywhere. |
| 15:05 | <Ms2ger> | So the difference is that the WHATWG's committee works in secret and the HTMLWG's in public? :) |
| 15:06 | <annevk> | I meant that we don't interfere much as it's not deemed necessary |
| 15:06 | <AryehGregor> | You'd have about as much say whether or not you were officially part of some committee. |
| 15:07 | <AryehGregor> | The reason you have say is really because you're implementers, not because you're on the steering committee. |
| 15:07 | <annevk> | if you say so |
| 15:07 | <AryehGregor> | When was the last time Hixie did anything he didn't want to do because the steering committee told him to? |
| 15:07 | <AryehGregor> | More to the point, what practical enforcement mechanism is there if the steering committee wants to tell Hixie what to do? |
| 15:08 | <Ms2ger> | Kick him out |
| 15:08 | <AryehGregor> | He owns the domain name, he can do whatever he feels like. At the W3C, the Team holds the cards. |
| 15:08 | <AryehGregor> | Or whatever, the W3C staff. |
| 15:08 | <AryehGregor> | Yeah, right, so we'd have the WHATWG operating without Hixie. I really see that happening. |
| 15:10 | annevk | goes back to work on mutation events |
| 15:10 | <smaug____> | annevk: what are you doing to them? |
| 15:11 | smaug____ | goes back to implement the replacement |
| 15:11 | <annevk> | sorting out the arguments for end of task and return of outermost method |
| 15:11 | <annevk> | and fleshing them out a bit better |
| 15:12 | <annevk> | the end of task arguments are somewhat compelling I think, just not that clear currently |
| 15:14 | <smaug____> | the end of task suffers badly from the case that one would need to be very careful to not do certain modal stuff in the same task as dom mutations |
| 15:14 | <annevk> | is there anything besides showModalDialog? |
| 15:14 | <smaug____> | the spec does have some other case |
| 15:15 | <smaug____> | IIRC |
| 15:15 | <annevk> | the after modification suffers badly from the same problem as the current mutation events, except the problem now becomes that of library authors rather than UA implementors |
| 15:16 | <smaug____> | anyway, it should be trivial to change the current implementation from "outermost method" to "end of task" |
| 15:16 | <smaug____> | though, it is not even clear what kind of API people want |
| 15:16 | <annevk> | yeah, your API would work either way |
| 15:17 | <annevk> | yeah, Rafael had that as open issue (6/7 or so?) but never elaborated |
| 15:17 | <annevk> | I will try to push a bit |
| 15:18 | <smaug____> | so far web devs have managed to work with mutation events quite well. "outermost method" doesn't really make it any worse |
| 15:20 | <smaug____> | annevk: also, the proposed <dialog> would cause similar problems as showModalDialog |
| 15:21 | <smaug____> | hmm, actually, the proposal isn't clear what showModal does |
| 15:51 | <annevk> | smaug____, btw, Rafael says sicking also thinks end of task is better |
| 15:51 | <annevk> | and apparently Indexed DB has such an "end of task" concept already? |
| 15:52 | jgraham | now plans to tell someone that annevk claims that Rafael said that sicking thinks end of task is better |
| 15:53 | <annevk> | just wondering whether smaug____ knows or not |
| 15:54 | <jgraham> | :) |
| 15:55 | Ms2ger | will alert the world that jgraham told someone that... Meh, it's boring already |
| 15:59 | <zcorpan> | it wasn't boring until you ruined it |
| 16:00 | <Ms2ger> | zcorpan, sorry :( |
| 16:01 | <smaug____> | annevk: I do know that |
| 16:01 | <smaug____> | I disagree with sicking |
| 16:01 | <annevk> | what happened to whatwg.org |
| 16:02 | <smaug____> | ? |
| 16:02 | <smaug____> | works here |
| 16:02 | <smaug____> | er, no |
| 16:02 | <smaug____> | not anymore |
| 16:02 | <annevk> | server disappeared? |
| 16:03 | <jgraham> | Gone for me too :( |
| 16:04 | <jgraham> | The server bus factor of web standards work is way too low |
| 16:04 | <jgraham> | I mean as comforting as it is that Hixie has everything backed up in eleventy bajillion places it doesn't help when his host goes down |
| 16:05 | <annevk> | AryehGregor, ECMAScript uses "code unit" and "character" |
| 16:05 | <AryehGregor> | Does it? |
| 16:06 | <AryehGregor> | "The String type is the set of all finite ordered sequences of zero or more 16-bit unsigned integer values (“elements”)." |
| 16:06 | <annevk> | oh only in source text |
| 16:06 | <AryehGregor> | It looks like it uses "code unit" to mean something totally different. |
| 16:06 | <AryehGregor> | Oh, it uses it for multiple things. |
| 16:06 | <AryehGregor> | How confusing. |
| 16:06 | <AryehGregor> | Yeah, looks like only for source text. |
| 16:06 | <annevk> | does element also mean escapes? |
| 16:06 | <annevk> | because you don't want that |
| 16:07 | <annevk> | 'Throughout the rest of this document, the phrase “code unit” and the word “character” will be used to refer to a 16-bit unsigned value used to represent a single 16-bit unit of text.' |
| 16:07 | <annevk> | that seems to be what we want |
| 16:08 | <AryehGregor> | So it looks like Steve Faulkner has put up a clone for me: http://dev.w3.org/html5/editing-api/Overview.html |
| 16:08 | <AryehGregor> | Now, I find this bit very interesting: "Copyright © 2011 W3C© (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply." |
| 16:08 | <AryehGregor> | That strikes me as actively misrepresenting the copyright status of the document. |
| 16:09 | <annevk> | back online |
| 16:31 | <david_carlisle> | AryehGregor: Is the original copyright status consistent? It says copyriight google, but released under CC0 which the CC0 page to which you link has the heading "no copyright" |
| 16:31 | <AryehGregor> | david_carlisle, AFAIK (IANAL), the copyright holder is Google, but by licensing it CC0 all actual rights are waived. Where does it say copyright Google, though? I thought I removed that. |
| 16:32 | <david_carlisle> | er I was looking at this which might not be the right thing |
| 16:32 | <david_carlisle> | http://aryeh.name/gitweb.cgi?p=editing;a=blob;f=LICENSE;h=85cb5c8689f2c59cd6b40e87c7b608b303d09294;hb=HEAD |
| 16:32 | <AryehGregor> | Oh, I missed that. |
| 16:33 | <AryehGregor> | david_carlisle, try now: http://aryeh.name/gitweb.cgi?p=editing;a=blob;f=LICENSE;hb=HEAD |
| 16:33 | <david_carlisle> | AryehGregor: I think publishing as a w3c spec has a w3c copyright as a rerequisite 9although I must adnit it's a while since I read those rules:-) |
| 16:33 | <AryehGregor> | david_carlisle, pubrules require that line to be present. |
| 16:34 | <AryehGregor> | But it's not actually submitted anywhere as REC-track just now. |
| 16:35 | <david_carlisle> | AryehGregor: yes but presumably the only point of copying it to w3c woul dbe to put it on rec trac (so if you were to object to a copyright change or anything else, better to get those things sorted earlier rather than later?0 |
| 16:35 | <AryehGregor> | david_carlisle, well, there are now Community Groups at the W3C. |
| 16:35 | <AryehGregor> | I'll see if people are okay with using those. |
| 16:35 | <AryehGregor> | I mean, it'll have to be REC track eventually if we want the patent policy. |
| 16:35 | <AryehGregor> | But doesn't have to be yet. |
| 16:36 | <david_carlisle> | well could stay in your git hosting until then;-) |
| 16:36 | <AryehGregor> | Except people will fork it if I do that. |
| 16:36 | <AryehGregor> | Which is fair enough, since I basically told them to. :) |
| 16:39 | <zewt> | this is ... odd |
| 16:39 | <Ms2ger> | What? AryehGregor not being openly hostile to the W3C? :) |
| 16:40 | <zewt> | the "quotes" in mark watson's mails show up in a very slightly different color than his text (red vs. black), which I assumed was his mailer being horrible |
| 16:40 | <zewt> | ... but when I view-original-message, there's no HTML part in it at all--is it Gmail somehow doing that? or is "view original" not actually showing the real original data? |
| 16:40 | <AryehGregor> | Ms2ger, well, maybe I am openly hostile, but if people are going to try publishing outdated forks of my spec . . . |
| 16:41 | <Ms2ger> | Can't have that |
| 16:41 | <zewt> | anyone want to tell me what his mails look like in another mailer and let me know the manner in which I'm going crazy? (eg. the last post to the MediaSource thread) |
| 16:43 | <Philip`> | zewt: They look normal colour to me, in Gmail |
| 16:43 | <Philip`> | Does it still look red if you zoom in so the text is larger? |
| 16:43 | <Philip`> | (Maybe it's an artifact of subpixel font rendering or something) |
| 16:44 | <jgraham> | Do you mean quotes from the message he is replying to? |
| 16:44 | <zewt> | https://zewt.org/~glenn/weird.png |
| 16:44 | <jgraham> | I can't tell which is which |
| 16:44 | <zewt> | i have to squint to even tell the difference, but it's there |
| 16:45 | <zewt> | ... but when I "show original", it's just a regular text/plain message |
| 16:46 | <Philip`> | If you mean quote marks then they look normal, if you mean quotations from earlier messages in a purplish colour then Gmail does that by comparing lines of text to lines in previous messages in that conversation |
| 16:46 | <zewt> | that's ... horribly disgustingly evil |
| 16:46 | <zewt> | and with a nearly-indistinguishable color? even worse |
| 16:46 | <Philip`> | The colour difference for quoted text looks clearly distinct to me |
| 16:47 | <zewt> | it's very subtle |
| 16:47 | <jgraham> | Well so is randomly interspersing your content amonst the content you are replying to with no plain text distinguishing marks |
| 16:47 | <Philip`> | Surely it's less evil than displaying the message with no indication of what's a quote and what's a reply? |
| 16:47 | <zewt> | well yeah, i was originally sending him a mail to ask him to quote normally when I was confused by that |
| 16:47 | <jgraham> | I thought only a11y people did that |
| 16:48 | <jgraham> | But it seems I was wrong |
| 16:49 | <dglazkov> | good morning, Whatwg! |
| 16:49 | <zewt> | Philip`: it encourages people to think that people can read messages that are quoted like that, encouraging people like mark to continue quoting in that horrible way |
| 16:50 | <Philip`> | zewt: It doesn't look like it was posted via Gmail, so I would assume the poster isn't going to be influenced by how Gmail renders it |
| 16:50 | <Philip`> | (until Gmail users complain at him) |
| 16:50 | <zewt> | didn't say he was |
| 16:51 | <Philip`> | (and Gmail's colouring will mean a smaller fraction of Gmail users will complain) |
| 16:51 | <Philip`> | (which seems like a pretty indirect form of encouragement) |
| 16:51 | <zewt> | thus proving my point :) |
| 16:51 | <Philip`> | (and likely oughtweighed by the convenience it provides to Gmail users) |
| 16:51 | <Philip`> | (since some people will format emails stupidly regardless of how much you complain) |
| 16:52 | <zewt> | it's not much use to me; as soon as I try to reply to it the questionable distinction is lost (it doesn't transfer to reply quotes in any way) |
| 16:52 | <jgraham> | It appears to be posted from exchange |
| 16:52 | <jgraham> | Which is mildly surprising |
| 16:52 | <jgraham> | I was expecting lotus notes |
| 16:52 | <jgraham> | But only very mildly |
| 16:52 | <Ms2ger> | zewt, my reply is colored green |
| 16:53 | <zewt> | Ms2ger: heh I hate when people do that--but at least they're distinguishing *somehow* |
| 16:53 | <AryehGregor> | I'd actually prefer to use a W3C Community Group than to host this on my website, on reflection, because hopefully it will push the W3C to be less dysfunctional about its process requirements if it sees that people don't mind working there if we don't have to deal with lots of crazy pointless rules. |
| 16:53 | <zewt> | (provided that the receiver sees HTML mail, that he hasn't disabled colors in HTML mail, and that green is readable on whatever his background happens to be) |
| 16:54 | <Philip`> | Green is an environmentally friendly colour, so I always give emails a solid green background before printing them |
| 16:54 | <timeless> | heh |
| 17:06 | <AryehGregor> | Okay, I need four people with W3C accounts to support my new Community Group so it can be approved: http://www.w3.org/community/groups/proposed/ |
| 17:06 | <AryehGregor> | Get to it! |
| 17:06 | <annevk> | oh Firefox 6 is out |
| 17:06 | AryehGregor | waits to see how many minutes it will take |
| 17:07 | <annevk> | does not work in Opera? |
| 17:07 | <zewt> | only difference i've seen in ff6 is ... randomly shuffled menu items breaking a bunch of my menu habits |
| 17:07 | <AryehGregor> | What doesn't, the W3C page? |
| 17:07 | <AryehGregor> | That's amusing. |
| 17:07 | <zewt> | (havn't checked into what API updates they've made yet) |
| 17:08 | <jgraham> | Nope, teh page is broken in Opera |
| 17:08 | <annevk> | AryehGregor, yeah, the big button does not appear |
| 17:08 | <AryehGregor> | lulz. |
| 17:08 | <jgraham> | Gotta love that |
| 17:09 | <jgraham> | AryehGregor: In firefox the links in the description seem to be missing |
| 17:09 | <zcorpan> | w3c hates opera! |
| 17:10 | zcorpan | goes to bbq |
| 17:10 | <Ms2ger> | Two more |
| 17:11 | <annevk> | I cheated by using a different browser |
| 17:14 | <zewt> | wow, ff6 seems much much slower at incrementally decoding big (print resolution) images |
| 17:15 | <Hixie> | the server going down earlier was because of the pdf generation |
| 17:15 | <Hixie> | happens every day these days because the pdf generation is taking too many resources |
| 17:15 | <smaug____> | zewt: really? Please file a bug |
| 17:15 | <Hixie> | i need to disable it really |
| 17:15 | <smaug____> | zewt: also, do you have a testcase? |
| 17:16 | <zewt> | need to reinstall ff5 to re-test first |
| 17:16 | <annevk> | Hixie, that would be better than the server going offline |
| 17:16 | <jgraham> | Oh, look at that, the problem is an HTML parsing issue |
| 17:16 | <annevk> | Hixie, maybe email whatwg⊙wo to ask if anyone wants to volunteer |
| 17:16 | <Philip`> | Hixie: You should make the spec smaller |
| 17:16 | <jgraham> | Also, who the hell uses wordpress to design a site like this |
| 17:16 | <Hixie> | Philip`: :-P |
| 17:16 | <Hixie> | annevk: yeah |
| 17:17 | <AryehGregor> | jgraham, cool. |
| 17:17 | <Philip`> | jgraham: What's wrong with Wordpress for a site like that? |
| 17:17 | <Ms2ger> | ö |
| 17:17 | <Ms2ger> | That page uses header |
| 17:18 | <annevk> | Ms2ger, only TR/ is outdated |
| 17:18 | <jgraham> | Philip`: It seems entirely unlike a blog |
| 17:18 | <jgraham> | Also, did you look at the source? |
| 17:18 | <Philip`> | "The group\'s deliverables" yay escaping |
| 17:18 | <AryehGregor> | We need two more people with a W3C account to signal support here: http://www.w3.org/community/groups/proposed/ |
| 17:18 | AryehGregor | prods |
| 17:18 | <Philip`> | "It will start work with the preliminary specification hosted at <http://aryeh.name/spec/editing/editing.html>"; yay escaping again |
| 17:18 | <Ms2ger> | Hixie, ^ |
| 17:19 | <AryehGregor> | WTF. |
| 17:20 | <Philip`> | Try XSSing it to get people to automatically approve your group as soon as they open the page |
| 17:20 | <jgraham> | <header class="group tMargin header_article"><a href="#" class="h3"><img src="/community/src/img/icon-minus.png" class="icon_plus_minus" width="14" height="14" alt="icon-minus" />HTML Editing APIs</a></header> |
| 17:20 | <jgraham> | Yes, it uses <header> |
| 17:20 | <jgraham> | No, it doesn't really get the point of <header> |
| 17:20 | <smaug____> | AryehGregor: so what does Community Group mean in practice? |
| 17:21 | <AryehGregor> | smaug____, AFAICT, the W3C provides some infrastructure but no Process requirements, and it doesn't produce "official" specs like RECs or anything. |
| 17:21 | <AryehGregor> | smaug____, http://www.w3.org/community/about/faq/ |
| 17:22 | <smaug____> | AryehGregor: and why should editing APIs be there and not in WebApps ? |
| 17:22 | <smaug____> | (Sorry, I haven't followed all the politics ) |
| 17:23 | <AryehGregor> | smaug____, because that way I don't have to deal with the Process, which is nice, because I'm not a masochist. Eventually it will have to be in WebApps for the Patent Policy. |
| 17:23 | <smaug____> | ok |
| 17:26 | <smaug____> | AryehGregor: now you need only one more to click "support" |
| 17:26 | <zewt> | reminds me of petitions, heh |
| 17:27 | <Ms2ger> | zewt, please sign my petition! Or do you *want* to kill puppies? |
| 17:27 | <zewt> | absolutely |
| 17:27 | <smaug____> | "Oil, Gas and Chemicals Business Group " o_O |
| 17:28 | <zewt> | "i got thousands of people to sign a piece of paper! i think one or two of them actually read it" |
| 17:28 | <Ms2ger> | smaug____, surprised me as well |
| 17:31 | <smaug____> | AryehGregor: I hope you'll use webapps or whatwg mailing lists for editing stuff |
| 17:35 | <jgraham> | Why pass up the oppertunity to start a new mailing list? |
| 17:35 | <jgraham> | Everyone knows that N+1 lists are strictly better than N, always |
| 17:36 | <zewt> | shh we'll end up in an infinite loop |
| 17:36 | <Ms2ger> | N+2* |
| 17:36 | <AryehGregor> | smaug____, I intend to, yeah. |
| 17:37 | <AryehGregor> | Likewise for wikis etc. |
| 17:37 | <Ms2ger> | Uh |
| 17:37 | <Ms2ger> | N+4* |
| 17:37 | <Ms2ger> | "Each group has four mailing lists by default, two public and two non-public." |
| 17:37 | <AryehGregor> | . . . |
| 17:38 | <jgraham> | See. The only way that could be improved is if they gave you 5 lists by default |
| 17:39 | <Ms2ger> | And CGs must use the public lists for technical stuff, Business Groups don't |
| 17:42 | <annevk> | from what I heard you can contact ij and get alternative setups |
| 17:42 | <annevk> | e.g. use an existing mailing list or repository |
| 17:43 | <annevk> | or bug tracker etc. |
| 17:43 | <annevk> | at the moment however that requires manual setup |
| 17:46 | <AryehGregor> | We still need one more supporter. |
| 17:48 | <nimbu> | foolip: Is this true "And: Unfortunately Opera still lack a very important feature in their HTML5 video spec implementation, which is the Buffer API." ? |
| 17:48 | <Ms2ger> | nimbu, surely you have a W3C account |
| 17:49 | <nimbu> | Ms2ger: I do >_> |
| 17:49 | <Ms2ger> | Want to click a button on http://www.w3.org/community/groups/proposed/? |
| 17:50 | <timeless> | AryehGregor: what is `as (1) te contenteditable ` ? |
| 17:50 | <AryehGregor> | timeless, a typo, possibly my fault and possibly not. |
| 17:50 | <AryehGregor> | (they reformatted it) |
| 17:51 | <timeless> | AryehGregor: if you fix it, you can have my vote:) |
| 17:51 | <nimbu> | what button Ms2ger |
| 17:52 | <Ms2ger> | The one you get to see after you click "HTML Editing APIs", if timeless doesn't beat you to it |
| 17:52 | <annevk> | Ms2ger, sounds like you need to find an XSS exploit lol |
| 17:52 | <AryehGregor> | timeless, Ian fixed it. |
| 17:52 | <Ms2ger> | Heh |
| 17:52 | <AryehGregor> | Ian Jacobs, that is. |
| 17:52 | <timeless> | > This group is no longer proposed, it has been |
| 17:52 | <timeless> | it has been what? |
| 17:52 | <annevk> | "oh come on, just log in and click the button, you'll get a cookie" |
| 17:53 | <timeless> | and i can't click the report a bug link |
| 17:53 | <timeless> | because the error page doesn't have it! |
| 17:53 | <timeless> | <h3> Errors </h3> <ul> <li>This group is no longer proposed, it has been </li> </ul> |
| 17:53 | <annevk> | it's a group |
| 17:53 | <annevk> | http://www.w3.org/community/editing/ |
| 17:53 | <timeless> | it has been... what? |
| 17:53 | <Ms2ger> | mailto:team-community-process⊙wo?Subject=Problem reported for editing |
| 17:54 | <Philip`> | It's a has been |
| 17:55 | <timeless> | oh cute |
| 17:55 | <timeless> | the group was on the list of /proposed/ with the error for when i tried to vote for it |
| 17:56 | <timeless> | but when i tried to vote for it *again*, the error appeared and the group did not reappear |
| 17:56 | timeless | goes to hunt lunch |
| 17:56 | <Ms2ger> | Heh |
| 17:57 | <Ms2ger> | AryehGregor, joined your own IRC channel already? :) |
| 17:57 | <AryehGregor> | We don't want our own IRC channel. |
| 17:59 | <AryehGregor> | I'm sad that the functional methods like .filter and such return arrays instead of iterators. |
| 17:59 | <AryehGregor> | It makes things gratuitously inefficient when you chain them, like .filter(...).every(...). |
| 18:01 | <gsnedders> | AryehGregor: Well, there aren't iterators in ES, so that's be hard. |
| 18:01 | <AryehGregor> | That's a potential issue, I grant. |
| 18:01 | <AryehGregor> | There should be, they're totally awesome. |
| 18:01 | <AryehGregor> | One of my favorite things in Python. |
| 18:01 | <gsnedders> | AryehGregor: Could still have lazily evaluated arrays, though. |
| 18:01 | <gsnedders> | So use thunks for filters and the like applied to an array |
| 18:02 | <gsnedders> | Somewhat evil, but would be a perf gain when stuff is chained |
| 19:11 | <timeless> | anyone here familiar w/ <video> ? |
| 19:12 | <timeless> | assuming someone had a <source> which was magical, i presume there's a way for a JS associated to a <video> to discover that the <video> has reached the end of the [stream] |
| 19:13 | <timeless> | is there also a way to discover if the <video> is dropping frames? |
| 19:14 | <timeless> | it looks like there's onstalled |
| 19:14 | <timeless> | and onwaiting |
| 19:14 | <timeless> | and onemptied |
| 19:14 | timeless | sighs |
| 19:14 | <timeless> | too many events |
| 19:19 | <timeless> | ok, so onstalled generally covers one half of the problem |
| 19:20 | <timeless> | > This specification doesn't define how the user agent achieves the appropriate playback rate |
| 19:21 | <timeless> | so, there isn't actually a way to find out if the player is dropping frames |
| 19:21 | <timeless> | hrm, this consumer has a requirement to know roughly that |
| 19:21 | <timeless> | (not precisely that, but roughly that) |
| 19:21 | <timeless> | (The consumer is trying to [in JS] automatically select the right content bitrate [instead of letting the browser negotiate for it]) |
| 19:22 | <jamesr> | mozilla had a vendor-prefixed way to collect more stats |
| 19:22 | <jamesr> | like frames decoded, frames presented, etc |
| 19:22 | <timeless> | yeah |
| 19:22 | <timeless> | i'll mention that |
| 19:22 | <timeless> | i'm not sure i really want to encourage this |
| 19:22 | <timeless> | i'll pastebin my proposal at some point and ask for feedback before i send it out |
| 19:23 | <timeless> | [mozBug 580531] |
| 19:23 | <timeless> | .mozDroppedFrames |
| 20:38 | <zcorpan> | annevk: "DOM4" is not a great name from a google search result standpoint either |
| 20:39 | <zcorpan> | (unless SafeSearch is on strict) |
| 20:41 | <nimbu> | ROFLZ |
| 20:42 | zcorpan | is pleased to see several instances of DOM cleanup in firefox 6 release notes |
| 20:43 | <Ms2ger> | Try guessing how many of these were mine :) |
| 20:44 | <zcorpan> | all of them? |
| 20:44 | <micheil> | hey, in the WebSockets specification / draft, where is the MessageEvent type defined? |
| 20:44 | <zcorpan> | micheil: it's defined in the html spec |
| 20:44 | <micheil> | okay... |
| 20:45 | <micheil> | is this the comms spec? |
| 20:45 | <Ms2ger> | whatwg.org/C/#messageevent |
| 20:45 | <micheil> | http://www.w3.org/TR/2008/WD-html5-20080610/comms.html |
| 20:45 | <zcorpan> | what Ms2ger said |
| 20:45 | <Hixie> | http://www.whatwg.org/specs/web-apps/current-work/complete.html#event-definitions-1 |
| 20:45 | <Ms2ger> | You certainly don't want to be looking at a 3 years old spec |
| 20:45 | <Hixie> | TR/ page strikes again |
| 20:45 | <Hixie> | good lord |
| 20:46 | <micheil> | okay |
| 20:46 | <micheil> | well, I'm just basing some new work so it's a familiar API to those using websockets in the browser |
| 20:46 | <micheil> | hence the reason I ask about MessageEvent, which is what the WebSocket object uses on message |
| 20:47 | <zcorpan> | micheil: read the whatwg.org/C version, it contains websockets and messageevent and has working xrefs |
| 20:47 | <zcorpan> | and it's up-to-date |
| 20:47 | <micheil> | is there any plan to extend MessageEvent to include a data type? |
| 20:47 | <Hixie> | data type? |
| 20:48 | <micheil> | yeah |
| 20:48 | <micheil> | so you don't need to do a typeof check |
| 20:49 | <Hixie> | ...what's wrong with typeof? |
| 20:49 | <Ms2ger> | Well, it's annoying from C++ |
| 20:49 | <micheil> | it's not exactly the best thing |
| 20:49 | <Ms2ger> | Why? |
| 20:50 | <Hixie> | i agree that it's not the best thing |
| 20:50 | <Hixie> | the best thing, is, like, a cat riding a model train or something |
| 20:50 | <Hixie> | but i don't see how that would help here |
| 20:50 | <micheil> | because, this project is a node.js project, so I wouldn't be using "blob", but rather "buffer" |
| 20:51 | <micheil> | I mean, we already know the type, no need to hide it from view |
| 20:51 | <micheil> | or obscure it |
| 20:51 | <Ms2ger> | Hixie, pics or it didn't happen ;) |
| 20:51 | <Hixie> | if you already have a library around this, just make it expose the type however you want it to expose it |
| 20:51 | <micheil> | okay |
| 20:52 | <micheil> | I like to stay close to standards if possible. |
| 20:52 | <micheil> | but that's cool, thanks for pointing me in the right direction. |
| 20:52 | <Hixie> | you can also still use typeof with whatever type you're actually using |
| 20:52 | <Hixie> | if it's been wrapped |
| 20:53 | <Ms2ger> | Microsoft about IndexedDB: "... so we can start getting some adoption on this technology." |
| 20:53 | jgraham | doesn't even see safesearch on google anymore (and just gets DOM4 when searching for DOM4) |
| 20:53 | <jgraham> | Also, instant breaks inline search |
| 20:53 | <Ms2ger> | I got shepazu's DOM4 |
| 20:53 | <timeless> | inline? |
| 20:54 | <shepazu> | hmmm? |
| 20:54 | <jgraham> | the type you get pressing / |
| 20:54 | <shepazu> | I don't remember uploading my draft of DOM4... |
| 20:54 | <shepazu> | but maybe I did |
| 20:55 | <Ms2ger> | You didn't hear Google now searches your local disk as well? :) |
| 20:55 | <jgraham> | Ms2ger: Oh, so did I. Having meaningless years in the URL is helpful in to noticing that there is anything wrong |
| 20:55 | <Ms2ger> | http://dev.w3.org/2006/webapi/DOM4Core/DOM4Core.html |
| 20:55 | <timeless> | jgraham: FAYT :) |
| 20:56 | jgraham | just rejects anything contating /TR/ and tries not to think too hard about the numbers |
| 20:56 | <shepazu> | Ms2ger: oh, that was a very early rough draft |
| 20:56 | <timeless> | shepazu: the best kind! |
| 20:56 | <AryehGregor> | Could we start a wiki page documenting cases where people were confused by /TR/? |
| 20:56 | <Ms2ger> | Won't argue with that ;) |
| 20:56 | jgraham | wonders what safesearch has o do with it |
| 20:56 | <AryehGregor> | As evidence, you know. |
| 20:57 | <zcorpan> | wait, i was editor for that? |
| 20:57 | <jgraham> | Does that block unfinished DOM drafts? |
| 20:57 | zcorpan | didn't know |
| 20:57 | <jgraham> | Maybe it blocks all non-TR content! |
| 20:57 | <jgraham> | Google protecting us from material of questionable stability |
| 20:57 | <Ms2ger> | I was going to share DOM Core, but Google doesn't like my name |
| 20:58 | <shepazu> | zcorpan: you and I talked about you editing "Web DOM" at W3C, which is why (I think) I started that draft |
| 20:58 | <Ms2ger> | Or "+1" it, what the cool kids do these days |
| 20:58 | <zcorpan> | shepazu: ah |
| 20:58 | <shepazu> | no, Ms2ger, +1 is evil! |
| 20:58 | <timeless> | Ms2ger: google killed my name |
| 20:58 | <Ms2ger> | I heard |
| 20:59 | <shepazu> | zcorpan: but we never closed the loop on it, and now others have picked it up, which I'm happy with |
| 20:59 | <Ms2ger> | shepazu, less work for you! ;) |
| 20:59 | <zcorpan> | so am i |
| 20:59 | <shepazu> | Ms2ger: precisely |
| 21:00 | <shepazu> | and now it looks like the DOM extensions I proposed for SVG may make it in as well, with convenience methods like .create() with property bags |
| 21:00 | <shepazu> | so, I'm happy |
| 21:00 | <zcorpan> | wonder why my email didn't make it to help@ archives. maybe i sent from the wrong address |
| 21:01 | <shepazu> | AryehGregor: nice work on the editing spec… I've only skimmed it, but I like what I see |
| 21:01 | <AryehGregor> | shepazu, thanks. |
| 21:01 | <smaug____> | timeless: Google did what to your name? |
| 21:02 | <timeless> | smaug____: they didn't believe that `timeless developer` satisfied their `real name` policy |
| 21:02 | <shepazu> | AryehGregor: for v2, it would be interesting to consider adding an SVG/graphics editing API into that |
| 21:02 | <timeless> | i claim that `timeless` should satisfy their `common name` requirement |
| 21:02 | <smaug____> | um |
| 21:02 | <timeless> | given that i've used it in real life for more than half my life |
| 21:02 | <timeless> | (and certainly my entire professional life) |
| 21:02 | <timeless> | unfortunately the stupid system insisted that i provide 2 names (first, last), so i had to pick a second part |
| 21:02 | <AryehGregor> | shepazu, that sounds like a different project, really. Graphics editing is a whole separate thing from rich text editing. Obviously it would be a useful addition to the web, of course. |
| 21:02 | <timeless> | i had business cards with `timeless developer` |
| 21:03 | <AryehGregor> | timeless, send them scans of the business cards and other documentation? |
| 21:03 | <shepazu> | a few months ago, I couldn't recall timeless' "real" name and had to ask him :) I know him almost exclusively as timeless |
| 21:03 | <smaug____> | timeless: or just give up with G+ ;) |
| 21:03 | <timeless> | shepazu: the majority of mozilla people do too |
| 21:03 | <timeless> | (know me almost exclusively as) |
| 21:03 | <shepazu> | you gotta admit, though, timeless… it's a little uppity for a name :) |
| 21:04 | timeless | shrugs |
| 21:04 | <timeless> | i've used it since around '94 or '95 ... |
| 21:04 | shepazu | contemplates changing nick to "teh_awesome" :P |
| 21:04 | <jgraham> | Not more so than chastity |
| 21:04 | <jgraham> | Or something |
| 21:04 | <jgraham> | Well maybe that is the opposite |
| 21:05 | <jgraham> | But still a pretty silly "real" name |
| 21:05 | <annevk> | zcorpan, that's because we aren't using it yet |
| 21:05 | <annevk> | zcorpan, DOM4 that is |
| 21:05 | <Ms2ger> | shepazu, do you have a real name? |
| 21:06 | <smaug____> | time to close some tabs. 400+ is getting hard to manage |
| 21:06 | <timeless> | heh |
| 21:06 | <timeless> | panorama isn't helping? |
| 21:06 | <shepazu> | Ms2ger: I have the name my parents gave me, though I don't really care for it |
| 21:07 | <timeless> | AryehGregor: i didn't seee any useful place to do anything about it |
| 21:07 | <AryehGregor> | timeless, unsurprising. Google doesn't seem to like dealing with user feedback. |
| 21:07 | <smaug____> | well, 400 is enough that panorama just puts them over each others |
| 21:07 | <AryehGregor> | (in general) |
| 21:07 | <timeless> | AryehGregor: anyway |
| 21:07 | <timeless> | yeah well |
| 21:07 | <timeless> | they aren't alone |
| 21:07 | <shepazu> | AryehGregor: yeah, I could see that being a separate API, though there will be overlap in the text editing |
| 21:07 | <timeless> | i've had pretty bad luck dealing w/ various groups |
| 21:07 | <timeless> | which reminds me |
| 21:07 | <AryehGregor> | Why don't you legally change your name? |
| 21:07 | <timeless> | ... time to call Chase again and yell at them... again |
| 21:07 | <timeless> | heh |
| 21:08 | <timeless> | that'd probably mess up my immigration status here |
| 21:08 | <zewt> | panorama seems pretty useless |
| 21:08 | <zewt> | thumbnails of webpages aren't helpful at all |
| 21:08 | <timeless> | i can't even leave ontario for more than 30 days between when i arrived and some day in december |
| 21:09 | <smaug____> | panorama works quite well if you have something like <50 tabs per group |
| 21:09 | <timeless> | zewt: i basically have 7 windows |
| 21:09 | shepazu | always liked names like "Capability Brown" and the Puritan "virtue names" like Temperance, Lamentation, Redeemed, Be-faithful, The-peace-of-God, etc. |
| 21:10 | <timeless> | one of those windows has 4 groups |
| 21:10 | <timeless> | `current work`, `<employer>`, `accessibility`, `w3 todo` |
| 21:11 | <timeless> | one of those groups is empty, two have 2 items, todo has 7 |
| 21:12 | <annevk> | 400 tabs? wow |
| 21:12 | <annevk> | and my friends think I'm crazy with about thirty |
| 21:12 | <timeless> | another window has 5 tabs (in a single group) |
| 21:12 | <zewt> | i don't find it useful, i don't know what use thumbnails of windows filled with text is supposed to be |
| 21:12 | shepazu | once had almost 1000 |
| 21:12 | <timeless> | in my case, i don't need the thumbnails |
| 21:12 | <timeless> | i need the document titles |
| 21:12 | <zcorpan> | annevk: 400 is nothing for bratell |
| 21:12 | <timeless> | `the web platform: bro...` `world wide web cons...` `widget packaging and...` |
| 21:13 | <zewt> | i wish the address bar completion was faster, which would make searching for tabs by title more useful |
| 21:13 | <timeless> | `w3c news archive: 20...` `the network informati...` `deviceorientation eve...` |
| 21:13 | <zewt> | but even with the completion delay set to 0 there's an ugly delay between typing and completion |
| 21:13 | <annevk> | zcorpan, damn it, and he already was the better man |
| 21:13 | <timeless> | i only have one duplicate in that set of 7 |
| 21:13 | <zewt> | generally i just remember where tabs are in each window, in practice |
| 21:13 | <annevk> | I tried joining the Editing group btw |
| 21:13 | <annevk> | seems that request is now redirected to Charles |
| 21:13 | <timeless> | amusingly, the duplicate is in fact a duplicate (two views of the w3 home page!) |
| 21:14 | <timeless> | annevk: requires AC Rep approval? |
| 21:14 | <annevk> | yes because of patent commitments |
| 21:14 | <timeless> | joy |
| 21:14 | <annevk> | it's kind of interesting that you can vouch for a group without AC approval but joining it requires AC approval |
| 21:14 | <annevk> | it makes sense that joining it requires that though |
| 21:14 | <timeless> | yeah, that seems slightly flawed |
| 21:14 | <annevk> | given the patent policy |
| 21:15 | <timeless> | yeah, that part seems right |
| 21:15 | <annevk> | which until you get to REC is a lot better than what every other WD has |
| 21:15 | <timeless> | zewt: anyway, in my case, the previews of the w3 todo items are actually pretty good / usable |
| 21:15 | <annevk> | so hopefully the W3C will move normal groups to that as well |
| 21:15 | <timeless> | annevk: wait |
| 21:15 | <timeless> | CGs require patent grants on current work? |
| 21:16 | <timeless> | as opposed to WGs which only apply the grants to REC achieved work? |
| 21:16 | <AryehGregor> | Only for your actual contributions. |
| 21:16 | <AryehGregor> | IIUC. |
| 21:16 | <annevk> | timeless, yes |
| 21:19 | <shepazu> | timeless: only for those contributions that go on to Rec track, I think… but you make the commitment up front, as opposed to waiting until Rec (IIRC) |
| 21:35 | <annevk> | guess I should read up again on what patent policy protection you get |
| 21:40 | <paul_irish_> | who is a good contact at MSFT for webforms ? |
| 21:41 | <timeless> | annevk / shepazu : is it unreasonable for me to expect that protection to be clearly linked from the /pending/ page ? |
| 21:42 | <shepazu> | timeless: not sure what you mean... |
| 21:43 | <timeless> | shepazu: well, there's clearly a patent policy which affects CGs |
| 21:43 | <annevk> | paul_irish_, maybe Adrian? |
| 21:43 | <shepazu> | timeless: yes… it's linked from the FAQ |
| 21:43 | <paul_irish_> | thanks annevk |
| 21:43 | <annevk> | paul_irish_, actually, maybe Eliot Graff |
| 21:44 | <annevk> | I think he's on the HTML WG at least |
| 21:44 | <timeless> | shepazu: is it linked from http://www.w3.org/community/groups/proposed/ ? |
| 21:44 | <shepazu> | timeless: doesn't look like it |
| 21:44 | <timeless> | what about from http://www.w3.org/community/groups/ ? |
| 21:45 | <timeless> | sorry, since i haven't seen/found the page, i'm listing the pages where i'd have needed to see that link |
| 21:45 | <timeless> | i think there are only 3 |
| 21:45 | <timeless> | those two plus the actual groups themselves |
| 21:45 | <shepazu> | it's at least on the "About" tab, and every time you say "Join" |
| 21:46 | <timeless> | http://www.w3.org/community/editing/ has a link to W3C Community Contributor License Agreement (CLA). -- http://www.w3.org/community/about/agreements/cla/ |
| 21:46 | <timeless> | which isn't a terrible place for it |
| 21:46 | <timeless> | but i claim it's one page too late on average |
| 21:47 | <timeless> | if it could be added to those two other pages, i think that'd be beneficial to some people |
| 21:47 | <shepazu> | timeless: file a bug |
| 21:47 | <timeless> | "how" :) |
| 21:47 | timeless | is actually in the middle of filing an internal bug (and has already filed one w3 bug today about CG) |
| 21:48 | <annevk> | why did I start a conversation on public-html-xml again while hsivonen is away |
| 21:49 | <annevk> | now I need to actually follow up myself :( |
| 21:49 | <timeless> | heh |
| 21:49 | <timeless> | yeah, definitely a bad idea |
| 21:55 | <zcorpan> | nobody implements css3 marquee right? |
| 21:55 | <shepazu> | timeless: Ian has updated the FAQ about how to report bugs… also see http://www.w3.org/community/about/tool/ |
| 21:56 | <annevk> | zcorpan, don't think so |
| 21:56 | <annevk> | zcorpan, was there -wap-marquee or some such as well? |
| 21:56 | <annevk> | zcorpan, we might have that |
| 22:04 | <annevk> | david_carlisle, if you can rewrite the HTML parsing algorithm into something schema / functional; I'd be impressed |
| 22:04 | <annevk> | david_carlisle, I don't think it has much to do with politics |
| 22:05 | <annevk> | david_carlisle, the basic algorithm is already nigh-on impossible I believe, and then document.write() comes on top of that |
| 22:06 | <david_carlisle> | annevk: if I rules the world (which is false for political reasons) i'd do away with document.write and any other inconveniences |
| 22:07 | <annevk> | an interesting way to defend your argument |
| 22:07 | <david_carlisle> | annevk: maybe my argument wasn't so clear (for others on irc, this has leaked from public-html-xml_ |
| 22:07 | <timeless> | david_carlisle =~ s/rules/ruled/ |
| 22:07 | <annevk> | but I'm not sure it holds, you didn't really say it involved making changes |
| 22:08 | <gsnedders> | david_carlisle: And then leave document.write etc. undefined? |
| 22:08 | <david_carlisle> | timeless: you clearly don't follow xslt-list (otherwise you'd give up correcting my typos0 |
| 22:09 | <timeless> | s/0/)/ -- and yes, clearly |
| 22:09 | <timeless> | as a matter of fact, i don't have any love for xslt :) |
| 22:09 | <annevk> | you might be one of the few WHATWG regulars that follows xslt-list :) |
| 22:09 | <david_carlisle> | annevk: I account for around a third of the traffic on that list last time I looked |
| 22:10 | <timeless> | but note that i didn't correct rules to ruled as a typo, but as a grammar-o |
| 22:11 | <timeless> | on irc i'm less likely to correct typos |
| 22:11 | <timeless> | i am impressed that you can mistype ) as both 0 and _ fwiw :) |
| 22:12 | <david_carlisle> | timeless: my usual metric is to try to be within one key with the right hand and two with the left, |
| 22:13 | Philip` | wrote (some of) an HTML5 parser is OCaml, and wonders if that counts as "functional" :-) |
| 22:14 | <timeless> | does anyone use it? |
| 22:14 | <timeless> | if not, i'd call it non-functional :) |
| 22:14 | <david_carlisle> | annevk: but I didn't say that i could make html parsing schema driven, just that it would have been nicer to do that in some other legacy free world, which is more or less what you said in your reply to John, that leniemt xml parsing can be simpler because ther eis less legacy |
| 22:15 | <Philip`> | timeless: I used it to generate interesting tokeniser test cases that are now part of the html5lib test suite, so it's very indirectly still used :-) |
| 22:16 | <timeless> | i don't count that :) |
| 22:16 | <timeless> | s/do/would/ |
| 22:17 | <annevk> | My name is mentioned in http://www.w3.org/TR/SVG11/ but I forgot what I contributed :( |
| 22:17 | <timeless> | heh |
| 22:17 | <annevk> | Congratulations nonetheless, shepazu & posse |
| 22:17 | <heycam> | oh right, I forgot that was being published today |
| 22:18 | <annevk> | heycam, it's on TR/ man, old news :p |
| 22:18 | <heycam> | heh |
| 22:18 | <timeless> | ooh, i'm in http://www.w3.org/TR/2008/PR-ElementTraversal-20081117/ |
| 22:18 | <heycam> | TR/ has one thing going for it -- it's 5 billion times faster than dev.w3.org |
| 22:18 | <shepazu> | annevk: thanks |
| 22:19 | <timeless> | heycam: heh |
