- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 02 Aug 2011 20:13:42 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-images
In directory hutz:/tmp/cvs-serv690
Modified Files:
Overview.html Overview.src.html
Log Message:
Temporarily removed image-rendering:pixelated at Chair request until WG has talked about it.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.html,v
retrieving revision 1.116
retrieving revision 1.117
diff -u -d -r1.116 -r1.117
--- Overview.html 2 Aug 2011 20:11:35 -0000 1.116
+++ Overview.html 2 Aug 2011 20:13:40 -0000 1.117
@@ -1961,7 +1961,7 @@
<tr>
<th>Value:
- <td>auto | crisp-edges | pixelated
+ <td>auto | crisp-edges<!-- | pixelated -->
<tr>
<th>Initial:
@@ -2034,19 +2034,13 @@
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
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.src.html,v
retrieving revision 1.122
retrieving revision 1.123
diff -u -d -r1.122 -r1.123
--- Overview.src.html 2 Aug 2011 20:11:35 -0000 1.122
+++ Overview.src.html 2 Aug 2011 20:13:40 -0000 1.123
@@ -1471,7 +1471,7 @@
<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 @@
<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>
Received on Tuesday, 2 August 2011 20:13:47 UTC