- From: <bugzilla@jessica.w3.org>
- Date: Sat, 23 Apr 2011 09:34:29 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12545
Philip Jägenstedt <philipj@opera.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philipj@opera.com
--- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2011-04-23 09:34:29 UTC ---
Hate to pull this tired line, but: What's the use case?
Since it is an IDL attribute that's being suggested, it requires using scripts.
The only benefit over using .onended = function() { this.currentTime=0; } is
gapless looping, which seems to really be of rather marginal importance. In
short, I don't think it's something implementors should be spending time on.
Other than that, what behavior is expected when the resources which loop are
not of the same duration? Before looping was removed from the spec, it was to
loop each clip over its own duration. This is problematic when seeking if the
exact duration (down to the sample) isn't available before decoding the end of
the resource. The duration metadata in the file header isn't always of
sufficient precision.
--
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 Saturday, 23 April 2011 09:34:30 UTC