W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > April 2011

[Bug 12426] Effect when @src of video element contains temporal media fragment URI and @loop

From: <bugzilla@jessica.w3.org>
Date: Thu, 07 Apr 2011 23:01:41 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q7yCr-0006tS-31@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12426

--- Comment #11 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-04-07 23:01:40 UTC ---
(In reply to comment #10)
> (In reply to comment #9)
> > Are you suggesting that when a @loop is given on a video for which a fragment
> > is specified, we ignore @loop and just stop playing at the end of the fragment,
> > no matter what? I don't think that meets the expectations of the developer.
> 
> Yes, because the alternatives I've seen so far seem even worse and the use
> cases for looping over a fragment don't seem very strong to begin with. For
> things like games that pack many sound effects into a single audio file to save
> network traffic I think that something like Mozilla's audio API that allows
> slicing and dicing the raw audio data is a good candidate.

The use case for looping over a fragment are no worse than the use cases for
looping over the complete video. I'm not a fan of that attribute myself, but it
exists, it has an effect on video elements and it needs to show the expected
effect when the resource is limited to a fragment, too, which should be looping
over the fragment rather than the full video.

-- 
Configure bugmail: http://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 Thursday, 7 April 2011 23:01:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:08 UTC