[Bug 12425] New: User interface of temporal media fragment URI in @src of video element

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12425

           Summary: User interface of temporal media fragment URI in @src
                    of video element
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: silviapfeiffer1@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Problem: what is a browser expected to display in @controls when a <video> or
<audio> element loads a media resource with a media fragment

Proposal: The browser will play the resource from the fragment start time to
the fragment end time and pauses at the end time. It further displays the time
segment on the timeline of the @controls in a suitable manner as part of the
full video's timeline. If the user hits "play" at the end of the fragment
playback, playback will continue past the end of the playback until it reaches
the end of the resource or another user interaction occurs.

The change should be made to
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#user-interface
where it should be added to recommendations of what browsers should expose when
a @controls attribute is present.

Note: Browsers should do the same thing when users navigate directly to a audio
or video resource that includes a temporal media fragment specification. Even
though this is a browser issue and therefore out of scope of this bug, it is
still important to understand that this is a consistency issue and should be
handled by user agents the same way everywhere.

-- 
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 Tuesday, 5 April 2011 21:52:30 UTC