01:09
<kingryan>
has anyone else implemented the content-type sniffing in the spec?
02:23
<JohnResig>
weinig: hehe, my name is 'resig' ;) btw http://trac.webkit.org/changeset/35134 I updated the test suite a bunch this afternoon, might want to pull a fresh copy (fixing up some unresolved failures) let me know if you have any questions!
02:24
<weinig>
oh noes!
02:24
<weinig>
will fix
02:24
<weinig>
sorry!
02:25
<weinig>
JohnResig: I think "xHTML|*#root3 xHTML|div svg *|circle" is still incorrect
02:25
<weinig>
circle1 should be allowed
02:26
<JohnResig>
weinig: one sec, I chatted with boris about this
02:26
<weinig>
ok
02:31
<JohnResig>
weinig: it seems to make sense to me - I'm double-checking. The one case that I fixed in that test was where a default namespace was actually provided - in that case the result should be *just* "circle1"
02:33
<weinig>
JohnResig: sorry
02:33
<weinig>
JohnResig: you were saying?
02:33
<JohnResig>
weinig: it seems to make sense to me - I'm double-checking. The one case that I fixed in that test was where a default namespace was actually provided - in that case the result should be *just* "cir
02:33
<JohnResig>
oops
02:34
<JohnResig>
*just* circle1
02:34
<weinig>
why just circle1?
02:34
<weinig>
svg should be interpreted as *|svg in this case
02:35
<JohnResig>
since when a default namespace is provided (when the resolver returns "http://www.w3.org/1999/xhtml";) it should limit it to that namespace - the other case, that the test also handles, is when the resolver returns undefined as the default namespace - in that case it should probably be "*|svg" - which is what I'm double-checking on right now.
02:40
<weinig>
JohnResig: no default namespace is provided though
02:41
<JohnResig>
weinig: "Good Namespace" resolvers 1, 3, 5, 7 return a default namespace if null is passed in
02:42
<weinig>
right, I think this was for number 2
02:42
<JohnResig>
correct - which is what I mentioned - that you and I think it should be equal to *|svg
02:42
<JohnResig>
and it's what I'm double-checking on now
02:42
<weinig>
I see
02:43
<JohnResig>
I had discussed it with bz earlier, I just wanted to verify our talk
03:27
<Hixie>
wtf is frank smoking
03:44
<weinig_>
JohnResig: receive verification? :)
04:24
<Hixie>
why won't apple take my money, othermaciej
04:24
Hixie
has been trying to update his ipod for 2 days now
04:27
<jruderman>
wait, doesn't the update fix a bunch of security holes? they're making you pay for a security fix?
04:28
<jruderman>
i'm going by http://blog.washingtonpost.com/securityfix/2008/07/a_bakers_dozen_security_update.html
04:38
<Hixie>
the only part of the update i care about is the part that gives me a public key that i can use to verify signed software
04:39
<Hixie>
which i guess is a "security fix" in the same sense that being under house arrest is a "security fix" for the people in the house
04:39
<Hixie>
(this feature is being marketed as "app store")
04:59
<Hixie>
this has to be the most botched launch of the year
05:21
<Hixie>
oooh, it started downloading
07:06
<othermaciej>
Hixie: if you'd like to send your money direct to me instead I'd accept it
07:07
<Hixie>
hah
07:08
<Hixie>
do i also get the stuff i would get through the normal channels? :-)
07:12
<othermaciej>
oh, you want to get stuff for your money
07:12
<othermaciej>
how selfish
07:46
<Hixie>
holy crap
07:46
<Hixie>
undocumented unexpected bug fix in ipod touch 2.0 software
07:47
<Hixie>
unicode font that includes U+263A!
07:53
Hixie
wonders why safari doesn't support Link: headers with rel="icon"
08:10
<Hixie>
hey the music player also takes video now
08:20
<Hixie>
good god
08:20
<Hixie>
is frank for real?
08:21
<Hixie>
calling firefox "bastard browser from hell" is so not professional
08:22
<MikeSmith>
dude seems to be in a world of his own
08:26
<MikeSmith>
Hixie: I guess you reopened Bug 5830 because of latest mail from Philip Jägenstedt about cue ranges?
08:44
<MikeSmith>
hmm, this is weird. I'm trying to use html5lib to parse the HTML5 spec, read in from the web (instead of a local filesystem copy). Sometimes it works, but sometimes it seems to get only part way through and then just quits -- without emitting any error.
08:45
<MikeSmith>
when it quits, I seem to end up with a truncated version of the source, which if I serialize it, looks like, e.g.:
08:45
<MikeSmith>
</td><td> There is a <a href="#ltquerygt" title="url-query">&lt;query&gt;</a>
08:45
<MikeSmith>
component, but it is empty. The question mark in the resulting value
08:45
<MikeSmith>
is the prefix</td></tr></tbody></table></div></body></html>
08:46
<MikeSmith>
is there another python HTML parser I can use?
08:46
<Hixie>
the philip and david mails
08:46
<MikeSmith>
Hixie: I see
09:27
<jgraham>
MikeSmith: Can you report that as a bug please? I have an idea what the problem is but can't look right now
09:36
<jgraham>
(fwiw I suspect it works if you read the whole thing off the network up front)
09:41
<othermaciej>
Hixie: frank who?
10:05
<Lachy>
othermaciej, Frank Ellermann on public-html-comments http://lists.w3.org/Archives/Public/public-html-comments/2008Jul/0013.html
10:08
<Lachy>
othermaciej, I think I may have a better solution to the NSResolver issue.
10:09
<weinig>
JohnResig: you around?
10:09
<Lachy>
If I make it a DOMString that uses the @namespace syntax, then browsers can use their existing parsers from CSS, it shifts the case sensitivity issue from selectors api to css3-namespace, solves all the problems with the function approach and is relatively easy and familiar for authors already using namespaces in selectors
10:10
<Lachy>
weinig, what do you think about that?
10:11
<Lachy>
e.g. querySelector("x|p", "@namespace x 'http://example.com'";);
10:11
<weinig>
Lachy: it might be a little cumbersome but I think it could work nicely
10:12
<Lachy>
since namespaces are a silly little edge case that authors will use relatively rarely, I don't really care that much about it being a little cumbersome
10:12
<Lachy>
but it's less cumbersome than the function
10:13
<weinig>
Lachy: way less!
10:14
<weinig>
Lachy: so the separate namespaces would be separated by ; ?
10:14
<weinig>
as in stylesheets
10:14
<Lachy>
yes
10:15
<Lachy>
and best of all, I get away with not having to define syntax and parsing requirements as I would have for the other DOMString suggestions previously raised on public-webapi
10:17
<othermaciej>
Lachy: BETTER THAN WHAT?
10:17
<othermaciej>
Lachy: THAT SEEMS OK
10:17
<othermaciej>
Lachy: oops
10:17
<othermaciej>
sorry I accidentally hit caps lock
10:21
<Lachy>
othermaciej, I wondered why you were shouting at me? :-)
10:21
<Lachy>
othermaciej, it's better than the current function approach
11:00
<Hixie>
all set up now. http://junkyard.damowmow.com/329
11:00
<Hixie>
i can now go back to fixing the spec.
11:00
<Hixie>
oh good, julian took care of frank.
11:00
Philip`
wonders who uses pi-bar as a currency
11:01
<Hixie>
valid question
11:02
<Philip`>
Oh, apparently 元 is Yuan so it's Chinese people
11:07
<Hixie>
ah
11:10
<Lachy>
Philip`, who said anything about "pi-bar"?
11:12
<Hixie>
i did
11:13
<Lachy>
where?
11:23
<Hixie>
"all set up now. http://junkyard.damowmow.com/329";
11:23
<Hixie>
oops, forgot to remove the DHSPAM marker that my spam filter added
11:23
<Hixie>
oh well
11:23
<Hixie>
i hope frank doesn't take offence
11:24
<Lachy>
oh, I see. In the currency converter logo.
11:55
<takkaria>
Hixie: how could you give credit to someone who's making you spell "tokenisation" wrong? :P
11:55
<Hixie>
eh i gave up on that months ago, the word tokenisation somehow slipped through the cracks
11:55
<Hixie>
everything else was changed a while back
11:55
<takkaria>
ah
11:56
takkaria
sighs
11:56
<Lachy>
what? why?
11:56
<Lachy>
tokenisation is the correct spelling
11:56
<Hixie>
imho it should be spelt tokenization
11:56
<Lachy>
silly corrupted american spelling :-(
11:57
<Hixie>
er wait
11:57
<Hixie>
other way around
11:57
<Hixie>
it should be spelt tokenisation
11:57
<Hixie>
but the spec now spells it tokenization
11:57
<Hixie>
or something
11:57
<Hixie>
i dunno
11:57
<Hixie>
whatever
11:58
<Lachy>
I see you did that mostly with color/colour too
11:58
<Hixie>
yeah
11:58
<Hixie>
not a battle worth fighting
11:58
<Lachy>
who insisted on changing it to en-US?
11:59
<Lachy>
(my specs are in en-AU and they're not changing)
11:59
<Hixie>
w3c policy
11:59
<Hixie>
good luck with that
11:59
<Lachy>
I'd be willing to settle for en-GB though
11:59
<Lachy>
the spelling is mostly the same
12:02
<Hixie>
i have plenty of petty fights already without adding spelling to the list :-)
12:02
<Hixie>
mostly i don't have a good argument against the spelling thing
12:02
<Hixie>
whereas i do on the other petty things :-)
12:03
<mcarter>
Lachy, it seems pretty trivial to come up with a list of words to transform from en-AU to en-US as part of the "publication process"
12:03
<Lachy>
I do. It's my native spelling and my editors all have en-AU spell checkers. If I were to use en-US, it would make it more difficult and easier for spelling mistakes to slip through
12:03
<takkaria>
just pretend you're a toff and you refuse to speak in American when you go fox-hunting
12:03
<Hixie>
sadly for me my editors all have en-US spelling checkers, so that doesn't work for me :-)
12:04
<Hixie>
anyway, that's enough editing for a friday night
12:04
<Hixie>
more tomorrow probably
12:04
<Hixie>
nn
13:24
<annevk>
Hixie, "patter length"
13:25
<Lachy>
annevk, any thoughts about my @namespace proposal for selectors api?
13:29
<annevk>
it puts a dependency on CSS
13:30
<annevk>
also, it seems worse than my proposal
13:30
<annevk>
but it seems nobody is interested in mine
13:41
<Lachy>
what was your proposal? dropping it?
13:41
<annevk>
yes
13:44
<JohnResig>
weinig|zZz: I added the "circle1" that we talked about, last night
14:15
<annevk>
seems validator.nu is back up
14:15
<annevk>
the logo remind of V for Vendetta
18:12
<Lachy>
does anyone know if we have the use cases for scoped stylesheets documented anywhere?
20:22
<jgraham>
Lachy: http://esw.w3.org/topic/HTML/StyleAttribute indirectly has some of the use cases for <style scoped>