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: Mon, 11 Apr 2011 07:02:12 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q9B8W-0005IU-Vw@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12426

--- Comment #14 from Philip Jägenstedt <philipj@opera.com> 2011-04-11 07:02:10 UTC ---
(In reply to comment #13)
> If we find more and more use cases where we disallow @loop, we might as well
> completely remove it. You can always do the looping through JavaScript with
> direct setting of currentTime.

In principle I would be fine with this. The only benefit of loop is that it can
in theory be gapless, but I would really rather have a solution where one can
achieve gapless playback between different resources rather than just within a
single one. With adaptive streaming the low-level plumbing to be able to do
that will have to exist anyway.

However, there are games that use looping audio for background music, so I also
don't really mind keeping loop for the simple cases and just making it not work
for the complex cases.

-- 
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 Monday, 11 April 2011 07:02:16 UTC

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