00:21
<Hixie>
is dave singer here, or anyone who has any opinion on the cue range idea?
00:24
<Hixie>
i have two problems
00:24
<Hixie>
i don't know how to port the "autopause at time" idea over to ranges
00:24
<Hixie>
and i don't know how to support the removal of ranges
00:25
<Hixie>
for the latter, i see four options:
00:25
<Hixie>
1. require all four arguments to be passed again
00:25
<Hixie>
2. return a handle when you add, and require the handle to remove
00:25
<Hixie>
3. just have something that removes all ranges between two points on the timeline
00:26
<Dashiva>
If there's a iterator for all existing handles, 2. could be good
00:26
<Hixie>
4. pass some identifier to the add method, and use that identifier (a "class name" for one or more ranges) to remove all ranges with that identifier
00:26
<Hixie>
adding an iterator seems harder than desired
00:27
<Hixie>
oh hey i know how to do the pausing thing. just pause at the start and end of a range
00:27
<Hixie>
when exiting
00:28
<Hixie>
5. not have a way to remove handlers.
00:28
<Hixie>
6. only have a way to remove all ranges
00:29
<Dashiva>
Well, I reckon the UA will need an internal list of handles anyhow. Exposing a .length and .item isn't that much more, is it?
00:30
<Hixie>
it's more than that
00:30
<Hixie>
you'd need to expose an object for each one, etc
00:33
<Hixie>
when would you remove cue ranges
00:33
<Hixie>
when changing media
00:33
<Hixie>
when switching in new subtitles
00:33
<Hixie>
anything else?
00:35
<Hixie>
i think i'm gonna go with 4.
00:35
<Hixie>
addCueRange() is gonna have a class name you can pass it
00:35
<Hixie>
and then you'll be able to remove all ranges with that class name
00:35
<Hixie>
that way you can add one set of ranges for ads, one for subtitles, one for lyrics, etc
00:35
<Hixie>
and switch them dynamically by just nuking the set you don't want
00:50
<jruderman>
Hixie: https://bugzilla.mozilla.org/show_bug.cgi?id=401217
00:52
<Hixie>
yeah
00:52
<Hixie>
he raised the issue in public-html as well
00:52
<Hixie>
as far as i can tell he's wrong about the POST issue
00:52
<Hixie>
turning the feature off would be a net loss for users, since it'll just mean authors continue using the tricks they use now, with the associated problems they have (which ping solves)
00:55
<Hixie>
commented
00:58
<jruderman>
thanks
01:42
<Hixie>
hahaha!
01:42
<Hixie>
i did it!
01:42
<Hixie>
there are NO outstanding comments on sql, offline, or video! (not counting the codec issue)
01:42
<Hixie>
sweet
02:05
<Hixie>
ok, we have a call for comments out:
02:05
<Hixie>
http://www.whatwg.org/specs/web-apps/2007-10-26/
02:06
<Hixie>
someone should feel free to write a whatwg blog entry about it if they feel up to it and care enough :-)
18:00
<zcorpan>
Hixie: shouldn't the frozen copy have used <body class=cfc>? :)
18:08
<zcorpan>
what's up with the orange background on normative text in the xhtml2 wg's specs?
18:08
<zcorpan>
it makes it really annoying to read
18:10
<zcorpan>
i also like "this example is informative", which makes one go "hmm, are there examples that are normative?"
18:20
<gsnedders>
More exam board fun: "<html>: Tag contains the entire document identifies the page as valid HTML"
18:21
gsnedders
is almost glad he doesn't have to do that optional section, and can do another instead which is slightly less wrong
18:23
<gsnedders>
actually, not very much stuff that is wrong is taught in the multimedia section! yay!
18:51
<zcorpan>
Hixie: done. http://blog.whatwg.org/html5-snapshot
19:34
<jacobolus>
Hixie: what is the standard for things going on the whatwg blog. If I write an article about event-source and server-sent-events, and the limits of opera's current implementation of them, would it be relevant to put a link to that from the whatwg blog?
19:38
<zcorpan>
jacobolus: i think you can write pretty much anything you like on the whatwg blog, but put the article on the whatwg blog (some articles have been cross-posted before), don't just put a link there. it's not a link blog :)
19:39
<jacobolus>
ah, okay :)
19:39
<jacobolus>
zcorpan: I certainly wouldn't *just* put a link :)
19:39
<zcorpan>
i think you may have to ask Lachy for publishing your first post
19:39
<jacobolus>
i mean, even it it was mostly a link, it would have 2-3 paragraphs of explanation. but cross-posting might be fine :)
19:40
<zcorpan>
ok
19:41
<zcorpan>
that might be fine too, btw, i just stated my understanding :)
20:55
<zcorpan>
http://forums.whatwg.org/viewtopic.php?t=31#452