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: Wed, 06 Apr 2011 09:01:04 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q7Obo-0000ju-RF@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12426

--- Comment #3 from Philip Jägenstedt <philipj@opera.com> 2011-04-06 09:01:03 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> > This is one of the corner cases with MF that has had me wondering what to do as
> > an implementor. Lacking strong use cases, I would prefer that the loop
> > attribute has no effect when used together with MF, to reduce the amount of
> > magical state.
> 
> The strong use case is simply the replay. Someone has carefully defined a
> temporal media fragment that illustrates a funny moment and wants to
> bookmark/share it. The loop on this media fragment will be to play and replay
> just this bit. For example, I just want to see the "trip over" of this rider in
> the Tour de France: http://www.youtube.com/watch?v=XycqQr03ba8#t=4,15

Personal preferences vary of course, but I'd prefer pressing play again to
replay the video, nothing is funny enough to loop indefinitely. However, the
issue is then what happens when you press play after pausing at the end of the
fragment range. What's the thinking on that? The user either wants to watch
from the beginning of range or keep watching past the end of the range, neither
is obviously the Right Thing™.

In a way, things would be a lot simpler API- and UI-wise if a temporal range
was more of a crop than a focus. That's not a great user experience though, so
I digress...

-- 
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 Wednesday, 6 April 2011 09:01:06 UTC

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