00:00
<gsnedders>
g'nite y'all
00:07
<Hixie>
Philip`: yeah
00:09
<Dashiva>
Isn't there a three-month view?
00:09
<Hixie>
depends on the list
00:12
<gavin>
depends on the number of messages per month, I thought
00:12
<gavin>
i.e. I thought it was automatic based on number of messages, instead of configured manually
00:12
<Hixie>
no
00:12
<Hixie>
manual
00:12
<gavin>
ah, ok
00:13
<Hixie>
gotta go again
00:37
<othermaciej>
hey, I got reddit karma points for defending html5: http://programming.reddit.com/info/61vbd/comments/
00:37
<othermaciej>
(the thread was going much the other way before my post)
00:45
<Dashiva>
"I say let Adobe's Air & Google's Gears work out the kinks, then maybe a few years down the road (once the issues with the core languages are settled) go about implementing them."
00:47
<Dashiva>
Although this one was more convincing: "html5 is a joke anyways and will never be adopted or supported and if it is I will get an ak 47 and find a rooftop"
00:47
<othermaciej>
heh
00:47
<Philip`>
Don't AK-47s work just as effectively at ground level?
00:47
<Dashiva>
Why are people so unpatriotic? Can't they use proper western firearms?
00:51
<jwalden>
the day of the tommy gun has passed
00:52
<bradee-oh>
http://www.ak-47.us/USmade.php <--- AK-47 varieties made in the United States
00:58
<othermaciej>
US military issue firearms are generally much harder to maintain than the AK-47
00:58
<othermaciej>
which is why they are not used as much by guerilla armies and criminal gangs and the like
01:00
<Philip`>
The US military should develop a really bad gun, then make it easy to obtain and put a huge PR campaign behind it, so the guerilla armies and criminal gangs think it's excellent and buy lots of it
01:01
<Dashiva>
Make a gun that calls the police when you fire it!
01:05
<Philip`>
Dashiva: The problem with that plan is that it would have to have something like a mobile phone embedded in the gun, and prolonged use might lead to excess levels of radiation, which would be a health hazard
01:07
<Dashiva>
It's three mile island all over again
05:58
<Hixie>
that's odd
05:58
<Hixie>
i posted a huge comment to sam ruby's blog the other day
05:58
<Hixie>
and it hasn't appeared
07:23
<othermaciej>
mine appeared
07:30
<othermaciej>
I just posted a slightly mean reply on his blog
07:52
<Hixie>
another?
08:03
<othermaciej>
I didn't think the first one was that mean
08:08
<Hixie>
indeed, hence my question
08:10
<othermaciej>
so, yes, another reply
15:27
<hendry>
hsivonen_: don't understand this transparent error http://validator.nu/?doc=http%3A%2F%2Fvideo.natalian.org%2Ftest%2Fhtml5-media-mp3.html
15:28
<Dashiva>
transparent?
15:28
anne-mac
gets that <audio> can't occur in <body>
15:33
<hendry>
anne-mac: really? not <body>? even with controls?
15:34
<hendry>
same goes for video I expect http://validator.nu/?doc=http%3A%2F%2Fvideo.natalian.org%2Ftest%2Fhtml5-media-ogg.html
15:35
<anne-mac>
yes
15:36
<anne-mac>
needs to be inside a paragraph like element, such as <p> or <figure>
15:38
<hendry>
anne-mac: ok, fine
15:38
<hendry>
though http://validator.nu/?doc=http%3A%2F%2Fvideo.natalian.org%2Ftest%2Fhtml5-media-ogg.html
15:38
<hendry>
seems to expect children on the video element
15:40
<hendry>
i don't understnad this 'transparent' business
15:42
<Dashiva>
Looks like fallback
15:43
<Dashiva>
Basically says "If you replace the element with its transparent children" which is essentially what is supposed to happen with fallback, as I understand it
15:43
<hsivonen_>
hendry: transparent means that the content model is block if the parent's content model was block. et.
15:43
<hsivonen_>
etc.
15:43
<hendry>
so it want's me to put something in there, like "You failed to playback the media"
15:44
<hsivonen_>
hendry: also, IIRC, there's a spec bug near here and I've implemented the spec pedentically with the bug
15:44
<hsivonen_>
hendry: the bug is that if the parent is figure, the transparent content model sucks and you have to put an <img> there
15:45
<Dashiva>
"When a transparent or semi-transparent element has no parent" <-- How does that work, unless documentElement is transparent?
15:45
<hsivonen_>
Dashiva: document fragments I guess
15:46
<hsivonen_>
hendry: hmm. interesting. I don't know why you are getting the error you are getting
15:47
<Dashiva>
Maybe you need a container (div,p) inside it to hold the (non-existent) content
15:48
<hendry>
oh gosh. i hope this block, inline stuff becomes a whole lot easier
15:48
Philip`
too :-)
15:49
<hsivonen_>
hendry: there's a chance you are seeing a validator bug. I'm not sure. I checked the schema and it isn't obvious to me why you get the error you are getting
15:49
<hsivonen_>
oohh!
15:49
<hsivonen_>
I have a bug!
15:51
<hsivonen_>
hendry: I'm fixing it now
15:52
<Dashiva>
Now that's customer service
15:52
<hendry>
hsivonen_: :)
15:56
<hsivonen>
and I should remove significant inline checks as well...
16:01
<hsivonen>
hendry: fixed
16:01
<hsivonen>
hendry: I'll remove the significant inline thing in due course
16:12
<hsivonen>
hendry: now fixed
16:12
<hsivonen>
hendry: thanks for finding this
16:21
<hendry>
hsivonen: thanks for the fix :)
17:48
<gsnedders>
Hixie: I'm wondering whether to integrate Content-Type sniffing into my spec, as it really does have an effect on what is effectively in Content-Type
17:49
<gsnedders>
Hixie: you got any thoughts on whether it should or should not be there?
22:24
<hendry>
i've written a web app using WF2, http://letter2.dabase.com/