- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 28 Aug 2009 02:10:00 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv19372
Modified Files:
Overview.html
Log Message:
Various consistency and editorial fixes for media elements. (whatwg r3687)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2865
retrieving revision 1.2866
diff -u -d -r1.2865 -r1.2866
--- Overview.html 28 Aug 2009 02:04:44 -0000 1.2865
+++ Overview.html 28 Aug 2009 02:09:56 -0000 1.2866
@@ -17586,7 +17586,7 @@
<a href="#reflect">reflect</a> the respective content attributes of the same
name.</p>
- </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs), <a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil) and <a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
+ </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil), <a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization) and <a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
<dd><a href="#flow-content">Flow content</a>.</dd>
<dd><a href="#phrasing-content">Phrasing content</a>.</dd>
<dd><a href="#embedded-content">Embedded content</a>.</dd>
@@ -18784,7 +18784,7 @@
<p>The user agent may use whatever means necessary to fetch the
resource (within the constraints put forward by this and other
specifications); for example, reconnecting to the server in the
- face of network errors, using HTTP partial range requests, or
+ face of network errors, using HTTP range retrieval requests, or
switching to a streaming protocol. The user agent must consider a
resource erroneous only if it has given up trying to fetch it.</p>
@@ -19076,10 +19076,24 @@
</dl><p>When the <a href="#networking-task-source">networking task source</a> has <a href="#queue-a-task" title="queue a task">queued</a> the last <a href="#concept-task" title="concept-task">task</a> as part of <a href="#fetch" title="fetch">fetching</a> the <a href="#media-resource">media resource</a>
(i.e. once the download has completed), if the fetching process
- completes without errors, including decoding the media data, then,
- the user agent must move on to the next step. This might never
- happen, e.g. when streaming an infinite resource such as Web
- radio.</p>
+ completes without errors, including decoding the media data, and
+ if all of the data is available to the user agent without network
+ access, then, the user agent must move on to the next step. This
+ might never happen, e.g. when streaming an infinite resource such
+ as Web radio, or if the resource is longer than the user agent's
+ ability to cache data.</p>
+
+ <p>While the user agent might still need network access to obtain
+ parts of the <a href="#media-resource">media resource</a>, the user agent must
+ remain on this step.</p>
+
+ <p class="example">For example, if the user agent has discarded
+ the first half of a video, the user agent will remain at this step
+ even once the <a href="#ended-playback" title="ended playback">playback has
+ ended</a>, because there is always the chance the user will
+ seek back to the start. In fact, in this situation, once <a href="#ended-playback" title="ended playback">playback has ended</a>, the user agent
+ will end up dispatching a <code title="event-stalled"><a href="#event-stalled">stalled</a></code> event, as described
+ earlier.</p>
</li>
@@ -19348,7 +19362,7 @@
having data for at least the current frame and the next frame. The
user agent cannot be in this state if <a href="#ended-playback" title="ended
playback">playback has ended</a>, as the <a href="#current-playback-position">current playback
- position</a> can never advanced in this case.</dd>
+ position</a> can never advance in this case.</dd>
<dt><dfn id="dom-media-have_enough_data" title="dom-media-HAVE_ENOUGH_DATA"><code>HAVE_ENOUGH_DATA</code></dfn> (numeric value 4)</dt>
@@ -20127,16 +20141,12 @@
suitable to the user (e.g. full-screen video or in an independent
resizable window). Other controls may also be made available.</p>
- <p>If the attribute is absent, then the user agent should avoid
- making a user interface available that could conflict with an
- author-provided user interface. User agents may make the following
- features available, however, even when the attribute is absent:</p>
-
- <p>User agents may provide controls to affect playback of the media
- resource (e.g. play, pause, seeking, and volume controls), but such
- features should not interfere with the page's normal rendering. For
- example, such features could be exposed in the <a href="#media-element">media
- element</a>'s context menu.</p>
+ <p>Even when the attribute is absent, however, user agents may
+ provide controls to affect playback of the media resource
+ (e.g. play, pause, seeking, and volume controls), but such features
+ should not interfere with the page's normal rendering. For example,
+ such features could be exposed in the <a href="#media-element">media element</a>'s
+ context menu.</p>
<p>Where possible (specifically, for starting, stopping, pausing,
and unpausing playback, for muting or changing the volume of the
@@ -48369,7 +48379,7 @@
<a href="#source-browsing-context">source browsing context</a>.</p>
- <h5 id="hyperlink-auditing"><span class="secno">6.12.2.1 </span><dfn>Hyperlink auditing</dfn></h5><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/63">ISSUE-63</a> (origin-req-scope), <a href="http://www.w3.org/html/wg/tracker/issues/2">ISSUE-2</a> (PINGUI) and <a href="http://www.w3.org/html/wg/tracker/issues/1">ISSUE-1</a> (PINGPOST) block progress to Last Call</span></p>
+ <h5 id="hyperlink-auditing"><span class="secno">6.12.2.1 </span><dfn>Hyperlink auditing</dfn></h5><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/63">ISSUE-63</a> (origin-req-scope), <a href="http://www.w3.org/html/wg/tracker/issues/1">ISSUE-1</a> (PINGPOST) and <a href="http://www.w3.org/html/wg/tracker/issues/2">ISSUE-2</a> (PINGUI) block progress to Last Call</span></p>
<p>If an <code><a href="#the-a-element">a</a></code> or <code><a href="#the-area-element">area</a></code> hyperlink element has a
<code title="attr-hyperlink-ping"><a href="#ping">ping</a></code> attribute, and the
Received on Friday, 28 August 2009 02:10:13 UTC