HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
3342Remove the sections on audio and video codecs, since no solution is forthcoming.2009-06-30 04:50
@@ -20926,48 +20926,42 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
   password. There is also the danger of "mere" annoyance, with pages
   launching full-screen videos when links are clicked or pages
   navigated. Instead, user-agent specific interface features may be
   provided to easily allow the user to obtain a full-screen playback
   mode.</p>
 
   </div>
 
 
 
+  <!--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)-->
+
 
 
 
 
   <h4 id="audio">The <dfn><code>audio</code></dfn> element</h4>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd><span>Flow content</span>.</dd>
    <dd><span>Phrasing content</span>.</dd>
@@ -21064,40 +21058,45 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {
   is present, the object created must have its <code
   title="dom-media-src">src</code> content attribute set to the
   provided value, and the user agent must invoke the object's <span
   title="concept-media-load-algorithm">resource selection
   algorithm</span> before returning.</p>
 
   </div>
 
 
 
+  <!--CODECS
+
   <div class="impl">
 
   <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>
 
-  <!-- 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>
 
   <dl class="element">
    <dt>Categories</dt>
    <dd>None.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>As a child of a <span>media element</span>, before any <span>flow content</span>.</dd>
    <dt>Content model:</dt>
    <dd>Empty.</dd>

|