- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 24 Feb 2012 17:28:37 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-images In directory hutz:/tmp/cvs-serv22261 Modified Files: Overview.html Overview.src.html Log Message: Fix the 'not rendered' definition to avoid locking in a particular definition for SVG. Index: Overview.html =================================================================== RCS file: /sources/public/csswg/css3-images/Overview.html,v retrieving revision 1.292 retrieving revision 1.293 diff -u -d -r1.292 -r1.293 --- Overview.html 22 Feb 2012 18:03:37 -0000 1.292 +++ Overview.html 24 Feb 2012 17:28:34 -0000 1.293 @@ -16,7 +16,7 @@ <h1>CSS Image Values and Replaced Content Module Level 3</h1> - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 22 February + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 24 February 2012</h2> <dl> @@ -24,7 +24,7 @@ <dd><a href="http://dev.w3.org/csswg/css3-images/">http://dev.w3.org/csswg/css3-images/</a> - <!-- <dd><a href="http://www.w3.org/TR/2012/ED-css3-images-20120222/">http://www.w3.org/TR/2012/WD-css3-images-20120222/</a>--> + <!-- <dd><a href="http://www.w3.org/TR/2012/ED-css3-images-20120224/">http://www.w3.org/TR/2012/WD-css3-images-20120224/</a>--> <dt>Latest Version: @@ -496,6 +496,11 @@ for images. <a href="#MEDIA-FRAGS" rel=biblioentry>[MEDIA-FRAGS]<!--{{!MEDIA-FRAGS}}--></a> + <p>If a URL in the list uses a fragment identifier syntax that the + implementation does not understand, or which the implementation does not + consider valid for that type of image, the image must be treated as + invalid. + <p>The ‘<code class=css>image()</code>’ notation is defined as: @@ -571,6 +576,21 @@ partially-transparent blue. </div> + <div class=example> + <p>Implementations are required to ignore images that use fragment + identifers they don't recognize, which allows authors to use new fragment + formats and still get safe fallback, which doesn't exist in normal CSS + (as an unknown fragment identifier in ‘<code + class=css>url()</code>’ doesn't make the property invalid).</p> + + <p>For example, if a future specification defined a way to refer to a + specific frame of an animated GIF with a fragment identifier, an author + could write the following to get newer browsers to use the GIF's frame, + and older browsers to instead download the fallback image:</p> + + <pre>background-image: image('cat_meme.gif#frame=5', 'lolcat.png');</pre> + </div> + <p>Along with each URL, the author may specify a directionality, similar to adding a <code>dir</code> attribute to an element in HTML. The image represented by the function takes on the directionality of the used URL. @@ -834,10 +854,10 @@ title=element-not-rendered>not rendered</dfn> if it does not have an associated box. This can happen, for example, if the element or an ancestor is ‘<code class=css>display:none</code>’, or if the - element is not in a rendered document. In SVG, the descendants of a - <code><defs></code> element are also considered to not be rendered. - Other host languages may define additional ways in which an element can be - considered not rendered. + element is not in a rendered document. Host languages may define + additional ways in which an element can be considered not rendered; for + example, in SVG, any descendant of a <code><defs></code> element is + considered to be not rendered. <h4 class=no-num id=paint-sources> Paint Sources</h4> Index: Overview.src.html =================================================================== RCS file: /sources/public/csswg/css3-images/Overview.src.html,v retrieving revision 1.302 retrieving revision 1.303 diff -u -d -r1.302 -r1.303 --- Overview.src.html 22 Feb 2012 18:03:37 -0000 1.302 +++ Overview.src.html 24 Feb 2012 17:28:34 -0000 1.303 @@ -266,7 +266,7 @@ <div class='example'> <p>Implementations are required to ignore images that use fragment identifers they don't recognize, which allows authors to use new fragment formats and still get safe fallback, which doesn't exist in normal CSS (as an unknown fragment identifier in ''url()'' doesn't make the property invalid).</p> - <p>For example, if a future specification defined a way to refer to a specific frame of an animated GIF, an author could write the following to get newer browsers to use the GIF's frame, and older browsers to instead download the fallback image:</p> + <p>For example, if a future specification defined a way to refer to a specific frame of an animated GIF with a fragment identifier, an author could write the following to get newer browsers to use the GIF's frame, and older browsers to instead download the fallback image:</p> <pre>background-image: image('cat_meme.gif#frame=5', 'lolcat.png');</pre> </div> @@ -454,7 +454,7 @@ the image must look identical to the referenced element, modulo rasterization quality.</p> - <p>An element is <dfn id='element-not-rendered' title='element-not-rendered'>not rendered</dfn> if it does not have an associated box. This can happen, for example, if the element or an ancestor is ''display:none'', or if the element is not in a rendered document. In SVG, the descendants of a <code><defs></code> element are also considered to not be rendered. Other host languages may define additional ways in which an element can be considered not rendered.</p> + <p>An element is <dfn id='element-not-rendered' title='element-not-rendered'>not rendered</dfn> if it does not have an associated box. This can happen, for example, if the element or an ancestor is ''display:none'', or if the element is not in a rendered document. Host languages may define additional ways in which an element can be considered not rendered; for example, in SVG, any descendant of a <code><defs></code> element is considered to be not rendered.</p> <h4 id='paint-sources' class='no-num'> Paint Sources</h4>
Received on Friday, 24 February 2012 17:28:39 UTC