Temporarily removed image-rendering:pixelated at Chair request until WG has talked about it.

Author: tabatkins

css3-images/Overview.html

@@ -1961,7 +1961,7 @@ <h3 id=image-rendering><span class=secno>7.3. </span> Determining How to
     <tr>
      <th>Value:
 
-     <td>auto | crisp-edges | pixelated
+     <td>auto | crisp-edges<!-- | pixelated -->
 
     <tr>
      <th>Initial:
@@ -2034,19 +2034,13 @@ <h3 id=image-rendering><span class=secno>7.3. </span> Determining How to
      algorithm described in this SIGGRAPH paper</a>. When downscaling an
      image, algorithms such as nearest-neighbor or bilinear interpolation are
      acceptable.</p>
-
-   <dt><dfn id=pixelated>pixelated</dfn>
-
-   <dd>
-    <p>The image should be scaled with an algorithm that preserves a
-     "pixelated" look. This is intended for images such as pixel art.</p>
-
-    <p>If the image is upscaled an integer multiple of its original size, it
-     must be scaled with the nearest-neighbor algorithm. When upscaled by any
-     other factor, nearest-neighbor is acceptable, as are other algorithms
-     that preserve a pixelated look. When downscaling an image, any algorithm
-     that preserves a pixelated look are acceptable, such as nearest-neighbor
-     or bilinear interpolation.</p>
+   </dd>
+   <!--<dt><dfn>pixelated</dfn></dt>
+		<dd>
+			<p>The image should be scaled with an algorithm that preserves a "pixelated" look.  This is intended for images such as pixel art.</p>
+
+			<p>If the image is upscaled an integer multiple of its original size, it must be scaled with the nearest-neighbor algorithm.  When upscaled by any other factor, nearest-neighbor is acceptable, as are other algorithms that preserve a pixelated look.  When downscaling an image, any algorithm that preserves a pixelated look are acceptable, such as nearest-neighbor or bilinear interpolation.</p>
+		</dd>-->
   </dl>
 
   <p>This property does <em>not</em> dictate any particular scaling algorithm

css3-images/Overview.src.html

@@ -1471,7 +1471,7 @@ <h3 id='image-rendering'>
 			<td><dfn>image-rendering</dfn>
 		<tr>
 			<th>Value:
-			<td>auto | crisp-edges | pixelated
+			<td>auto | crisp-edges<!-- | pixelated -->
 		<tr>
 			<th>Initial:
 			<td>auto
@@ -1506,12 +1506,12 @@ <h3 id='image-rendering'>
 			<p>For example, when upscaling an image, algorithms such as nearest-neighbor are acceptable, as are specialized pixel-art scaling algorithms like EPX or <a href="http://research.microsoft.com/en-us/um/people/kopf/pixelart/">the algorithm described in this SIGGRAPH paper</a>.  When downscaling an image, algorithms such as nearest-neighbor or bilinear interpolation are acceptable.</p>
 		</dd>
 
-		<dt><dfn>pixelated</dfn></dt>
+		<!--<dt><dfn>pixelated</dfn></dt>
 		<dd>
 			<p>The image should be scaled with an algorithm that preserves a "pixelated" look.  This is intended for images such as pixel art.</p>
 
 			<p>If the image is upscaled an integer multiple of its original size, it must be scaled with the nearest-neighbor algorithm.  When upscaled by any other factor, nearest-neighbor is acceptable, as are other algorithms that preserve a pixelated look.  When downscaling an image, any algorithm that preserves a pixelated look are acceptable, such as nearest-neighbor or bilinear interpolation.</p>
-		</dd>
+		</dd>-->
 	</dl>
 
 	<p>This property does <em>not</em> dictate any particular scaling algorithm to be used.  For example, with ''image-rendering:auto'', a user agent might scale images with bilinear interpolation by default, switch to nearest-neighbor interpolation in high-load situations, and switch to a high-quality scaling algorithm like Lanczos interpolation for static images that aren't moving or changing.  Similarly, with ''image-rendering:crisp-edges'', a user agent might scale images with nearest-neighbor interpolation by default, and switch to EPX interpolation in low-load situations.</p>