[whatwg] <video>/<audio> feedback
singer at apple.com
Tue May 12 21:29:42 PDT 2009
At 12:09 +1000 13/05/09, Silvia Pfeiffer wrote:
>On Wed, May 13, 2009 at 5:01 AM, Jonas Sicking <jonas at sicking.cc> wrote:
>> On Sun, May 10, 2009 at 6:56 PM, David Singer <singer at apple.com> wrote:
>>> At 14:09 +1000 9/05/09, Silvia Pfeiffer wrote:
>>>> Of course none of the
>>>> discussion will inherently disallow seeking - scripts will always be
>>>> able to do the seeking. But the user may not find it easy to do
>>>> seeking to a section that is not accessible through the displayed
>>>> timeline, which can be both a good and a bad thing.
>>> How easy a particular user interface is to use for various tasks
>>>is (I hope)
>>> not our worry...
>> I'm not sure I agree. If the spec provides a feature set that no one
>> is able to create a useful UI for, then there definitely might be a
>> problem with the spec.
>> I still have not received any comments on my previous assertion that
>> there are essentially two separate use cases here. One for bringing
>> attention to a specific point in a larger context, one for showing
>> only a smaller range of a video.
>Just to confirm: yes, there are two separate use cases. (I was under
>the impression that the discussion had brought that out).
Yes, that's fine. I think it's clear that we could have a 'verb' in
the fragment "focus-on", "select" etc. to indicate that. I think
it's also clear that no matter what verb is used, the entire resource
is 'available' to the UA, that scripts can (if they wish) navigate
anywhere in the entire resource, and that UAs can optimize the
interface for the given verb, but the interface can still permit
access to the entire resource.
Multimedia Standards, Apple Inc.
More information about the whatwg