Remove comments from spec and open bug reports instead.

Author: dirkschulze

css3-transforms/ChangeLog

@@ -1,3 +1,6 @@
+2012-10-18 dschulze@adobe.com
+    Remove comments from spec and open bug reports instead.
+
 2012-10-18 dschulze@adobe.com
     Fix typo in pseudo code.
     https://www.w3.org/Bugs/Public/show_bug.cgi?id=18961

css3-transforms/Overview.html

@@ -429,8 +429,7 @@ <h2 id=module-interactions><span class=secno>2. </span>Module Interactions</h2>
    class=property><a
    href="http://www.w3.org/TR/css3-background/#the-background-attachment">background-attachment</a></code></code>’
    property, which is specified in <a href="#CSS3BG"
-   rel=biblioentry>[CSS3BG]<!--{{!CSS3BG}}--></a>.</p>
-  <!-- Probably need more here. -->
+   rel=biblioentry>[CSS3BG]<!--{{!CSS3BG}}--></a>.
 
   <h2 id=css-values><span class=secno>3. </span>CSS Values</h2>
 
@@ -630,7 +629,8 @@ <h2 id=two-dimensional-subset><span class=secno>5. </span> Two Dimensional
 
   <h2 id=transform-rendering><span class=secno>6. </span>The Transform
    Rendering Model</h2>
-  <!-- This section is normative -->
+
+  <p class=note>This section is normative.
 
   <p> Specifying a value other than ‘<code class=css>none</code>’ for the
    ‘<a href="#effects"><code class=css>transform</code></a>’ property
@@ -744,7 +744,6 @@ <h2 id=transform-rendering><span class=secno>6. </span>The Transform
     &lt;/div&gt;
 &lt;/div&gt;</pre>
   </div>
-  <!-- This "in the HTML namespace" is awkward. Is there a better way? -->
 
   <p> In the HTML namespace, the transform property does not affect the flow
    of the content surrounding the transformed element. However, the extent of
@@ -790,8 +789,6 @@ <h2 id=transform-rendering><span class=secno>6. </span>The Transform
 
   <h3 id=transform-3d-rendering><span class=secno>6.1. </span>3D Transform
    Rendering</h3>
-  <!-- Maybe define "tranform container" in the definitions, and use it everywhere
-              in place of "containing block"? I'm not sure if "containing block" is exactly right. -->
 
   <p> Normally, elements render as flat planes, and are rendered into the
    same plane as their containing block. Often this is the plane shared by
@@ -882,7 +879,7 @@ <h3 id=transform-3d-rendering><span class=secno>6.1. </span>3D Transform
 
   <p id=perspective-matrix-computation> The <a
    href="#TermPerspectiveMatrix"><i>perspective matrix</i></a> is computed as
-   follows: <!-- Make this more mathy, with matrices? -->
+   follows:
 
   <ol>
    <li>Start with the identity matrix.
@@ -961,7 +958,6 @@ <h3 id=transform-3d-rendering><span class=secno>6.1. </span>3D Transform
    establishes the <a class=term href="#d-rendering-context">3D rendering
    context</a> through each element that is a containing block for the given
    element, as described below.
-   <!-- More detail required, probably with matrices -->
 
   <div class=example>
    <pre>
@@ -1052,7 +1048,6 @@ <h3 id=transform-3d-rendering><span class=secno>6.1. </span>3D Transform
      <li>apply to the accumulated matrix a translation equivalent to the
       horizontal and vertical offset of the element relative to its
       containing block as specified by the CSS visual formatting model.
-      <!-- (tighten this!) -->
 
      <li>multiply the accumulated matrix with the <a class=term
       href="#transformation-matrix">transformation matrix</a>.
@@ -1265,9 +1260,8 @@ <h3 id=processing-of-perspective-transformed-boxes><span class=secno>6.2.
     sent very far away. The radial gradient is stretched over the whole box,
     now enormous, so the part that's visible without scrolling should be the
     color of the middle pixel: yellow. However, since the box is not actually
-    infinite, the user can still scroll to the edges to see the blue parts.</p>
-   <!-- TODO: Maybe we should specify that the whole thing is
-                yellow here somehow?  Doesn't seem worth it. --></div>
+    infinite, the user can still scroll to the edges to see the blue parts.
+  </div>
 
   <div class=example>
    <pre>&lt;style&gt;
@@ -1531,8 +1525,7 @@ <h2 id=transform-style-property><span class=secno>9. </span> The ‘<a
     ‘<code class=css>1</code>’.
 
    <li>‘<code class=property>filter</code>’: any value other than
-    ‘<code class=css>none</code>’.</li>
-   <!-- Others? -->
+    ‘<code class=css>none</code>’.
   </ul>
 
   <div class=issue>
@@ -1707,15 +1700,14 @@ <h2 id=backface-visibility-property><span class=secno>12. </span> The ‘<a
    whether or not the "back" side of a transformed element is visible when
    facing the viewer. With an identity transform, the front side of an
    element faces the viewer. Applying a rotation about Y of 180 degrees (for
-   instance) would cause the back side of the element to face the viewer.</p>
-  <!-- This should not be in a normative section. -->
-
-  <p> This property is useful when you place two elements back-to-back, as
-   you would to create a playing card. Without this property, the front and
-   back elements could switch places at times during an animation to flip the
-   card. Another example is creating a box out of 6 elements, but where you
-   want to see the inside faces of the box. This is useful when creating the
-   backdrop for a 3 dimensional stage.
+   instance) would cause the back side of the element to face the viewer.
+
+  <p class=note> Note that this property is useful when you place two
+   elements back-to-back, as you would to create a playing card. Without this
+   property, the front and back elements could switch places at times during
+   an animation to flip the card. Another example is creating a box out of 6
+   elements, but where you want to see the inside faces of the box. This is
+   useful when creating the backdrop for a 3 dimensional stage.
 
   <table class=propdef>
    <tbody>

css3-transforms/Transforms.src.html

@@ -161,7 +161,6 @@ <h2 id="module-interactions">Module Interactions</h2>
             '<code class="property"><a href="http://www.w3.org/TR/css3-background/#the-background-attachment">background-attachment</a></code>' property,
             which is specified in [[!CSS3BG]].
           </p>
-          <!-- Probably need more here. -->
 
         <h2 id="css-values">CSS Values</h2>
 
@@ -340,7 +339,7 @@ <h2 id="two-dimensional-subset">
           <!-- ======================================================================================================= -->
 
           <h2 id="transform-rendering">The Transform Rendering Model</h2>
-            <!-- This section is normative -->
+            <p class="note">This section is normative.</p>
             <p>
               Specifying a value other than ''none'' for the ''transform'' property establishes a
               new <span class="term">local coordinate system</span> at the element that it is
@@ -447,7 +446,6 @@ <h2 id="transform-rendering">The Transform Rendering Model</h2>
 &lt;/div&gt;</pre>
               </div>
 
-              <!-- This "in the HTML namespace" is awkward. Is there a better way? -->
               <p>
                 In the HTML namespace, the transform property does not affect the flow of the
                 content surrounding the transformed element. However, the extent of the overflow
@@ -490,8 +488,6 @@ <h2 id="transform-rendering">The Transform Rendering Model</h2>
 
               <h3 id="transform-3d-rendering">3D Transform Rendering</h3>
 
-              <!-- Maybe define "tranform container" in the definitions, and use it everywhere
-              in place of "containing block"? I'm not sure if "containing block" is exactly right. -->
               <p>
                 Normally, elements render as flat planes, and are rendered into the same plane
                 as their containing block. Often this is the plane shared by the rest of the page.
@@ -578,7 +574,6 @@ <h3 id="transform-3d-rendering">3D Transform Rendering</h3>
 
               <p id="perspective-matrix-computation">
                 The <a href="#TermPerspectiveMatrix"><i>perspective matrix</i></a> is computed as follows:
-                <!-- Make this more mathy, with matrices? -->
                 <ol>
                   <li>Start with the identity matrix.</li>
                   <li>Translate by the computed X and Y values of 'perspective-origin'</li>
@@ -638,7 +633,6 @@ <h3 id="transform-3d-rendering">3D Transform Rendering</h3>
                 space is determined by accumulating the transformation matrices
                 up from the element that establishes the <span class="term">3D rendering context</span>
                 through each element that is a containing block for the given element, as described below.
-                <!-- More detail required, probably with matrices -->
               </p>
 
               <div class="example">
@@ -711,7 +705,7 @@ <h3 id="transform-3d-rendering">3D Transform Rendering</h3>
                       on the element's containing block (if any). That containing block is not necessarily a member
                       of the 3D rendering context.</li>
                     <li>apply to the accumulated matrix a translation equivalent to the horizontal and vertical offset of the element relative to
-                      its containing block as specified by the CSS visual formatting model. <!-- (tighten this!) --></li>
+                      its containing block as specified by the CSS visual formatting model.</li>
                     <li>multiply the accumulated matrix with the <span class="term">transformation matrix</span>.</li>
                   </ol>
                 </li>
@@ -951,9 +945,6 @@ <h3 id="processing-of-perspective-transformed-boxes">
                   not actually infinite, the user can still scroll to the edges
                   to see the blue parts.
                 </p>
-
-                <!-- TODO: Maybe we should specify that the whole thing is
-                yellow here somehow?  Doesn't seem worth it. -->
               </div>
 
               <div class="example">
@@ -1310,7 +1301,6 @@ <h2 id="transform-style-property">
                   <li>'overflow': any value other than ''visible''.</li>
                   <li>'opacity': any value other than ''1''.</li>
                   <li>'filter': any value other than ''none''.</li>
-                  <!-- Others? -->
                 </ul>
 
               <div class="issue">
@@ -1536,9 +1526,8 @@ <h2 id="backface-visibility-property">
                 degrees (for instance) would cause the back side of the element to face
                 the viewer.
               </p>
-              <!-- This should not be in a normative section. -->
-              <p>
-                This property is useful when you place two elements back-to-back, as you
+              <p class="note">
+                Note that this property is useful when you place two elements back-to-back, as you
                 would to create a playing card. Without this property, the front and
                 back elements could switch places at times during an animation to flip
                 the card. Another example is creating a box out of 6 elements, but where