Last Comment Bug 498253 - Need to implement updated media timeline support
: Need to implement updated media timeline support
: html5
Product: Core
Classification: Components
Component: Audio/Video: Playback (show other bugs)
: Trunk
: All All
-- normal with 5 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Anthony Jones (:kentuckyfriedtakahe, :k17e)
: 503802 521899 566375 589565 603034 635569 (view as bug list)
Depends on: 648595
Blocks: ietestcenter
  Show dependency treegraph
Reported: 2009-06-14 16:50 PDT by cajbir (:cajbir)
Modified: 2016-01-22 02:50 PST (History)
19 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image cajbir (:cajbir) 2009-06-14 16:50:38 PDT
The WHATWG specification has changed to add a 'startTime' attribute to the MediaElement. This needs to be implemented.
Comment 1 User image Chris Pearce (:cpearce) 2009-10-12 16:12:49 PDT
*** Bug 521899 has been marked as a duplicate of this bug. ***
Comment 2 User image Chris Pearce (:cpearce) 2009-10-12 16:13:05 PDT
We're out of date with the current HTML video spec. The timeline (i.e. the
values of HTMLMediaElement.currentTime) of a video/audio should go from the
"earliest possible position" to the las possible position. We currently always
have the playback position starting a 0 and ending at duration.
Comment 3 User image Justin Dolske [:Dolske] 2009-10-12 18:46:22 PDT
This seems like a somewhat unfortunate thing for the spec, I bet everyone's going to get it wrong because it won't be common. :( I can't help but wonder if it would be better to have a startTimeOffset property, so that .currentTime et al are all still have a timeline starting from 0, and if you want the "real" time you'd use .currentTime + .startTimeOffset.

I'd also suspect we'll want the default video controls to normalize everything to 0 (.currentTime - .startTime), since it would be really confusing otherwise.
Comment 4 User image Robert O'Callahan (:roc) (email my personal email if necessary) 2009-10-12 19:11:33 PDT
I totally agree with comment #3.
Comment 5 User image Chris Pearce (:cpearce) 2010-04-27 20:31:06 PDT
*** Bug 503802 has been marked as a duplicate of this bug. ***
Comment 6 User image Chris Pearce (:cpearce) 2010-05-17 14:38:47 PDT
*** Bug 566375 has been marked as a duplicate of this bug. ***
Comment 7 User image Matthew Gregan [:kinetik] 2010-06-24 17:38:08 PDT
When this bug is fixed, the following test should pass:
(Note that the tests current sniff the user agent for Firefox--hopefully that'll be fixed soon.)
Comment 8 User image :Ms2ger (⌚ UTC+1/+2) 2010-08-22 12:27:26 PDT
*** Bug 589565 has been marked as a duplicate of this bug. ***
Comment 10 User image Matthew Gregan [:kinetik] 2010-10-13 19:34:42 PDT
*** Bug 603034 has been marked as a duplicate of this bug. ***
Comment 11 User image Matthew Gregan [:kinetik] 2010-10-13 19:38:00 PDT
Spec changed again, morphing this bug to track the current state.
Comment 12 User image Matthew Gregan [:kinetik] 2011-02-19 18:25:39 PST
*** Bug 635569 has been marked as a duplicate of this bug. ***
Comment 13 User image Odin Hørthe Omdal 2011-05-11 06:11:54 PDT
Any new developments here?
Comment 14 User image cajbir (:cajbir) 2011-05-11 06:30:45 PDT
I'd be reluctant to start implementing this part of the spec until things like multitrack, media controller, streams, etc are less of a moving target. It's likely to be in a bit of flux.
Comment 15 User image cajbir (:cajbir) 2011-05-25 06:25:47 PDT
I'm adding 'initialTime' as part of the implementation of temporal media fragments in bug 648595.
Comment 16 User image Chris Needham 2012-03-16 03:33:49 PDT
I recently did some experimental work on synchronising events to live streams, and I patched Firefox to implement startOffsetTime for WebM streams.

I do agree that the spec needs some clarification. My colleague Sean O'Halpin blogged about this:
Comment 17 User image Florian Bender 2013-08-18 02:35:26 PDT
It's been some time and I guess the spec has stabilized. If there are still outstandind issues, did anybody file bugs?
Comment 18 User image Anthony Jones (:kentuckyfriedtakahe, :k17e) 2016-01-21 14:15:36 PST
This is no longer a requirement of the spec.

Note You need to log in before you can comment on or make changes to this bug.