Skip to content
Permalink
Browse files

[e] (0) update comment for recent changes

git-svn-id: http://svn.whatwg.org/webapps@5985 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Apr 11, 2011
1 parent f98ebb3 commit 5d6eb6b5d11f9f9d5b3cc9c49b5536d820443b2f
Showing with 21 additions and 33 deletions.
  1. +7 −11 complete.html
  2. +7 −11 index
  3. +7 −11 source
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-->

18 index
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-->

18 source
@@ -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-->

0 comments on commit 5d6eb6b

Please sign in to comment.