RESOLVED WONTFIX 48054
Implement startOffsetTime (after the new HTML5 media spec update)
https://bugs.webkit.org/show_bug.cgi?id=48054
Summary Implement startOffsetTime (after the new HTML5 media spec update)
Odin Hørthe Omdal
Reported 2010-10-21 03:06:35 PDT
The HTML5 spec was updated a while ago, I couldn't find any bug tracking that so this is not connected to a master-bug for it. Anyway, I'm pushing startOffsetTime because I need it for my webapp :-) You also need to fix your startTime, because now it doesn't conform to spec. This was my original bug (use case) to the WHATWG and browsers: I stream conferences using Ogg Theora+Vorbis using Icecast2. I have built a site that shows the video and then automatically shows the slides (as PNG files) as well. I use orbited (COMET) to have the server PUSH my «next» presses on my keyboard. The problem is that icecast does heavy buffering, and also the client, so that while I switch the slides, the browser will go from slide 3 to 4 WAY too early (from 10 second to 1 minute). If I could get the timestamp OR time-since-started-sending/recording from the ogg file in javascript, I'd be able to sync everything. There are multiple way to sync this, may even an stream with the slide-data INSIDE the ogg file, however, AFAIK there's also no way of getting out such arbitrary streams.
Attachments
Odin Hørthe Omdal
Comment 1 2011-05-11 06:17:11 PDT
Can this be confirmed?
Nicholas Shanks
Comment 2 2012-02-01 13:18:43 PST
BBC blog post regarding their implementation of this in Firefox: http://www.bbc.co.uk/blogs/researchanddevelopment/2012/01/implementing-startoffsettime-f.shtml
Ahmad Saleem
Comment 3 2023-10-12 13:02:17 PDT
Nothing to do here. These are now marked as 'historical' and we pass the test as well. https://wpt.fyi/results/html/semantics/embedded-content/media-elements/historical.html?label=master&label=experimental&aligned=&q=media-elements%2Fhistorical.html > audio.startOffsetTime should not be supported > video.startOffsetTime should not be supported
Note You need to log in before you can comment on or make changes to this bug.