- From: <bugzilla@jessica.w3.org>
- Date: Mon, 30 Apr 2012 23:21:37 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14851 --- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-04-30 23:21:36 UTC --- On Sat, 22 Jan 2011, Michael Dale wrote: > > It seems the needs for a seek bar are different from the api usage of > setting video.currentTime. As people mention rules of 'least surprise' > are important. If you set currentTime to 3.453 you expect it to return > something very close to 3.453 .. > > Why not have a separate api for "seek bars" that just seek to a > percentage of the video stream. Letting implementations do what's > fastest and consistent, but without guarantees for a given play time > being set. This way the different needs are addressed and we don't > conflate the currentTime api with parameters for accuracy. > > In terms of real world use cases, we use accurate seeks in an html5 > video editor. Its especially important when flattening with firefogg > that as we can accurately set a given time in source videos per our > output frame interval. > > http://commons.wikimedia.org/wiki/Commons:Sequencer -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 30 April 2012 23:21:40 UTC