[html5] r5985 - [e] (0) update comment for recent changes

whatwg at whatwg.org whatwg at whatwg.org
Mon Apr 11 16:38:52 PDT 2011


Author: ianh
Date: 2011-04-11 16:38:51 -0700 (Mon, 11 Apr 2011)
New Revision: 5985

Modified:
   complete.html
   index
   source
Log:
[e] (0) update comment for recent changes

Modified: complete.html
===================================================================
--- complete.html	2011-04-11 23:34:51 UTC (rev 5984)
+++ complete.html	2011-04-11 23:38:51 UTC (rev 5985)
@@ -1374,18 +1374,14 @@
         higher numbers. These indicate ideas for future versions of
         the specification that have not yet been included, usually
         because it's too early (one has to move slowly lest the
-        browser vendors get overwhelmed with changes). --><!-- Finally, there are also a number of known issues in this
+        browser vendors get overwhelmed with changes). --><!-- Finally, there may also be some known issues in this
         specification marked with the following punctuation: --><!--!--><!-- These are issues that are known to the editor but cannot be
-        currently fixed because they were introduced by Sam Ruby
-        acting as chairman of the W3C HTML Working Group as part of
-        the HTML Working Group Decision Process. (Maciej wants it to
-        be known he also accepts responsibility for this decision, as
-        he was supposed to review it.) In theory we could fork the
-        WHATWG copy of the spec, but doing so would introduce
-        normative differences between the W3C and WHATWG specs and
-        these issues are not worth the hassle that this would cause.
-        We'll probably be able to fix them some day, but for now we
-        are living with them. --><h2 id=introduction><span class=secno>1 </span>Introduction</h2>
+        currently fixed because they were introduced by W3C decisions.
+        In theory we could fork the WHATWG copy of the spec, but doing
+        so would introduce normative differences between the W3C and
+        WHATWG specs and these issues are not worth the hassle that
+        this would cause. We'll probably be able to fix them some day,
+        but for now we are living with them. --><h2 id=introduction><span class=secno>1 </span>Introduction</h2>
 
 <!--VERSION-->
 

Modified: index
===================================================================
--- index	2011-04-11 23:34:51 UTC (rev 5984)
+++ index	2011-04-11 23:38:51 UTC (rev 5985)
@@ -1301,18 +1301,14 @@
         higher numbers. These indicate ideas for future versions of
         the specification that have not yet been included, usually
         because it's too early (one has to move slowly lest the
-        browser vendors get overwhelmed with changes). --><!-- Finally, there are also a number of known issues in this
+        browser vendors get overwhelmed with changes). --><!-- Finally, there may also be some known issues in this
         specification marked with the following punctuation: --><!--!--><!-- These are issues that are known to the editor but cannot be
-        currently fixed because they were introduced by Sam Ruby
-        acting as chairman of the W3C HTML Working Group as part of
-        the HTML Working Group Decision Process. (Maciej wants it to
-        be known he also accepts responsibility for this decision, as
-        he was supposed to review it.) In theory we could fork the
-        WHATWG copy of the spec, but doing so would introduce
-        normative differences between the W3C and WHATWG specs and
-        these issues are not worth the hassle that this would cause.
-        We'll probably be able to fix them some day, but for now we
-        are living with them. --><h2 id=introduction><span class=secno>1 </span>Introduction</h2>
+        currently fixed because they were introduced by W3C decisions.
+        In theory we could fork the WHATWG copy of the spec, but doing
+        so would introduce normative differences between the W3C and
+        WHATWG specs and these issues are not worth the hassle that
+        this would cause. We'll probably be able to fix them some day,
+        but for now we are living with them. --><h2 id=introduction><span class=secno>1 </span>Introduction</h2>
 
 <!--VERSION-->
 

Modified: source
===================================================================
--- source	2011-04-11 23:34:51 UTC (rev 5984)
+++ source	2011-04-11 23:38:51 UTC (rev 5985)
@@ -28,22 +28,18 @@
         because it's too early (one has to move slowly lest the
         browser vendors get overwhelmed with changes). -->
 
-   <!-- Finally, there are also a number of known issues in this
+   <!-- Finally, there may also be some known issues in this
         specification marked with the following punctuation: -->
 
            <!--!-->
 
    <!-- These are issues that are known to the editor but cannot be
-        currently fixed because they were introduced by Sam Ruby
-        acting as chairman of the W3C HTML Working Group as part of
-        the HTML Working Group Decision Process. (Maciej wants it to
-        be known he also accepts responsibility for this decision, as
-        he was supposed to review it.) In theory we could fork the
-        WHATWG copy of the spec, but doing so would introduce
-        normative differences between the W3C and WHATWG specs and
-        these issues are not worth the hassle that this would cause.
-        We'll probably be able to fix them some day, but for now we
-        are living with them. -->
+        currently fixed because they were introduced by W3C decisions.
+        In theory we could fork the WHATWG copy of the spec, but doing
+        so would introduce normative differences between the W3C and
+        WHATWG specs and these issues are not worth the hassle that
+        this would cause. We'll probably be able to fix them some day,
+        but for now we are living with them. -->
 
 <!--START w3c-html-->
 




More information about the Commit-Watchers mailing list