- From: Philip Jägenstedt <philipj@opera.com>
- Date: Thu, 27 Feb 2014 14:02:50 +0700
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: Leeroy <soupress@gmail.com>, Media Fragment <public-media-fragment@w3.org>
I would like it if Blink agreed with the spec, that's for sure. I think that looping correctly is too much work to be worth the effort, but if you file a bug on the WHATWG spec we can discuss it there. IIRC Hixie already rejected the idea once, but I can't find that old bug or mail... Philip On Thu, Feb 27, 2014 at 12:51 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > On Thu, Feb 27, 2014 at 2:24 PM, Philip Jägenstedt <philipj@opera.com> wrote: >> Blink just pauses when playing past the end time. However, HTML >> actually only integrates with the fragment start time (by setting the >> initial playback position) so I would argue that doing anything at all >> with the fragment end time is wrong. > > That would be a bug in the HTML spec - it should indeed pause just > like blink does, seeing as the end time is otherwise useless > information. > Would you agree? If so, we should register a bug on the HTML spec. > > Silvia. > >> Philip >> >> On Wed, Feb 26, 2014 at 11:20 PM, Leeroy <soupress@gmail.com> wrote: >>> I would like to propose looping of video fragments as well as entire videos. >>> >>> When rendering the following video element (in Chrome 33 and Firefox 27) >>> >>> <video loop autoplay> >>> <source src="video.webm#t=00:00.000,00:04.395" type="video/webm" /> >>> Your browser doesn't support the <code>video</code> element. >>> </video> >>> >>> >>> I expect it to loop the portion of the video from the start to 0 minutes 4 >>> seconds. >>> But instead it pauses at 0 minutes 4 seconds. >>> >>> If you can, please help me address this issue in the correct place. >>> Thank you! >>> >>> >>
Received on Thursday, 27 February 2014 07:03:20 UTC