00:00
<jacobolus>
Philip`: ↑
00:02
<Philip`>
I don't see any value in keeping it, unless there's some reason that I'm missing
00:02
<jacobolus>
okay. :)
00:03
<Philip`>
jacobolus: My font doesn't have that glyph :-p
00:03
<jacobolus>
the unicode up arrow? :)
00:04
<jacobolus>
sorry, i'll stick to --^ in the future ;)
00:04
<Hixie>
right. <video>.
00:04
<jacobolus>
Hixie: hrm?
00:04
<Hixie>
jacobolus: my next target in dealing with spec feedback.
00:05
<jacobolus>
ah, okay. so nothing to do with whether type="text/css" is needed in <link rel="stylesheet" …> then :)
00:05
<Hixie>
no, sorry, was just talking to myself :-)
00:05
<jacobolus>
Hixie: how many outstanding emails do you have? :)
00:06
<Hixie>
not counting the issues on the htmlwg wiki, http://www.whatwg.org/issues/data.csv
00:06
<Hixie>
(third column)
00:06
<jacobolus>
ack
00:06
<jacobolus>
good luck :)
00:06
<Hixie>
i'm aiming to reach 3500 by dec31, though i'm not sure if i'll shoot past that target or not
00:07
<Hixie>
i don't know how many i can do per quarter yet
00:07
<Philip`>
How predictable is the rate of new issues?
00:07
<Hixie>
still, the trend is downwards currently
00:07
<Hixie>
Philip`: hard to say
00:08
<Hixie>
Philip`: but that number is (new issues)-(completed issues)
00:08
<Hixie>
so right now the rate of replying is > the rate of new issues
00:08
<Hixie>
on average
00:10
<Hixie>
hm. i should get an LED display that shows this number and hang it in my cube
00:14
<jacobolus>
sounds depressing
00:15
<Hixie>
why?
00:16
<Hixie>
having this much feedback is awesome
00:16
<Hixie>
it means people care about the spec
00:16
<Hixie>
and means the spec stands a chance of being good
00:17
<Philip`>
You could get a big bucket and fill it with 3723 small items of food, and refill/eat as necessary to keep the number in sync with the number of outstanding issues, to provide a visual indication of progress
00:18
<Hixie>
mmm
00:18
<Hixie>
i don't think that would work well with the kind of food i eat
00:21
<jacobolus>
you need something very small, that never goes bad
00:21
<Hixie>
peanuts
07:08
<hsivonen>
jacobolus: IIRC, <meta charset=''> was said to work in IE/Gecko/WebKit/Opera but not in iCab
07:09
<jacobolus>
hsivonen: okay. fine by me :)
07:09
<jacobolus>
thanks for the followup :)
09:30
<Hixie>
i love replying to dozens of messages at once
09:30
<Hixie>
it goes so much faster
09:30
<Hixie>
so much easier than when each mail requires major surgery to the spec
09:31
<Hixie>
ok everyone? Focus on bikeshed issues, not on powerplant issues!
09:31
<othermaciej>
heh
09:31
<othermaciej>
I hope you get to the s/cue points/cue ranges/ one soon
09:32
<othermaciej>
I can provide more justification if the email on that is insufficient
09:32
<Hixie>
just 15 issues left on video
09:33
<Hixie>
and that one is #9
09:33
<Hixie>
i imagine i'll do it
09:33
<Hixie>
it seems reasonable
09:33
<Hixie>
unless i find some problem when speccing it
09:33
<othermaciej>
always a good caveat
09:34
<Hixie>
oh actually it's #8 too, dave sent me a headsup first which also ended up in my pile
09:34
<othermaciej>
heh
09:35
<Hixie>
the next issue is about the naming of the looping attributes
09:35
<Hixie>
which is a REALLY INTERESTING issue
09:35
<othermaciej>
heh
09:35
Dashiva
gets the shed paint ready
09:35
<othermaciej>
you did ask for bikeshed issues!
09:35
<Hixie>
true
09:36
<annevk>
our engineers wondered what we wasted our time on when I forwarded that
09:37
<Hixie>
hah
09:37
<Hixie>
i think i'll change loopcount to playcount and leave the rest as is
10:07
<Lachy>
Hixie, it seems strange for a media element to keep playing once it's been removed from the document and all references to it have been removed.
10:08
<Lachy>
especially since in such a case, it's impossible to ever access it again and stop it via script
10:08
<OmegaJunior>
I agree... would you send the player a stop message?
10:08
<OmegaJunior>
Or maybe even a kill message, so the player can free its memory as well?
10:09
<Lachy>
OmegaJunior, how would you access the player if the element is gone? The element provides the API. Without it, there's nothing
10:09
<OmegaJunior>
onbeforeunload?
10:10
<OmegaJunior>
there needs to be some kind of mechanism that recognises "oops it's gone"
10:10
<OmegaJunior>
Otherwise the media will continue to play, and retain memory
10:11
<Lachy>
I would hope browsers would stop playing it automatically once the user left the page, regardless
10:13
<OmegaJunior>
If the player is a plug-in or native, closing the page should destroy it and thus stop the playing. But when removing an element, that might not be the case. One can imagine a page-close to be handled far more aggressively in terms of clean-up than an element removal.
11:04
<Lachy>
I suppose the reason for keeping media elements playing must be because you don't know when the element no longer has any references until garbage collection is performed, and that's unpredictable when that will occur
18:53
<Hixie>
xhtml2 finally updated their draft to use the xhtml1 namespace http://www.w3.org/MarkUp/2007/ED-xhtml2-20071024/conformance.html#s_conform
19:05
<hsivonen>
Hixie: interesting that they put the namespace URI in schemaLocation as well.
19:13
<hsivonen>
there are now LEIRIs in addition to URI, IRI and HRRI?
23:23
<Hixie>
i'm mildly amused at the e-mails to www-html-cg every few weeks where people express surprise that we're not hitting the htmlwg charter's timetable
23:23
<Hixie>
we're almost exactly on track with my original timetable
23:24
<Dashiva>
-cg?
23:26
<Hixie>
coordination group
23:26
<Hixie>
where wgs send their status e-mails
23:27
<Dashiva>
aha
23:31
<Hixie>
oh hey
23:31
<Hixie>
actually
23:31
<Hixie>
we're going to miss my first milestone
23:31
<Hixie>
crap
23:31
<Hixie>
http://lists.w3.org/Archives/Public/www-archive/2006Nov/0045.html
23:31
<Hixie>
i guess i'd better publish a wd
23:32
<Dashiva>
Unilateral action? I smell a formal objection :P
23:33
<Hixie>
oh not through the w3c
23:33
<Hixie>
that'd take weeks
23:33
<Hixie>
we have 5 days before we miss the deadline
23:33
<Hixie>
just on the whatwg site
23:34
<Dashiva>
That sounds more feasible
23:35
<gsnedders>
Hixie: :D
23:35
<gsnedders>
Hixie: though isn't that a charter for the W3C HTML WG?
23:36
<Hixie>
it's what i proposed as the timetable for the html5 work
23:37
<gsnedders>
Hixie: can I raise a formal objection about the draft, though?
23:37
<hsivonen>
Hixie: seems to me that there's demand for an unofficial, open-source, ad hoc test suite already before 2011
23:38
<gsnedders>
Hixie: one minor irrelevant issue that is noted in the draft hasn't been fixed
23:38
<Hixie>
gsnedders: sure, but it won't make any difference to the whatwg, we don't have a formal objection process :-)
23:39
<Hixie>
hsivonen: hey if you want to do it quicker, be my guest :-D
23:39
<Dashiva>
The fo would be in the w3c, though, for willfully going outside standard procedure :P
23:39
<Hixie>
publishing drafts on the whatwg site is standard procedure for the whatwg :-D
23:40
<Hixie>
not my fault the w3c missed their self-set deadlines by months
23:40
<Dashiva>
The memo said doing anything outside the w3c was high treason
23:40
<Hixie>
oh i know i'm a traitor
23:41
<gsnedders>
Hixie: want the same punishment as some medieval traitors?
23:41
<gsnedders>
wait… we'll need a new editor then. damn.
23:42
<Dashiva>
I'm sure Google has an ample supply of clones
23:42
<gsnedders>
Dashiva: but in which datacentre?
23:42
<Hixie>
Dashiva: i wish
23:43
<gsnedders>
Dashiva: and why don't they make use of them?
23:43
<gsnedders>
Dashiva: we could have HTML 5 as a REC by the W3C timetable
23:43
<Dashiva>
They don't want to tip their hand, I suppose
23:52
gsnedders
can't believe he's actually become a loser on bebo