W3C home > Mailing lists > Public > public-css-commits@w3.org > July 2011

csswg/css3-images Overview.src.html,1.113,1.114

From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 01 Jul 2011 22:16:48 +0000
To: public-css-commits@w3.org
Message-Id: <E1Qcm12-0004gz-ON@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-images
In directory hutz:/tmp/cvs-serv18019

Modified Files:
	Overview.src.html 
Log Message:
Reworded slightly awkward comment.


Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.src.html,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -d -r1.113 -r1.114
--- Overview.src.html	9 Jun 2011 23:17:10 -0000	1.113
+++ Overview.src.html	1 Jul 2011 22:16:46 -0000	1.114
@@ -224,12 +224,7 @@
 		<p><small>* SVG-in-&lt;img> support required.  Click the picture to view the SVG directly.</small></p>
 	</div>
 	
-	<p class="note">Note however that a UA that doesn't understand the media
-	fragments notation will display the entirety an image specified with ''url''.
-	However, since URLs with media fragment identifiers can also be used in the
-	''image()'' notation defined below, authors can take advantage of CSS's
-	forward-compatible parsing rules to provide a fallback when using an image
-	fragment URL:
+	<p class="note">Unfortunately, a UA that doesn't understand the media fragments notation will ignore the fragment and simply display the entirety of an image specified with ''url''. However, since URLs with media fragment identifiers can also be used in the ''image()'' notation defined below, authors can take advantage of CSS's forward-compatible parsing rules to provide a fallback when using an image fragment URL:</p>
 
 	<div class="example">
 		<p>In the example below, the ''image()'' notation is used together with
Received on Friday, 1 July 2011 22:16:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 1 July 2011 22:16:49 GMT