| 00:04 | <Hixie> | jgraham: your argument for 2 sounds correct |
| 00:05 | <jgraham> | Hixie: Thanks |
| 00:05 | <Hixie> | jgraham: in general though so long as you have at least 1 when there is at least 1, and 0 when there aren't any, you're pretty much ok |
| 00:05 | <Hixie> | so i wouldn't focus on this unless you're out of other bugs :-) |
| 00:05 | jgraham | wishes html5lib didn't record parse error |
| 00:06 | <jgraham> | Hixie: The problem is working out why our testcases are failing. Sometimes getting the wrong number of parse errors is useful information like "you haven't implemented the RCDATA parsing algorithm properly yet" |
| 00:06 | <annevk> | I never realized, http://www.w3.org/TR/css3-layout/ also contains flexbox |
| 00:07 | <Hixie> | jgraham: yeah |
| 00:07 | <annevk> | (not defined in detail or anything though) |
| 00:07 | <Philip`> | That kind of boolean test for parse errors is unhelpful if there aren't test cases for each possible parse error in isolation |
| 00:08 | <jgraham> | Philip`: Patches welcome ;) |
| 00:08 | <Philip`> | and I think there aren't tests for each parse error in isolation now, so you have to count the errors to make sure you're not missing some |
| 00:08 | <Hixie> | yeah |
| 00:08 | <Hixie> | i'm not saying it shouldn't be tested for |
| 00:08 | <Hixie> | i'm just saying it's no the highest priority |
| 00:08 | <Hixie> | in particular, excessive errors aren't a big deal |
| 00:09 | <Hixie> | so long as you return 0 when there are 0 |
| 00:09 | Hixie | has gotten as far as June 4th 2006 in his replying to e-mails about mathml |
| 00:10 | <annevk> | lucky you, the last 250-300 were from last month... |
| 00:10 | <Hixie> | 12 of 620 |
| 00:10 | <jgraham> | Hixie: When did you start |
| 00:10 | <jgraham> | ? |
| 00:11 | <Hixie> | a few hours ago |
| 00:11 | <Hixie> | (i wrote a long summary first) |
| 00:12 | <annevk> | defining error handling for MathML in HTML5 makes no sense... |
| 00:13 | <jgraham> | So I reckon you have about a week (620/12 * 3/24) of no-sleep continuous work ahead replying to these emails. But maybe linear extrapolation is bad ;) |
| 00:20 | <annevk> | there should be some root function in there probably |
| 00:22 | <annevk> | Hixie, we're keeping <![cdata[ and "change" <script> parsing inside <svg> / <math>? |
| 00:27 | <Hixie> | annevk: according to one of these e-mails, the host language is the one that has to define the error handling. so... |
| 00:27 | <Hixie> | annevk: i haven't worked out what to do about cdata yet |
| 00:28 | <Hixie> | annevk: i'd need to pretty substantially reinstrument my parser to get the necessary information |
| 00:28 | <Hixie> | annevk: so far, though, i have seen little enough data that i think it might be a non-issue in practice |
| 00:28 | <Hixie> | at least compared to the issue of <svg> elements all over the web suddenly insertion white blobs into documents |
| 00:30 | <Hixie> | this folder originally had over 33000 lines of e-mail |
| 00:30 | <annevk> | For new authors it seems confusing that the two <script> elements are completely different, but I guess that goes for <a> and <textarea> too... |
| 00:31 | <annevk> | As for the MathML error handling, you'd hope the same error handling would be applied in standalone MathML, HTML, SVG, etc. Maybe something to convince the MathML WG about in due course :) |
| 00:37 | <Hixie> | authors are going to find a lot of this new stuff confusing |
| 00:39 | <annevk> | i guess the question is whether "compat" with current tools or long term "consistency" is preferable |
| 00:44 | <Hixie> | consistency if definitely preferable |
| 00:44 | <Hixie> | compat is, however, necessary |
| 01:06 | <Hixie> | there is a direct correlation between people whose e-mails are hard to read (badly wrapped, bad line spacing, bad language) and people whose input is of little use (rambling, inaccurate, ranting) |
| 01:10 | <Philip`> | A statistically significant correlation? :-) |
| 01:11 | <MikeSmith> | Hixie: could graph usefulness against User-Agent or X-Mailer header of messages |
| 01:13 | <Philip`> | Look for "-- "-delimited signatures as another potential indicator |
| 01:19 | <jwalden> | of clue or not? |
| 01:27 | <MikeSmith> | User-Agent in form "Mutt 1.5.14r5360+poontang (2008-03-11 17:20:48+09:00)" probably good indication of least clue |
| 01:45 | <Hixie> | 6% complete |
| 01:47 | <Philip`> | Hmm, Googlebot seems to be following URLs from my XHR JavaScript code |
| 01:49 | <Philip`> | and they're relative ones, so it's not just picking up http://... |
| 01:50 | <othermaciej> | maybe it's achieved sentience |
| 01:50 | <Philip`> | so either it's being very stupid and trying to resolve every string like "/.../..." as a URL, or it's being very clever and understanding JavaScript, or I've accidentally got normal links to that page (but I'm fairly sure I haven't) |
| 01:52 | Philip` | changes his server code to require the POST parameter, to foil Googlebot |
| 01:52 | <Hixie> | did you have side-effects on GET? |
| 01:52 | <Philip`> | Of course |
| 01:53 | <Hixie> | naughty naughty! :-) |
| 01:53 | <Philip`> | although all it did was log the fact that someone had clicked a button |
| 01:53 | <Philip`> | so the result is just that the log is full of Googlebots |
| 01:54 | <Hixie> | good times |
| 01:54 | <Hixie> | usually when a secret link gets into google, it's because some site somewhere had public logs that included the uri of its referers and the hidden page linked to that site |
| 01:57 | <Philip`> | This hidden page doesn't link anywhere (it simply returns the text "OK"), and there's a dozen of them and Googlebot has found them all, and nobody visits this site anyway |
| 01:59 | <takkaria> | Philip`: you don't have to be /very/ clever to understand JS, just run a parser over anything marked as JS |
| 01:59 | <jruderman> | nobody visits the site? |
| 02:01 | <Philip`> | Unrelatedly: Googlebot doesn't understand xml:base |
| 02:01 | <Philip`> | or it doesn't understand XHTML at all and thinks it's HTML |
| 02:02 | <Philip`> | because I'm getting lots of 404s from xml:based relative URLs in http://canvex.lazyilluminati.com/misc/imgmaps.xhtml |
| 02:03 | <Hixie> | last i checked our xhtml support consisted of pretending it was text/html |
| 02:04 | <Philip`> | That would quite possibly explain it |
| 02:04 | <jruderman> | google's https support sucks too |
| 02:04 | <jruderman> | it keeps sending me to sites with bogus certs |
| 02:05 | Philip` | tries a test to determine whether Googlebot really is following XHR requests |
| 02:05 | <Philip`> | Someone please remind me in a few weeks to check my logs and see what happened :-) |
| 02:07 | <Hixie> | how did you test it? |
| 02:08 | Hixie | lets the google sentience know that it should try to confuse philip some more |
| 02:08 | <Philip`> | I'm just trying to write some scripts that are like the one that Googlebot appeared to follow, to see whether I'm just imagining things or if it's real, and where its limits are :-) |
| 02:09 | <Hixie> | ah |
| 02:17 | <Hixie> | i have reached the ninth of june! |
| 02:17 | <Philip`> | Which ninth of June? |
| 02:17 | <Hixie> | 2006 still |
| 02:17 | <Hixie> | i'm down to 27,000 lines |
| 02:18 | <Hixie> | i start at above 33,000 |
| 02:49 | <dglazkov> | Hixie? |
| 03:01 | <Hixie> | dglazkov: yo |
| 03:21 | <Hixie> | 10th of june! |
| 03:24 | <dglazkov> | good! |
| 03:24 | <dglazkov> | what? |
| 03:25 | <dglazkov> | Hixie? |
| 03:25 | <dglazkov> | We're like ships in the fog |
| 03:26 | <Hixie> | i'm responding to math e-mails |
| 03:26 | <Hixie> | i got to the e-mails from the 10th of june 2006 |
| 03:29 | <Hixie> | ooh, the thread must have died down at that point |
| 03:29 | <Hixie> | 16th of june |
| 03:30 | <dglazkov> | cool |
| 03:30 | <G0k> | only 22 months |
| 03:30 | <dglazkov> | can you explain why nokia folks post about SQL spec on public-html while the rest of us post on whatwg? |
| 03:30 | <dglazkov> | is there some political tension that I am unable to detect? |
| 03:31 | <Hixie> | not everyone is subscribed to both lists |
| 03:31 | <Hixie> | how people pick one over the other, i dunno |
| 03:31 | <Hixie> | i don't pay much attention to which list is which |
| 03:31 | <dglazkov> | ok, different question. Is this somewhere in your pile: http://lists.w3.org/Archives/Public/public-html/2008Feb/0401.html? |
| 03:32 | <Hixie> | except that i guarantee that i will reply to feedback on the whatwg list, and don't guarantee that i'll reply to feedback on the public-html list |
| 03:33 | <Hixie> | yes, third from the bottom in http://www.whatwg.org/issues/#sql |
| 03:34 | <dglazkov> | do I still have time for another question? ;) |
| 03:34 | <Hixie> | sure |
| 03:34 | <Hixie> | you can ask as many as you like :-) |
| 03:34 | <dglazkov> | why changeVersion is modeled after transaction()? Why not just have a setVersion on tx object? |
| 03:36 | <Hixie> | the idea is to let you safely make changes to the schema when you change the version |
| 03:36 | <Hixie> | so that the database is never in an in-between state |
| 03:36 | <Hixie> | it's either version X with the old schema, or version X+1 with the new schema. |
| 03:38 | <dglazkov> | so, even though the transaction assures atomic version change, you want a more explicitly designed interface? |
| 03:39 | <Hixie> | oh you would have had a "set version" method that you could call from within a transaction only? |
| 03:39 | <dglazkov> | right -- this is not my idea, btw |
| 03:39 | <dglazkov> | aa had asked me |
| 03:40 | <dglazkov> | and I went to the source |
| 03:40 | <Hixie> | i guess it could be done that way... seems more brittle though |
| 03:40 | <Hixie> | what's the advantage of the other way? |
| 03:41 | <dglazkov> | I think the advantage is that it's the same transaction() for everything |
| 03:41 | <dglazkov> | simpler API |
| 03:41 | <Hixie> | it's not simpler, you'd still add a method |
| 03:41 | <dglazkov> | and changeVersion is hanging lower in the interface |
| 03:41 | <dglazkov> | hierarchy |
| 03:41 | <Hixie> | two, probably, since you have to check the version first |
| 03:41 | <Hixie> | and define how it works outside transactions, etc |
| 03:42 | <Hixie> | in fact it would be more complicated as far as i can tell |
| 03:46 | <dglazkov> | we could get away with one method tx.changeVersion(old, new), but I do wonder if it'll make it more complex in term of interaction with other statements in transaction. |
| 03:58 | <Hixie> | well you'd want to check first, then run the statements, then change at the end |
| 03:58 | <Hixie> | personally i think the way the spec works today is fine :-) |
| 04:06 | <Hixie> | 20 june 2006! |
| 04:11 | <jruderman> | does anyone implement the pseudo-rules part of http://www.w3.org/TR/css-style-attr ? |
| 05:13 | <MikeSmith> | Hixie: editorial nit, fwiw |
| 05:13 | <MikeSmith> | about r1419 |
| 05:13 | <MikeSmith> | [[ |
| 05:13 | <MikeSmith> | + <p>User agents must act as if any MathML element whose contents does not |
| 05:13 | <MikeSmith> | + match the element's content model was replaced, for the purposes of MathML |
| 05:13 | <MikeSmith> | + layout and rendering, by an <code title="">merror</code> element |
| 05:13 | <MikeSmith> | ]] |
| 05:13 | <MikeSmith> | I think it should be "the element's content model were replaced" |
| 08:21 | <zcorpan> | Hixie: "h1", "h2", "h3", "h5", "h6"<!--for completeness-->, ... not h4 (for completeness)? |
| 08:22 | <Hixie> | ooops |
| 08:24 | <zcorpan> | i thought the list would be a lot longer |
| 08:24 | <Hixie> | i might add more, but yeah |
| 08:24 | <Hixie> | there's not that much svg/mathml out there in text/html |
| 08:25 | <zcorpan> | ok |
| 08:25 | <zcorpan> | what about stray text in <svg>, though? not common? |
| 08:28 | <Hixie> | hm, didn't check that |
| 08:33 | <zcorpan> | neither <math> nor <svg> may contain text as direct children, so it would be possible to make non-whitespace bail if pages break because of it |
| 08:33 | <zcorpan> | (although <math>foo</math> would render fine either way) |
| 08:37 | <zcorpan> | <![CDATA[ is the odd one out in html wrt case sensitivity |
| 08:38 | <zcorpan> | i'm not saying it should be case insensitive, i'm just noting :) |
| 08:45 | <Hixie> | zcorpan: yeah. let me know if you see compat problems in reality if you implement this, and i'll add in whatever we need to avoid them |
| 08:45 | <Hixie> | i agree about the text thing |
| 08:45 | <Hixie> | but i'd rather not make more changes unless required |
| 09:56 | <hendry> | Hixie: http://www.flickr.com/photos/hendry/2399898537/ # acid3 on the Nokia S60 browser |
| 10:13 | <jruderman> | Hixie: acid2 font metrics drama in https://bugzilla.mozilla.org/show_bug.cgi?id=426616 |
| 10:17 | gsnedders | always forgets MikeSmith's name on twitter, and always has to look up who his nick is |
| 10:18 | <MikeSmith> | gsnedders: sideshowbarker |
| 10:18 | <gsnedders> | MikeSmith: yeah, it's the other way round |
| 10:18 | <MikeSmith> | ah |
| 10:18 | <gsnedders> | MikeSmith: seeing tweets from sideshowbarker, and wondering who the hell that is |
| 10:18 | <MikeSmith> | heh |
| 10:18 | <gsnedders> | MikeSmith: seeming I only follow people I actually know, it should know |
| 10:18 | <MikeSmith> | good, I like it that way |
| 10:18 | <MikeSmith> | I like the who-the-hell effect |
| 10:19 | <gsnedders> | I guess gsnedders doesn't have the same affect ;P |
| 10:20 | <MikeSmith> | gsnedders: so you're writing some pornographic science-fiction love ballads or something these days? |
| 10:20 | <MikeSmith> | given on HTML5 and turned to creative writing, have you? |
| 10:20 | <gsnedders> | MikeSmith: hah! |
| 10:20 | <gsnedders> | MikeSmith: not quite! :) |
| 10:21 | <gsnedders> | MikeSmith: it's not pornographic, it's slightly erotic. it's not science-fiction, it's based mainly on fact, and it's not a ballad anyway. |
| 10:21 | <gsnedders> | it's currently a far-too-short short-story |
| 10:23 | <gsnedders> | MikeSmith: and also turned back to http-parsing, so yeah, I am doing less with HTML 5 now, though I'm still reading what comes in |
| 10:23 | <MikeSmith> | yeah, I have noticed you on the httpbis list |
| 10:23 | <gsnedders> | anyhow, bbiab |
| 10:24 | <MikeSmith> | they are trying to give us HTML people a run for our money |
| 10:24 | <MikeSmith> | in terms of generating large volumes of e-mail |
| 10:56 | <gsnedders> | MikeSmith: But from what I see, about ignoring the reality of how HTTP is used and thinking they can specify anything that isn't conforming |
| 11:06 | <Hixie> | 24 feb 2007 |
| 11:06 | <Hixie> | i finally made it out of 2006 |
| 11:06 | <Hixie> | down to 20000 lines |
| 11:15 | <zcorpan_> | speaking of lines, there are 39942 non-blank lines in the generated spec source, which is the amount of testcases we need according to an old draft charter proposal, iirc |
| 11:22 | <Hixie> | sounds about right |
| 11:22 | <Hixie> | i'm surprised that the estimate works out that well |
| 11:40 | <Hixie> | 9 march 2008! |
| 11:42 | <annevk> | that we didn't start this discussion right on from 2004 :) |
| 11:43 | <annevk> | I guess that's because we didn't have the plan for writing down the parser algorithm back then... |
| 11:43 | <Hixie> | actually i've already sent a giant reply to these e-mails |
| 11:43 | <Hixie> | i dealt with namespaces in mid 2006 |
| 11:44 | <Hixie> | that's why the earliest e-mails are from then |
| 11:44 | <Hixie> | because all the earlier ones already got replies |
| 11:44 | <annevk> | interesting |
| 11:47 | <hsivonen> | If I implement data URIs (per, IIRC, Lachy's RFE), I'll end up creating an insanely inefficient way to upload schemas to Validator.nu... |
| 11:48 | <zcorpan_> | Hixie: pointer to that email? can't find in the archives searching for "namespace" in mid 2006 |
| 11:48 | <hsivonen> | but then, the current design doesn't take POSTed *schemas* into account in any way :-( |
| 11:48 | <Hixie> | zcorpan_: it was just maths, back then. search for anything from me. might have been a set of smaller e-mails instead of one big one. At least one of the e-mails had a general comment about tone and making positive contributions, which is probably the main one i'm thinking of |
| 11:49 | <Hixie> | early june 2006 |
| 11:49 | <Hixie> | or maybe late may |
| 11:50 | zcorpan_ | sees quite a bit of "math" emails in http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2006-June/thread.html |
| 11:53 | <hsivonen> | hmm. am I right that MIME allows backslash escapes in the value of the charset parameter? |
| 11:54 | <hsivonen> | like text/html; charset=\u\t\f\-\8 |
| 11:55 | <Hixie> | no idea, i've tried to ignore the details of that kind of syntax |
| 11:55 | <Hixie> | i have a firm head-in-the-sand approach to MIME |
| 11:56 | <Hixie> | especially it's sytnax |
| 11:56 | <Hixie> | syntax too |
| 11:57 | <hsivonen> | I'm trying to implement data URIs. correctly. |
| 11:57 | <Hixie> | let me know how that goes |
| 11:57 | <Hixie> | :-) |
| 11:58 | <Hixie> | i can add more tests to my data: uri test suite if you find edge cases that should be tested |
| 11:58 | <Hixie> | http://www.hixie.ch/tests/adhoc/data/ |
| 11:58 | <hsivonen> | ooh. a test suite. thanks |
| 11:59 | <annevk> | the tests for # might be incorrect |
| 12:05 | <hsivonen> | is space between ";base64" and "," allowed by some referenced RFC? |
| 12:09 | <hsivonen> | am I right that there's nothing prohibiting the type part of the URI from being percent-escaped? |
| 12:10 | <gsnedders> | hsivonen: plain old URI path, so sure, you can percent-escape it |
| 12:10 | <gsnedders> | hsivonen: even ;base64 can be escaped |
| 12:10 | <hsivonen> | excellent |
| 12:11 | <annevk> | <canvas>: http://blog.nihilogic.dk/2008/04/super-mario-in-14kb-javascript.html |
| 12:11 | <gsnedders> | the behaviour isn't quite right. you should be able to jump and slide along the bottom of something, getting all the coins along the way :( |
| 12:14 | gsnedders | played too much Mario when he was younger |
| 12:14 | annevk | finds a Hixie in the comments :) |
| 12:15 | <Hixie> | hm? |
| 12:15 | <Hixie> | oh, those comments |
| 12:15 | <Hixie> | heh |
| 12:15 | <Hixie> | i was replying to namespace e-mail, i swear |
| 12:18 | gsnedders | wonders whether to dig out his game boy |
| 12:18 | <gsnedders> | just to play Mario :\ |
| 12:18 | <Philip`> | That's what emulators are for |
| 12:19 | <gsnedders> | But that's not the same as using real ARM-based hardware! |
| 12:20 | <Philip`> | You could set up an ARM-based PC and run the emulator on that |
| 12:20 | <gsnedders> | Philip`: that means getting an ARM-based PC |
| 12:20 | <gsnedders> | (where can you get one from, anyway?) |
| 12:20 | <Philip`> | You make that sound like it's a bad thing |
| 12:21 | <gsnedders> | Philip`: getting one? It means spending money :P |
| 12:22 | <Philip`> | Nintendo seems to be defeating emulators nowadays by using hardware that isn't a subset of what PCs have - there's no way you could play most DS games with a mouse and keyboard :-( |
| 12:23 | <annevk> | the mouse could act like a stylus, maybe |
| 12:23 | <hsivonen> | "As a shorthand, "text/plain" can be omitted but the charset parameter supplied." aarrgh. |
| 12:23 | <gsnedders> | Philip`: iPhone? That's quite close to the DS in many ways |
| 12:23 | <hsivonen> | does the type start with ";" in that case? |
| 12:23 | <annevk> | whoa, data: has a charset? |
| 12:24 | <annevk> | that sounds like a pre-IRI thing... |
| 12:24 | <gsnedders> | hsivonen: I would assume so |
| 12:24 | <hsivonen> | annevk: data has crazy layering |
| 12:25 | <hsivonen> | consider text/plain as base64 data |
| 12:25 | <annevk> | omitting text/plain is nice |
| 12:25 | <annevk> | data:,data |
| 12:25 | <hsivonen> | the URI string is text |
| 12:25 | <hsivonen> | percent-decoding yields bytes |
| 12:25 | <hsivonen> | those are ASCII-decoded to text |
| 12:25 | <hsivonen> | that text is Base64-decoded into bytes |
| 12:25 | <hsivonen> | then the bytes are decoded as text |
| 12:26 | <hsivonen> | yay! |
| 12:26 | <gsnedders> | how about: data:%3Bcharset=UTF%2D8;base64,SGVsbG8sI%48dvcmxkIQ== |
| 12:26 | <gsnedders> | that crazy enough? |
| 12:27 | <Hixie> | i'm not convinced you can %-escape before the , |
| 12:27 | <Hixie> | but i'm not sure |
| 12:28 | <gsnedders> | Hixie: nothing prohibits it, as far as I can see, so normal URI path rules apply |
| 12:28 | <gsnedders> | Safari copes with my example |
| 12:29 | <gsnedders> | "where "urlchar" is imported from [RFC2396]" — I see no urlchar there :\ |
| 12:29 | <Hixie> | no you can only have %XX in pct-encoded |
| 12:30 | <gsnedders> | sure, but in that case it doesn't even allow it in the actual data |
| 12:30 | <Hixie> | oh nevermind |
| 12:30 | <gsnedders> | it doesn't explicitly allow pct-encoded anywhere |
| 12:30 | <Hixie> | it explicitly says "represented using URL escaped encoding of [RFC2396] as necessary" |
| 12:31 | Hixie | goes back to namespace hell |
| 12:31 | <gsnedders> | 'where "urlchar" is imported from [RFC2396]' — that's odd, though, seeming there is no urlchar |
| 12:32 | <gsnedders> | maybe pchar? |
| 12:32 | <gsnedders> | and no erratum about that |
| 12:32 | <hsivonen> | so %-encoding is allowed anywhere after "data:", right? |
| 12:32 | <gsnedders> | hsivonen: yeah |
| 12:42 | <Hixie> | bed time |
| 12:42 | <Hixie> | nn |
| 21:17 | hsivonen | sees property="dc:title" on <h1> on Flickr |
| 21:19 | <annevk> | evil :) |
| 21:19 | <annevk> | in related news: http://www.w3.org/News/2008#item66 |
| 21:20 | <gsnedders> | What a name… |
| 21:21 | <annevk> | more: http://www.w3.org/2005/Incubator/app-backplane/charter-20080409.html |
| 22:37 | <Hixie> | gotta love how microsoft are considering extensions to DOM3 Events before even implementing DOM1 Events |
| 22:46 | <othermaciej> | Hixie: my wild-ass guess based on Travis's last message is that customers want a way to remove all event listeners when leaving a page to avoid IE's memory leak problems with leftover event listeners |
| 22:48 | <Hixie> | maybe |
| 22:48 | <Hixie> | of course if we don't spec what they want, they'll just make up their own shit and say we wouldn't give it to them |
| 22:50 | <annevk> | would that be different for other UAs? |
| 22:50 | <annevk> | Mozilla has quite a few extensions to Range for instance... |
| 22:54 | <Hixie> | i'm just saying that we can't prevent them from adding this feature |
| 22:54 | <Hixie> | so we should specify it carefully with them, to ensure that it addressed real Web concerns and is the best thing for the Web |
| 22:54 | <othermaciej> | I don't strongly care if they add the feature, or if the spec adds it |
| 22:54 | <annevk> | (Having said that, I'd actually like to trim DOM Level 3 Events... Namespaces for instance...) |
| 22:54 | <othermaciej> | I would like to understand the use case to make sure we design the right feature for the job |
| 22:56 | <othermaciej> | (if the job is "avoid IE memory leaks" then I think the right feature for the job does not involve any new API) |
| 22:56 | <othermaciej> | (but maybe Travis has more details for us) |
| 23:06 | <annevk> | MathML 3 uses xml:id... |
| 23:08 | <takkaria> | where's MS talking about extensions to DOM3? what have I missed? :) |
| 23:08 | <annevk> | http://lists.w3.org/Archives/Public/public-webapi/2008Apr/ |
| 23:09 | <takkaria> | ah, thanks |
| 23:12 | <roc> | hmm |
| 23:13 | <roc> | does that mean IE8 is doing DOM2 events? |
| 23:13 | <annevk> | maybe, though i'd expect IE9 |
| 23:15 | <roc> | working on IE9 already? |
| 23:16 | <annevk> | no idea :) |
| 23:16 | <annevk> | i catch your drift now, if it's customer request IE8 might be more plausible |
| 23:24 | <Hixie> | i don't think i can recall any time microsoft has asked for a new feature without saying it was a customer request -- i don't think they do anything to their platform that isn't directly requested by customers |
| 23:25 | <Hixie> | so that can't distinguish between IE8 and 9 |