- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 28 Feb 2012 23:42:54 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css4-images In directory hutz:/tmp/cvs-serv1500/css4-images Modified Files: Overview.src.html Log Message: Change the span.note/.issue styling to more closely match the blocks. Index: Overview.src.html =================================================================== RCS file: /sources/public/csswg/css4-images/Overview.src.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- Overview.src.html 17 Aug 2011 00:33:59 -0000 1.2 +++ Overview.src.html 28 Feb 2012 23:42:52 -0000 1.3 @@ -32,28 +32,25 @@ <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2> <dl> - <dt>This version: - <dd><a href="[VERSION]"> - http://www.w3.org/TR/[YEAR]/[STATUS]-[SHORTNAME]-[CDATE]</a> + <dt>This version:</dt> + <dd><a href="[VERSION]">http://www.w3.org/TR/[YEAR]/[STATUS]-[SHORTNAME]-[CDATE]</a></dd> - <dt>Latest version: - <dd><a href="http://www.w3.org/TR/css4-color"> - http://www.w3.org/TR/css4-images</a> + <dt>Latest version:</dt> + <dd><a href="http://www.w3.org/TR/css4-images">http://www.w3.org/TR/css4-images</a></dd> - <dt>Editor's draft: - <dd><a href="http://dev.w3.org/csswg/css4-images">http://dev.w3.org/csswg/css4-images</a> + <dt>Editor's draft:</dt> + <dd><a href="http://dev.w3.org/csswg/css4-images">http://dev.w3.org/csswg/css4-images</a></dd> - <dt>Previous version: - <dd><a href="http://www.w3.org/PreviousVersionURI"> - http://www.w3.org/PreviousVersionURI</a> + <dt>Previous version:</dt> + <dd><a href="http://www.w3.org/PreviousVersionURI">http://www.w3.org/PreviousVersionURI</a></dd> - <dt>Editors: - <dd class=vcard><span class=fn>Tab Atkins Jr.</span>, - <span class=org>Google, Inc.</span>, - <a class=url href="http://xanthir.com/contact">http://xanthir.com/contact</a> - <dd class=vcard><span class=fn>Elika J. Etemad (fantasai)</span>, - <span class=org>W3C Invited Expert</span>, - <a class=url href="http://fantasai.inkedblade.net/contact">http://fantasai.inkedblade.net/contact</a> + <dt>Editors:</dt> + <dd class=vcard><span class=fn>Tab Atkins Jr.</span>, + <span class=org>Google, Inc.</span>, + <a class=url href="http://xanthir.com/contact">http://xanthir.com/contact</a></dd> + <dd class=vcard><span class=fn>Elika J. Etemad (fantasai)</span>, + <span class=org>W3C Invited Expert</span>, + <a class=url href="http://fantasai.inkedblade.net/contact">http://fantasai.inkedblade.net/contact</a></dd> </dl> <!--copyright--> @@ -113,16 +110,20 @@ <h2>Planned Features</h2> <ol> + <li>Resolution tagging in image()</li> + <li>Logical keywords for specifying linear gradient direction.</li> <li>Conical gradients</li> -</ol> -<h2>Stuff I'm Pulling From Images 3</h2> + <li>The image-interpolation property</li> + <li>How to transition/animate images and gradients</li> +</ol> +<h2>Stuff I'm Pulling From Images 3</h2> -<!-- ====================================================================== --> +<!-- <h3 id="image-notation"> Image Annotations and Fallbacks: the ''image()'' notation</h3> @@ -201,7 +202,6 @@ this fallback will be painted over the 'background-color' (if any).</p> </div> -<!-- ====================================================================== --> <h3 id='cross-fade-function'> Combining images: the ''cross-fade()'' notation</h3> @@ -241,15 +241,6 @@ <span class='note'>The "dissolve()" function and "plus" compositing operator are defined in the literature by Porter-Duff.</span></p> -<!-- ====================================================================== --> - - - -<!-- ====================================================================== --> - - - -<!-- ====================================================================== --> <h3 id='image-rendering'> Determining How to Scale an Image: the 'image-rendering' property</h3> @@ -260,7 +251,7 @@ <td><dfn>image-rendering</dfn> <tr> <th>Value: - <td>auto | crisp-edges<!-- | pixelated --> + <td>auto | crisp-edges | pixelated <tr> <th>Initial: <td>auto @@ -295,12 +286,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> @@ -311,7 +302,6 @@ <p class=issue>dbaron suggests that optimizeSpeed should instead alias to crisp-edges.</p> -<!-- ====================================================================== --> <h2 id='serialization'> Serialization</h2> @@ -323,7 +313,6 @@ <p>All of these algorithms refer to a variable "s". For each, let s initially be the empty string, run the steps described, and then return s.</p> -<!-- ====================================================================== --> <h3 id='serializing-resolution'> Serializing a <resolution></h3> @@ -335,14 +324,12 @@ can all be converted to the canonical "dpcm" unit that CSSOM defines the serialization in terms of.</p> -<!-- ====================================================================== --> <h3 id='serializing-url-notation'> Serializing the ''url()'' notation</h3> <p>The serialization of the url() function is defined in the CSSOM spec.</p> -<!-- ====================================================================== --> <h3 id='serializing-image-notation'> Serializing the ''image()'' / <i><image-list></i> notation</h3> @@ -374,7 +361,6 @@ append the keyword to s.</li> </ol> -<!-- ====================================================================== --> <h3 id='serializing-element-notation'> Serializing the ''element()'' / <i><element-reference></i> notation</h3> @@ -390,7 +376,6 @@ <li>Append a close parenthesis ")" to s.</li> </ol> -<!-- ====================================================================== --> <h3 id='serializing-cross-fade'> Serializing the ''cross-fade()'' / <i><image-combination></i> notation</h3> @@ -416,7 +401,6 @@ <li>Append a close parenthesis ")" to s.</li> </ol> -<!-- ====================================================================== --> <h3 id="serializing-gradients"> Serializing Gradients</h3> @@ -534,7 +518,6 @@ it to s.</li> </ol> -<!-- ====================================================================== --> <h3 id='serializing-properties'> Serializing new properties</h3> @@ -575,7 +558,6 @@ <li>Serialize the value as a <bg-position> and append it to s.</li> </ol> -<!-- ====================================================================== --> <h2 id='interpolation'> Interpolation</h2> @@ -593,8 +575,6 @@ the elapsed time, and the timing function in use. For example, with a linear timing function and a 1s duration, after .3s t is equal to 30%.</p> -<!-- ====================================================================== --> - <h3 id='interpolating-images'> Interpolating <i><image></i></h3> @@ -606,7 +586,6 @@ <p>In specific terms, at each point in the interpolation the image is equal to <code>cross-fade(<start image>, <end image>, t)</code>.</p> -<!-- ======================================================================= --> <h3 id='interpolating-image-combinations'> Interpolating <i><image-combination></i></h3> @@ -624,7 +603,6 @@ argument, the percentage. Otherwise, they must be interpolated as generic <image>s.</p> -<!-- ======================================================================= --> <h3 id='interpolating-gradients'> Interpolating <i><gradient></i></h3> @@ -713,8 +691,7 @@ Then, for each pair of color-stops, interpolate the position and color independently.</li> </ol> - -<!-- ====================================================================== --> +-->
Received on Tuesday, 28 February 2012 23:42:57 UTC