[html5] r3687 - [gow] (2) Various consistency and editorial fixes for media elements.
whatwg at whatwg.org
whatwg at whatwg.org
Thu Aug 27 19:11:43 PDT 2009
Author: ianh
Date: 2009-08-27 19:11:42 -0700 (Thu, 27 Aug 2009)
New Revision: 3687
Modified:
index
source
Log:
[gow] (2) Various consistency and editorial fixes for media elements.
Modified: index
===================================================================
--- index 2009-08-28 02:06:30 UTC (rev 3686)
+++ index 2009-08-28 02:11:42 UTC (rev 3687)
@@ -21499,7 +21499,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>
@@ -21791,11 +21791,25 @@
</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>
<li><p>Set the <code title=dom-media-networkState><a href=#dom-media-networkstate>networkState</a></code> attribute to
@@ -22089,7 +22103,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>
@@ -22899,17 +22913,13 @@
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>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>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
audio, and for seeking), user interface features exposed by the user
Modified: source
===================================================================
--- source 2009-08-28 02:06:30 UTC (rev 3686)
+++ source 2009-08-28 02:11:42 UTC (rev 3687)
@@ -23258,7 +23258,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>
@@ -23620,11 +23620,27 @@
title="concept-task">task</span> as part of <span
title="fetch">fetching</span> the <span>media resource</span>
(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 <span>media resource</span>, 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 <span title="ended playback">playback has
+ ended</span>, because there is always the chance the user will
+ seek back to the start. In fact, in this situation, once <span
+ title="ended playback">playback has ended</span>, the user agent
+ will end up dispatching a <code
+ title="event-stalled">stalled</code> event, as described
+ earlier.</p>
+
</li>
<li><p>Set the <code
@@ -23955,7 +23971,7 @@
having data for at least the current frame and the next frame. The
user agent cannot be in this state if <span title="ended
playback">playback has ended</span>, as the <span>current playback
- position</span> can never advanced in this case.</dd>
+ position</span> can never advance in this case.</dd>
<dt><dfn title="dom-media-HAVE_ENOUGH_DATA"><code>HAVE_ENOUGH_DATA</code></dfn> (numeric value 4)</dt>
@@ -24907,17 +24923,13 @@
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>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 <span>media element</span>'s
+ context menu.</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 <span>media
- element</span>'s context menu.</p>
-
<p>Where possible (specifically, for starting, stopping, pausing,
and unpausing playback, for muting or changing the volume of the
audio, and for seeking), user interface features exposed by the user
More information about the Commit-Watchers
mailing list