W3C home > Mailing lists > Public > public-css-commits@w3.org > February 2012

csswg/css3-images Overview.html,1.306,1.307 Overview.src.html,1.316,1.317

From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 28 Feb 2012 21:10:27 +0000
To: public-css-commits@w3.org
Message-Id: <E1S2UJX-0002sZ-3g@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-images
In directory hutz:/tmp/cvs-serv11053

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Add note about why one of the 'invalid image' clauses is limited to image() only, not url().

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.html,v
retrieving revision 1.306
retrieving revision 1.307
diff -u -d -r1.306 -r1.307
--- Overview.html	28 Feb 2012 21:07:03 -0000	1.306
+++ Overview.html	28 Feb 2012 21:10:24 -0000	1.307
@@ -528,7 +528,9 @@
   <p>If a URL 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 URL must be treated as representing an <a
-   href="#invalid-image"><i>invalid image</i></a>.
+   href="#invalid-image"><i>invalid image</i></a>. <span class=note>This
+   error-handling is limited to image(), and not placed in url(), for legacy
+   compat reasons.</span>
 
   <p>Multiple &lsquo;<a href="#image-decl-type"><code
    class=css>&lt;image-decl>s</code></a>&rsquo; can be given separated by

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.src.html,v
retrieving revision 1.316
retrieving revision 1.317
diff -u -d -r1.316 -r1.317
--- Overview.src.html	28 Feb 2012 21:07:04 -0000	1.316
+++ Overview.src.html	28 Feb 2012 21:10:25 -0000	1.317
@@ -233,7 +233,7 @@
 
 	<p>Each <code>&lt;string></code> represents a <a href="http://dev.w3.org/csswg/css3-values/#urls">URL</a>.  As usual for URLs in CSS, each is resolved to an absolute URL (as described in Values &amp; Units) when ''image()'' appears in the computed value of a property.</p>
 
-	<p>If a URL 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 URL must be treated as representing an <i>invalid image</i>.</p>
+	<p>If a URL 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 URL must be treated as representing an <i>invalid image</i>. <span class='note'>This error-handling is limited to image(), and not placed in url(), for legacy compat reasons.</span></p>
 
 	<p>Multiple ''&lt;image-decl>s'' can be given separated by commas, in which case the function represents the first image that's not an <i>invalid image</i>.  The final argument can specify a ''&lt;color>'' to serve as an ultimate fallback; this can be used, e.g. for 'background-image', to ensure adequate contrast if none of the preceding ''&lt;image-decl>s'' can be used. If the final argument is a ''&lt;color>'', it represents a solid-color image of the given color with no <i>intrinsic dimensions</i>.  If all of the provided ''&lt;image-decl>s'' are <i>invalid images</i> and a fallback color was not provided as the last argument, the entire ''image()'' function must be treated as an <i>invalid image</i>.
 
Received on Tuesday, 28 February 2012 21:10:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:50 UTC