[html5] r5578 - [e] (0) Remove a 'willful violation' note. Fixing http://www.w3.org/Bugs/Public/ [...]

whatwg at whatwg.org whatwg at whatwg.org
Mon Oct 4 16:36:25 PDT 2010


Author: ianh
Date: 2010-10-04 16:36:24 -0700 (Mon, 04 Oct 2010)
New Revision: 5578

Modified:
   complete.html
   index
   source
Log:
[e] (0) Remove a 'willful violation' note.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10854

Modified: complete.html
===================================================================
--- complete.html	2010-10-04 23:05:30 UTC (rev 5577)
+++ complete.html	2010-10-04 23:36:24 UTC (rev 5578)
@@ -54624,8 +54624,8 @@
 
 
    <dt>If the element is an <code><a href=#audio>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>,
-   <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>, or
-   <code><a href=#video>video</a></code> element</dt>
+   <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>,
+   <code><a href=#the-track-element>track</a></code>, or <code><a href=#video>video</a></code> element</dt>
 
    <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title="">src</code> content attribute.</dd>
 
@@ -62587,15 +62587,11 @@
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs. <a href=#refsRFC3629>[RFC3629]</a></p>
 
-  <p class=note>This is a <a href=#willful-violation>willful violation</a> of two
-  aspects of RFC 2046, which requires all <code title="">text/*</code>
-  types to support an open-ended set of character encodings and only
-  allows CRLF line breaks. These requirements, however, are outdated;
-  UTF-8 is now widely used, such that supporting other encodings is no
-  longer necessary, and use of CR, LF, and CRLF line breaks is
-  commonly supported and indeed sometimes CRLF is <em>not</em>
-  supported by text editors. <a href=#refsRFC2046>[RFC2046]</a></p>
-  <!-- also RFC 2045 for charset -->
+  <p class=note>This is a <a href=#willful-violation>willful violation</a> of RFC
+  2046, which requires all <code title="">text/*</code> types to only
+  allow CRLF line breaks. This requirement, however, is outdated; the
+  use of CR, LF, and CRLF line breaks is commonly supported and indeed
+  sometimes CRLF is <em>not</em> supported by text editors. <a href=#refsRFC2046>[RFC2046]</a></p>
 
   <p>The first line of an application cache manifest must consist of
   the string "CACHE", a single U+0020 SPACE character, the string

Modified: index
===================================================================
--- index	2010-10-04 23:05:30 UTC (rev 5577)
+++ index	2010-10-04 23:36:24 UTC (rev 5578)
@@ -54604,8 +54604,8 @@
 
 
    <dt>If the element is an <code><a href=#audio>audio</a></code>, <code><a href=#the-embed-element>embed</a></code>,
-   <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>, or
-   <code><a href=#video>video</a></code> element</dt>
+   <code><a href=#the-iframe-element>iframe</a></code>, <code><a href=#the-img-element>img</a></code>, <code><a href=#the-source-element>source</a></code>,
+   <code><a href=#the-track-element>track</a></code>, or <code><a href=#video>video</a></code> element</dt>
 
    <dd><p>The attribute must act as it would if it was <a href=#reflect title=reflect>reflecting</a> the element's <code title="">src</code> content attribute.</dd>
 
@@ -62576,15 +62576,11 @@
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs. <a href=#refsRFC3629>[RFC3629]</a></p>
 
-  <p class=note>This is a <a href=#willful-violation>willful violation</a> of two
-  aspects of RFC 2046, which requires all <code title="">text/*</code>
-  types to support an open-ended set of character encodings and only
-  allows CRLF line breaks. These requirements, however, are outdated;
-  UTF-8 is now widely used, such that supporting other encodings is no
-  longer necessary, and use of CR, LF, and CRLF line breaks is
-  commonly supported and indeed sometimes CRLF is <em>not</em>
-  supported by text editors. <a href=#refsRFC2046>[RFC2046]</a></p>
-  <!-- also RFC 2045 for charset -->
+  <p class=note>This is a <a href=#willful-violation>willful violation</a> of RFC
+  2046, which requires all <code title="">text/*</code> types to only
+  allow CRLF line breaks. This requirement, however, is outdated; the
+  use of CR, LF, and CRLF line breaks is commonly supported and indeed
+  sometimes CRLF is <em>not</em> supported by text editors. <a href=#refsRFC2046>[RFC2046]</a></p>
 
   <p>The first line of an application cache manifest must consist of
   the string "CACHE", a single U+0020 SPACE character, the string

Modified: source
===================================================================
--- source	2010-10-04 23:05:30 UTC (rev 5577)
+++ source	2010-10-04 23:36:24 UTC (rev 5578)
@@ -61250,8 +61250,8 @@
 
 
    <dt>If the element is an <code>audio</code>, <code>embed</code>,
-   <code>iframe</code>, <code>img</code>, <code>source</code>, or
-   <code>video</code> element</dt>
+   <code>iframe</code>, <code>img</code>, <code>source</code>,
+   <code>track</code>, or <code>video</code> element</dt>
 
    <dd><p>The attribute must act as it would if it was <span
    title="reflect">reflecting</span> the element's <code
@@ -70764,15 +70764,12 @@
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs. <a href="#refsRFC3629">[RFC3629]</a></p>
 
-  <p class="note">This is a <span>willful violation</span> of two
-  aspects of RFC 2046, which requires all <code title="">text/*</code>
-  types to support an open-ended set of character encodings and only
-  allows CRLF line breaks. These requirements, however, are outdated;
-  UTF-8 is now widely used, such that supporting other encodings is no
-  longer necessary, and use of CR, LF, and CRLF line breaks is
-  commonly supported and indeed sometimes CRLF is <em>not</em>
-  supported by text editors. <a href="#refsRFC2046">[RFC2046]</a></p>
-  <!-- also RFC 2045 for charset -->
+  <p class="note">This is a <span>willful violation</span> of RFC
+  2046, which requires all <code title="">text/*</code> types to only
+  allow CRLF line breaks. This requirement, however, is outdated; the
+  use of CR, LF, and CRLF line breaks is commonly supported and indeed
+  sometimes CRLF is <em>not</em> supported by text editors. <a
+  href="#refsRFC2046">[RFC2046]</a></p>
 
   <p>The first line of an application cache manifest must consist of
   the string "CACHE", a single U+0020 SPACE character, the string




More information about the Commit-Watchers mailing list