- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 14 Mar 2011 10:20:01 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv5861
Modified Files:
Overview.html
Log Message:
Completely revamp how peer-to-peer networking works (and some minor typo fixes in other parts of the spec). This is only a second draft, and therefore this feature will likely evolve a lot over the coming months. Detailed responses to feedback on the topic will be sent out soon. (whatwg r5945)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4785
retrieving revision 1.4786
diff -u -d -r1.4785 -r1.4786
--- Overview.html 5 Mar 2011 00:12:42 -0000 1.4785
+++ Overview.html 14 Mar 2011 10:19:57 -0000 1.4786
@@ -343,7 +343,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-5-march-2011">Editor's Draft 5 March 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-14-march-2011">Editor's Draft 14 March 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -485,7 +485,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 5 March 2011 Editor's Draft.
+ This specification is the 14 March 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -21479,7 +21479,7 @@
zero or more <code><a href="#the-track-element">track</a></code> elements, then
<!--KEEP-START w3c-html--><!--TT-->
<a href="#transparent">transparent</a>, but with no <a href="#media-element">media element</a> descendants.</dd>
- <dd>If the element does not have a <code title="attr-media-src"><a href="#attr-media-src">src</a></code> attribute: one or more <code><a href="#the-source-element">source</a></code> elements, then
+ <dd>If the element does not have a <code title="attr-media-src"><a href="#attr-media-src">src</a></code> attribute: zero or more <code><a href="#the-source-element">source</a></code> elements, then
<!--KEEP-END w3c-html--><!--TT-->
zero or more <code><a href="#the-track-element">track</a></code> elements, then
<!--KEEP-START w3c-html--><!--TT-->
@@ -23787,8 +23787,8 @@
<a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple event</a>
named <code title="event-media-playing"><a href="#event-media-playing">playing</a></code>.</p>
- <p class="note">User agents are not required to autoplay, and it
- is suggested that user agents honor user preferences on the
+ <p class="note">User agents do not need to support autoplay,
+ and it is suggested that user agents honor user preferences on the
matter. Authors are urged to use the <code title="attr-media-autoplay"><a href="#attr-media-autoplay">autoplay</a></code> attribute rather than
using script to force the video to play, so as to allow the user
to override the behavior if so desired.</p>
@@ -65253,7 +65253,7 @@
up if the user interacted with the actual image.</p>
<hr><p>All animated images with the same <a href="#absolute-url">absolute URL</a> and
- the same image data are expected to be rendered synchronised to the
+ the same image data are expected to be rendered synchronized to the
same timeline as a group, with the timeline starting at the time of
the most recent addition to the group.</p>
Received on Monday, 14 March 2011 10:20:03 UTC