HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
1143Lift the cat who was amongst the pigeons up and put him back on his pedestal for now. (remove requirement on ogg for now)2007-12-11 02:45
@@ -607,27 +607,31 @@
     defined in this specification must implement them in a manner
     consistent with the ECMAScript Bindings for DOM Specifications
     specification, as this specification uses that specification's
     terminology. <a href="#refsEBFD">[EBFD]</a></p>
 
    </dd>
 
   </dl>
 
   <p>This specification does not require support of any particular
-  network transport protocols, image formats, audio formats, video
-  formats, style sheet language, scripting language, or any of the DOM
-  and WebAPI specifications beyond those described above. However, the
-  language described by this specification is biased towards CSS as
-  the styling language, ECMAScript as the scripting language, and HTTP
-  as the network protocol, and several features assume that those
-  languages and protocols are in use.</p>
+  network transport protocols, style sheet language, scripting
+  language, or any of the DOM and WebAPI specifications beyond those
+  described above. However, the language described by this
+  specification is biased towards CSS as the styling language,
+  ECMAScript as the scripting language, and HTTP as the network
+  protocol, and several features assume that those languages and
+  protocols are in use.</p>
+
+  <p class="note">This specification might have certain additional
+  requirements on character encodings, image formats, audio formats,
+  and video formats in the respective sections.</p>
 
 
   <h4>Features defined in other specifications</h4>
 
   <p>Some elements are defined in terms of their DOM
   <dfn><code>textContent</code></dfn> attribute. This is an attribute
   defined on the <code>Node</code> interface in DOM3 Core. <a
   href="#refsDOM3CORE">[DOM3CORE]</a></p>
 
   <p class="big-issue">Should textContent be defined differently for
@@ -11324,27 +11328,29 @@ The island of Shalott.&lt;/p></pre>
   provided to easily allow the user to obtain a full-screen playback
   mode.</p>
 
 
 
   <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>User agents should support Ogg Theora video and Ogg Vorbis audio,
-  as well as the Ogg container format. <a
-  href="#refsOggTheora">[THEORA]</a> <a
-  href="#refsOggVorbis">[VORBIS]</a> <a href="#refsOgg">[OGG]</a></p>
-  <!-- (it's not a MUST because some vendors may have legal reasons
-  why they can't or won't support it, and there's no point making them
-  non-conforming when they have no choice in the matter) -->
+  <p class="big-issue">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>
 
   <!-- XXX mention that this spec doesn't require native support or
   plugin support, either is fine -->
 
   <p class="note">Certain user agents might support no codecs at all,
   e.g. text browsers running over SSH connections.</p>
 
 
 
 

|