W3C home > Mailing lists > Public > public-media-fragment@w3.org > May 2011

Re: Temporal media fragment for HTML media questions

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Tue, 10 May 2011 19:15:25 +1000
Message-ID: <BANLkTikQFpR3qGk6rpyuRqoz1JfO_vntPQ@mail.gmail.com>
To: Philip Jägenstedt <philipj@opera.com>
Cc: public-media-fragment@w3.org
On Tue, May 10, 2011 at 7:06 PM, Philip Jägenstedt <philipj@opera.com> wrote:
> On Tue, 10 May 2011 10:54:38 +0200, Silvia Pfeiffer
> <silviapfeiffer1@gmail.com> wrote:
>> On Tue, May 10, 2011 at 6:39 PM, Chris Double <cdouble@mozilla.com> wrote:
>>> On Tue, May 10, 2011 at 8:08 PM, Philip Jägenstedt <philipj@opera.com>
>>> wrote:
>>>>> 1) When a temporal fragment is given with a start time, when the
>>>>> loadedmetadata event on the resource is raised this is the currentTime
>>>>> of the resource.
>>>> Do you mean that you internally seek when reaching HAVE_METADATA? That's
>>>> what I did, but care must be taken to not show the first frame of the
>>>> video
>>>> before seeking. Also, should seeking events be fired at this point?
>>> I internally seek after I've read the metadata from the resource, then
>>> raise HAVE_METADATA when the seek is complete. I don't fire the
>>> seeking events. Would it be better to do HAVE_METADATA, then seek and
>>> raise the usual seeking events?
>>>>> 2) When an end time is given I do the equivalent of calling 'pause()'
>>>>> on the media element. I do not raise the 'ended' event.
>>>> Is paused set to true, or is the element "paused for user interaction"?
>>>> I
>>>> think the latter actually makes sense, but when I implemented MF as a
>>>> quick
>>>> hack for FOMS I just called pause().
>>> It behaves exactly as if the 'pause()' method was called on the media
>>> element, so 'paused' is set to true. I think this makes it easier for
>>> controls to stay in sync with what's happening.
>> I wonder if it would be better to behave like "cropping" during the
>> load and as long as no user interactions happen. Thus, fire
>> metadataloaded when the offset time is reached and fire ended when the
>> end time is reached. Do you think that would cause problems?
> By cropping I meant that the timeline is modified to map 0 to the start of
> the fragment and the duration is the duration of the fragment. This would
> make it impossible to seek outside the fragment, the user wouldn't even know
> that there was something called a fragment. Thus, it doesn't make sense to
> switching between cropping and something else.

Yeah, I didn't quite mean it that far. Just that events and all other
behaviour would be as though the video is only that short.
Received on Tuesday, 10 May 2011 09:16:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:46 UTC