Browse files

[] (0) Remove the sections on audio and video codecs, since no soluti…

…on is forthcoming.

git-svn-id: http://svn.whatwg.org/webapps@3342 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent 7d34d18 commit 1dfc0e2874af666cd1561585c15864965b38fad3 @Hixie Hixie committed Jun 30, 2009
Showing with 33 additions and 39 deletions.
  1. +22 −27 index
  2. +11 −12 source
View
49 index
@@ -67,7 +67,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
- <h2 class="no-num no-toc" id=draft-standard-&mdash;-date:-01-jan-1901>Draft Standard &mdash; 29 June 2009</h2>
+ <h2 class="no-num no-toc" id=draft-standard-&mdash;-date:-01-jan-1901>Draft Standard &mdash; 30 June 2009</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -408,12 +408,8 @@
<li><a href=#the-embed-element><span class=secno>4.8.4 </span>The <code>embed</code> element</a></li>
<li><a href=#the-object-element><span class=secno>4.8.5 </span>The <code>object</code> element</a></li>
<li><a href=#the-param-element><span class=secno>4.8.6 </span>The <code>param</code> element</a></li>
- <li><a href=#video><span class=secno>4.8.7 </span>The <code>video</code> element</a>
- <ol>
- <li><a href=#video-and-audio-codecs-for-video-elements><span class=secno>4.8.7.1 </span>Video and audio codecs for <code>video</code> elements</a></ol></li>
- <li><a href=#audio><span class=secno>4.8.8 </span>The <code>audio</code> element</a>
- <ol>
- <li><a href=#audio-codecs-for-audio-elements><span class=secno>4.8.8.1 </span>Audio codecs for <code>audio</code> elements</a></ol></li>
+ <li><a href=#video><span class=secno>4.8.7 </span>The <code>video</code> element</a></li>
+ <li><a href=#audio><span class=secno>4.8.8 </span>The <code>audio</code> element</a></li>
<li><a href=#the-source-element><span class=secno>4.8.9 </span>The <code>source</code> element</a></li>
<li><a href=#media-elements><span class=secno>4.8.10 </span>Media elements</a>
<ol>
@@ -19557,34 +19553,28 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
- <div class=impl>
+ <!--CODECS
- <h5 id=video-and-audio-codecs-for-video-elements><span class=secno>4.8.7.1 </span>Video and audio codecs for <code><a href=#video>video</a></code> elements</h5>
+ <div class="impl">
+
+ <h5>Video and audio codecs for <code>video</code> elements</h5>
<p>User agents may support any video and audio codecs and container
formats.</p>
- <p class=XXX>It would be helpful for interoperability if all
- browsers could support the same codecs. However, there are no known
- codecs that satisfy all the current players: we need a codec that is
- known to not require per-unit or per-distributor licensing, that is
- compatible with the open source development model, that is of
- sufficient quality as to be usable, and that is not an additional
- submarine patent risk for large companies. This is an ongoing issue
- and this section will be updated once more information is
- available.</p>
-
- <p class=note>Certain user agents might support no codecs at all,
+ <p class="note">Certain user agents might support no codecs at all,
e.g. text browsers running over SSH connections.</p>
- <!-- similar note in audio codecs section -->
- <p class=note>Implementations are free to implement support for
+ <!- - similar note in audio codecs section - ->
+ <p class="note">Implementations are free to implement support for
video codecs either natively, or using platform-specific APIs, or
using plugins: this specification does not specify how codecs are to
be implemented.</p>
</div>
+ (when replacing this text, also fix "- -" nested comments)-->
+
@@ -19674,26 +19664,31 @@ interface <dfn id=htmlaudioelement>HTMLAudioElement</dfn> : <a href=#htmlmediael
- <div class=impl>
+ <!--CODECS
+
+ <div class="impl">
- <h5 id=audio-codecs-for-audio-elements><span class=secno>4.8.8.1 </span>Audio codecs for <code><a href=#audio>audio</a></code> elements</h5>
+ <h5>Audio codecs for <code>audio</code> elements</h5>
<p>User agents may support any audio codecs and container
formats.</p>
<p>User agents must support the WAVE container format with audio
encoded using the 16 bit PCM (LE) codec, at sampling frequencies of
11.025kHz, 22.050kHz, and 44.100kHz, and for both mono and
- stereo. <a href=#refsWAVE>[WAVE]</a></p>
+ stereo. <a href="#refsWAVE">[WAVE]</a></p>
- <!-- similar note in video codecs section -->
- <p class=note>Implementations are free to implement support for
+ <!- - similar note in video codecs section - ->
+ <p class="note">Implementations are free to implement support for
audio codecs either natively, or using platform-specific APIs, or
using plugins: this specification does not specify how codecs are to
be implemented.</p>
</div>
+ (when replacing this text, also fix "- -" nested comments)-->
+
+
<h4 id=the-source-element><span class=secno>4.8.9 </span>The <dfn><code>source</code></dfn> element</h4>
View
23 source
@@ -20933,34 +20933,28 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
+ <!--CODECS
+
<div class="impl">
<h5>Video and audio codecs for <code>video</code> elements</h5>
<p>User agents may support any video and audio codecs and container
formats.</p>
- <p class="XXX">It would be helpful for interoperability if all
- browsers could support the same codecs. However, there are no known
- codecs that satisfy all the current players: we need a codec that is
- known to not require per-unit or per-distributor licensing, that is
- compatible with the open source development model, that is of
- sufficient quality as to be usable, and that is not an additional
- submarine patent risk for large companies. This is an ongoing issue
- and this section will be updated once more information is
- available.</p>
-
<p class="note">Certain user agents might support no codecs at all,
e.g. text browsers running over SSH connections.</p>
- <!-- similar note in audio codecs section -->
+ <!- - similar note in audio codecs section - ->
<p class="note">Implementations are free to implement support for
video codecs either natively, or using platform-specific APIs, or
using plugins: this specification does not specify how codecs are to
be implemented.</p>
</div>
+ (when replacing this text, also fix "- -" nested comments)-->
+
@@ -21071,6 +21065,8 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {
+ <!--CODECS
+
<div class="impl">
<h5>Audio codecs for <code>audio</code> elements</h5>
@@ -21083,14 +21079,17 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {
11.025kHz, 22.050kHz, and 44.100kHz, and for both mono and
stereo. <a href="#refsWAVE">[WAVE]</a></p>
- <!-- similar note in video codecs section -->
+ <!- - similar note in video codecs section - ->
<p class="note">Implementations are free to implement support for
audio codecs either natively, or using platform-specific APIs, or
using plugins: this specification does not specify how codecs are to
be implemented.</p>
</div>
+ (when replacing this text, also fix "- -" nested comments)-->
+
+
<h4>The <dfn><code>source</code></dfn> element</h4>

0 comments on commit 1dfc0e2

Please sign in to comment.