- From: poot <cvsmail@w3.org>
- Date: Wed, 9 Jul 2008 11:14:25 +0900 (JST)
- To: public-html-diffs@w3.org
1.1043 Clarify that 'pixelratio' doesn't affect later <source> elements;
clarify that load() doesn't wait for earlier invocations to abort. (Re:
HTMLMediaElement: more issues and ambiguities) (credit: pj) (whatwg
r1854) (changed by: Michael Smith)
Diffs for this change per section:
http://people.w3.org/mike/diffs/html5/pubnotes/Overview.1.301.html#status
http://people.w3.org/mike/diffs/html5/pubnotes/Overview.1.301.html#media_wd2
http://people.w3.org/mike/diffs/html5/pubnotes/Overview.1.301.html#abstract
http://people.w3.org/mike/diffs/html5/pubnotes/Overview.1.301.html#relationship0_wd2
Current content per affected section:
http://dev.w3.org/html5/pubnotes/Overview.html#status
http://dev.w3.org/html5/pubnotes/Overview.html#media_wd2
http://dev.w3.org/html5/pubnotes/Overview.html#abstract
http://dev.w3.org/html5/pubnotes/Overview.html#relationship0_wd2
Previously published WD content per affected section:
http://www.w3.org/TR/2008/WD-html5-20080610/single-page/#status
http://www.w3.org/TR/2008/WD-html5-20080610/single-page/#media_wd2
http://www.w3.org/TR/2008/WD-html5-20080610/single-page/#abstract
http://www.w3.org/TR/2008/WD-html5-20080610/single-page/#relationship0_wd2
Cumulative diff: http://people.w3.org/mike/diffs/html5/pubnotes/Overview.diff.html
http://dev.w3.org/cvsweb/html5/pubnotes/Overview.html?r1=1.300&r2=1.301&f=h
http://html5.org/tools/web-apps-tracker?from=1853&to=1854
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.html,v
retrieving revision 1.300
retrieving revision 1.301
diff -u -d -r1.300 -r1.301
--- Overview.html 9 Jul 2008 01:59:46 -0000 1.300
+++ Overview.html 9 Jul 2008 02:13:25 -0000 1.301
@@ -42,7 +42,7 @@
specification itself or to read through the entire diff
document that shows all the changes..</p>
<div class="ednote"><h4 class="ednoteHeader">Editorial note</h4><p>This document was generated on
- <b>2008-07-09T10:57:37+09:00</b>.</p></div></div>
+ <b>2008-07-09T11:10:23+09:00</b>.</p></div></div>
<div id="status">
<h2>Status of this Document</h2>
<p><em>
@@ -1297,7 +1297,9 @@
<p>In this section, the following changes were made:</p>
<ul>
<li>In the “Loading the media resource”
- subsection, a statement regarding the
+ subsection, the following changes were made:
+ <ul>
+ <li>a statement regarding the
<code class="domattribute">buffered</code>
attribute was updated to read (changed text
highlighted), <q>The buffered attribute must
@@ -1316,28 +1318,59 @@
attribute is evaluated</q>, and the following
statement was added: <q>User agents may discard
previously buffered data</q>.</li>
- <li>Also in the “Loading the media resource”
- subsection, the following note was added: <q>Thus,
+ <li>The following note was added: <q>Thus,
a time or byte position included within a range
of the objects return by the buffered or
bufferedBytes attributes at one time can end
up being not included in the range(s) of objects
returned by the same attributes at a later
time.</q></li>
- <li>Also in the “Loading the media resource”, a
+ <li>A
step in the algorithm that user agents must run
when the
<code class="method">load()</code>
method
is invoked on a media element was revised to now
- read (added text highlighted): <q>The user agent
+ read (added text highlighted):
+ <q>The user agent
must then set the begun flag to true and
<em class="highlight">synchronously</em> fire a
progress event called loadstart at the media
element.</q></li>
+ <li>A
+ step in the algorithm that user agents must run
+ when the
+ <code class="method">load()</code>
+ method
+ is invoked on a media element was revised to now
+ read (added text highlighted): <q>Any
+ already-running instance of this algorithm for
+ this element must be aborted. If those method
+ calls have not yet returned, they must finish
+ the step they are on, and then immediately
+ return. <em class="highlight">This is not
+ blocking; this algorithm must not wait for the
+ earlier instances to abort before
+ continuing.</em></q></li>
+ </ul>
+ </li>
<li>In the “Location of the media resource”
- subsection, text was added to define the <q>pixel
+ subsection, the following changes were made:
+ <ul>
+ <li>Text was added to define the <q>pixel
ratio override</q> of a media resource.</li>
+ <li>A step in the algorithm for picking a media
+ resource for a media element was revised to now
+ read (added text highlighted: <q>If candidate is
+ not null and it has a pixelratio attribute,
+ and the result of applying the rules for
+ parsing floating point number values to the
+ value of that attribute is not an error, then
+ let the chosen resource’s pixel ratio override
+ be that result. result; <em class="highlight">otherwise, reset it back to
+ none.</em></q></li>
+ </ul>
+ </li>
<li>In the “Offsets into the media resource”
subsection, the introduction to an algorithm was
updated to now read (added text highlighted):
Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.src.html,v
retrieving revision 1.286
retrieving revision 1.287
diff -u -d -r1.286 -r1.287
--- Overview.src.html 9 Jul 2008 01:59:46 -0000 1.286
+++ Overview.src.html 9 Jul 2008 02:13:25 -0000 1.287
@@ -582,7 +582,9 @@
<p>In this section, the following changes were made:</p>
<ul>
<li>In the “Loading the media resource”
- subsection, a statement regarding the
+ subsection, the following changes were made:
+ <ul>
+ <li>a statement regarding the
<code class=domattribute>buffered</code>
attribute was updated to read (changed text
highlighted), <q>The buffered attribute must
@@ -602,28 +604,60 @@
attribute is evaluated</q>, and the following
statement was added: <q>User agents may discard
previously buffered data</q>.</li>
- <li>Also in the “Loading the media resource”
- subsection, the following note was added: <q>Thus,
+ <li>The following note was added: <q>Thus,
a time or byte position included within a range
of the objects return by the buffered or
bufferedBytes attributes at one time can end
up being not included in the range(s) of objects
returned by the same attributes at a later
time.</q></li>
- <li>Also in the “Loading the media resource”, a
+ <li>A
step in the algorithm that user agents must run
when the
<code class=method>load()</code>
method
is invoked on a media element was revised to now
- read (added text highlighted): <q>The user agent
+ read (added text highlighted):
+ <q>The user agent
must then set the begun flag to true and
<em class=highlight>synchronously</em> fire a
progress event called loadstart at the media
element.</q></li>
+ <li>A
+ step in the algorithm that user agents must run
+ when the
+ <code class=method>load()</code>
+ method
+ is invoked on a media element was revised to now
+ read (added text highlighted): <q>Any
+ already-running instance of this algorithm for
+ this element must be aborted. If those method
+ calls have not yet returned, they must finish
+ the step they are on, and then immediately
+ return. <em class=highlight>This is not
+ blocking; this algorithm must not wait for the
+ earlier instances to abort before
+ continuing.</em></q></li>
+ </ul>
+ </li>
<li>In the “Location of the media resource”
- subsection, text was added to define the <q>pixel
+ subsection, the following changes were made:
+ <ul>
+ <li>Text was added to define the <q>pixel
ratio override</q> of a media resource.</li>
+ <li>A step in the algorithm for picking a media
+ resource for a media element was revised to now
+ read (added text highlighted: <q>If candidate is
+ not null and it has a pixelratio attribute,
+ and the result of applying the rules for
+ parsing floating point number values to the
+ value of that attribute is not an error, then
+ let the chosen resource’s pixel ratio override
+ be that result. result; <em
+ class=highlight>otherwise, reset it back to
+ none.</em></q></li>
+ </ul>
+ </li>
<li>In the “Offsets into the media resource”
subsection, the introduction to an algorithm was
updated to now read (added text highlighted):
Received on Wednesday, 9 July 2008 02:15:04 UTC