- From: Garrett Smith <dhtmlkitchen@gmail.com>
- Date: Mon, 31 Aug 2015 11:27:30 -0700
- To: Michael Enright <mike@kmcardiff.com>
- Cc: WHAT Working Group <whatwg@lists.whatwg.org>, Domenic Denicola <d@domenic.me>, "robert@ocallahan.org" <robert@ocallahan.org>
On 8/31/15, Michael Enright <mike@kmcardiff.com> wrote: > On Fri, Aug 28, 2015 at 11:17 AM, Domenic Denicola wrote: >> From: Robert O'Callahan >> >>> According to the spec it should work, but it's very low priority for us >>> and >>> implementing it would be very inefficient as Yay295 describes. So I >>> don't >>> think it's going to happen in Firefox in the forseeable future. >> >> I was looking in to this yesterday and it seems like the spec places >> absolute no limits on playbackRate. Am I right? This seems a bit bad. >> >> If nobody is supporting negative nor has any plans to, we should at least >> consider throwing for negative. I guess we can leave the upper limit >> unspecified, unless implementations all happen to agree on one. >> > > I have implemented video element implementations which allowed the > video to play in reverse, and scripts that ran on such implementations > that allowed the user to ask for playback in reverse. If it is thought > that browser scripts need guidance on what speeds are possible for a > given server or video, then by all means go that route. > > USE CASE: Implementing things like VidiPath or in some other fashion > implementing satellte STB or cable STB UI in HTML 5. > USE CASE: https://www.youtube.com/watch?v=BtSdt1G6mcE -- Garrett @xkit ChordCycles.wordpress.com garretts.github.io personx.tumblr.com
Received on Monday, 31 August 2015 18:27:58 UTC