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

csswg/css3-images Overview.html,1.111,1.112 Overview.src.html,1.117,1.118

From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 07 Jul 2011 00:24:59 +0000
To: public-css-commits@w3.org
Message-Id: <E1QecOp-0004wK-R6@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-images
In directory hutz:/tmp/cvs-serv18964

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Fix markup errors

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.html,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -d -r1.111 -r1.112
--- Overview.html	6 Jul 2011 21:34:00 -0000	1.111
+++ Overview.html	7 Jul 2011 00:24:57 -0000	1.112
@@ -9,10 +9,6 @@
   <link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel=stylesheet
   type="text/css">
 
-  <style type="text/css">
-  p { text-indent: 0 !important; margin: .5em 0; }
-  </style>
-
  <body>
   <div class=head> <!--begin-logo-->
    <p><a href="http://www.w3.org/"><img alt=W3C height=48
@@ -20,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 6 July 2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 7 July 2011</h2>
 
    <dl>
     <dt>Latest Version:
@@ -436,7 +432,7 @@
     the SVG directly.</small></p>
   </div>
 
-  <p class=note>Unfortunately, a UA that doesn't understand the media
+  <p class=note>Note that a legacy UA that doesn't understand the media
    fragments notation will ignore the fragment and simply display the
    entirety of an image specified with &lsquo;<code
    class=css>url</code>&rsquo;. However, since URLs with media fragment
@@ -1585,7 +1581,7 @@
      href="#default-object-size"><i>default object size</i></a> equal to the
      replaced element's used width and height.</p>
 
-   <dt>scale-down <b class=issue>better name?</b>
+   <dt>scale-down <i class=issue>better name?</i>
 
    <dd>
     <p>Size the content as if &lsquo;<code class=property>none</code>&rsquo;
@@ -2348,61 +2344,59 @@
 
   <ol>
    <li>Convert both the start and end gradients to their explicit forms:
-  </ol>
-
-  <dl>
-   <dt>For linear gradients:
+    <dl>
+     <dt>For linear gradients:
 
-   <dd>
-    <ul>
-     <li>If the direction is specified as an &lt;angle>, it is already in its
-      explicit form.
+     <dd>
+      <ul>
+       <li>If the direction is specified as an &lt;angle>, it is already in
+        its explicit form.
 
-     <li>Otherwise, if the direction is specified as a single keyword, change
-      &lsquo;<code class=property>bottom</code>&rsquo; to &lsquo;<code
-      class=css>0deg</code>&rsquo;, &lsquo;<code
-      class=property>left</code>&rsquo; to &lsquo;<code
-      class=css>90deg</code>&rsquo;, &lsquo;<code
-      class=property>top</code>&rsquo; to &lsquo;<code
-      class=css>180deg</code>&rsquo;, or &lsquo;<code
-      class=property>right</code>&rsquo; to &lsquo;<code
-      class=css>270deg</code>&rsquo;.
+       <li>Otherwise, if the direction is specified as a single keyword,
+        change &lsquo;<code class=property>bottom</code>&rsquo; to
+        &lsquo;<code class=css>0deg</code>&rsquo;, &lsquo;<code
+        class=property>left</code>&rsquo; to &lsquo;<code
+        class=css>90deg</code>&rsquo;, &lsquo;<code
+        class=property>top</code>&rsquo; to &lsquo;<code
+        class=css>180deg</code>&rsquo;, or &lsquo;<code
+        class=property>right</code>&rsquo; to &lsquo;<code
+        class=css>270deg</code>&rsquo;.
 
-     <li>Otherwise, if the direction is specified as two keywords, change the
-      direction to an &lt;angle> in the following ranges that would produce
-      an equivalent gradient: for &lsquo;<code class=css>bottom
-      left</code>&rsquo; or &lsquo;<code class=css>left bottom</code>&rsquo;,
-      the angle must be between 0deg and 90deg; for &lsquo;<code
-      class=css>top left</code>&rsquo; or &lsquo;<code class=css>left
-      top</code>&rsquo;, the angle must be between 90deg and 180deg; for
-      &lsquo;<code class=css>top right</code>&rsquo; or &lsquo;<code
-      class=css>right top</code>&rsquo;, the angle must be between 180deg and
-      270deg; for &lsquo;<code class=css>bottom right</code>&rsquo; or
-      &lsquo;<code class=css>right bottom</code>&rsquo;, the angle must be
-      between 270deg and 360deg.
-    </ul>
+       <li>Otherwise, if the direction is specified as two keywords, change
+        the direction to an &lt;angle> in the following ranges that would
+        produce an equivalent gradient: for &lsquo;<code class=css>bottom
+        left</code>&rsquo; or &lsquo;<code class=css>left
+        bottom</code>&rsquo;, the angle must be between 0deg and 90deg; for
+        &lsquo;<code class=css>top left</code>&rsquo; or &lsquo;<code
+        class=css>left top</code>&rsquo;, the angle must be between 90deg and
+        180deg; for &lsquo;<code class=css>top right</code>&rsquo; or
+        &lsquo;<code class=css>right top</code>&rsquo;, the angle must be
+        between 180deg and 270deg; for &lsquo;<code class=css>bottom
+        right</code>&rsquo; or &lsquo;<code class=css>right
+        bottom</code>&rsquo;, the angle must be between 270deg and 360deg.
 
-    <p>If both the start and end gradients had their direction specified with
-     keywords, and the absolute difference between the angles their
-     directions mapped to is greater than 180deg, add 360deg to the direction
-     of the gradient with the smaller angle. <span class=note>This ensures
-     that a transition from, for example, "right" (270deg) to "bottom" (0deg)
-     rotates the gradient a quarter-turn clockwise, as expected, rather than
-     rotating three-quarters of a turn counter-clockwise.</span></p>
+       <li>If both the start and end gradients had their direction specified
+        with keywords, and the absolute difference between the angles their
+        directions mapped to is greater than 180deg, add 360deg to the
+        direction of the gradient with the smaller angle. <span
+        class=note>This ensures that a transition from, for example, "right"
+        (270deg) to "bottom" (0deg) rotates the gradient a quarter-turn
+        clockwise, as expected, rather than rotating three-quarters of a turn
+        counter-clockwise.</span>
+      </ul>
 
-   <dt>For radial gradients:
+     <dt>For radial gradients:
 
-   <dd>
-    <ul>
-     <li>If the size is specified as two &lt;length>s or &lt;percentage>s, it
-      is already in its explicit form.
+     <dd>
+      <ul>
+       <li>If the size is specified as two &lt;length>s or &lt;percentage>s,
+        it is already in its explicit form.
 
-     <li>Otherwise, the size must be changed to a pair of &lt;length>s that
-      would produce an equivalent ending-shape.
-    </ul>
-  </dl>
+       <li>Otherwise, the size must be changed to a pair of &lt;length>s that
+        would produce an equivalent ending-shape.
+      </ul>
+    </dl>
 
-  <ul>
    <li>Interpolate each component and color-stop of the gradients
     independently. For linear gradients, the only component is the angle. For
     radial gradients, the components are the horizontal and vertical position
@@ -2414,9 +2408,9 @@
     start and end gradients are considered to be at the same index, and all
     other color-stops following and preceding are indexed appropriately.
     Then, for each pair of color-stops, interpolate the position and color
-    independently.</li>
-   <!-- ====================================================================== -->
-  </ul>
+    independently.
+  </ol>
+  <!-- ====================================================================== -->
 
   <h2 class=no-num id=changes>Changes Since the 17 February 2011 Working
    Draft</h2>

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.src.html,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- Overview.src.html	6 Jul 2011 21:34:00 -0000	1.117
+++ Overview.src.html	7 Jul 2011 00:24:57 -0000	1.118
@@ -5,9 +5,6 @@
   <title>CSS Image Values and Replaced Content Module Level 3</title>
   <link rel="stylesheet" type="text/css" href="http://dev.w3.org/csswg/default.css">
   <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED">
-  <style type=text/css>
-  p { text-indent: 0 !important; margin: .5em 0; }
-  </style>
 </head>
 
 <body>
@@ -224,7 +221,12 @@
 		<p><small>* SVG-in-&lt;img> support required.  Click the picture to view the SVG directly.</small></p>
 	</div>
 	
-	<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>
+	<p class="note">Note that a legacy 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
@@ -392,7 +394,6 @@
 
 	<p class=issue>Someone else needs to review this and make sure that I'm 
 	not missing any cycles.</p>
-</div>
 
 <!-- ====================================================================== -->
 
@@ -706,7 +707,7 @@
 			''0'' is allowed, but produces a degenerate shape.  The handling of
 			degenerate ending-shapes is specified later in this specification.</p>
 		</dd>
-	</dt>
+	</dl>
 
 	<p>If this argument is omitted, it defaults to ''ellipse cover''.</p>
 
@@ -1185,7 +1186,7 @@
 			the replaced element's used width and height.</p>
 		</dd>
 
-		<dt>scale-down <b class=issue>better name?</i></dt>
+		<dt>scale-down <i class=issue>better name?</i></dt>
 		<dd>
 			<p>Size the content as if 'none' or 'contain' were specified, whichever
 			would result in a smaller size.</p>
@@ -1764,7 +1765,7 @@
 		<li>Serialize the keyword and append it to s.</li>
 	</ol>
 
-	<p>To serialize the 'object-position' property:</li>
+	<p>To serialize the 'object-position' property:</p>
 
 	<ol>
 		<li>Serialize the value as a &lt;bg-position> and append it to s.</li>
@@ -1847,7 +1848,7 @@
 	generic image.</p>
 
 	<ol>
-		<li>Convert both the start and end gradients to their explicit forms:</li>
+		<li>Convert both the start and end gradients to their explicit forms:
 			<dl>
 				<dt>For linear gradients:</dt>
 				<dd>
@@ -1869,7 +1870,7 @@
 						must be between 180deg and 270deg; for 'bottom right' or
 						'right bottom', the angle must be between 270deg and 360deg.</li>
 
-						<p>If both the start and end gradients had their direction
+						<li>If both the start and end gradients had their direction
 						specified with keywords, and the absolute difference 
 						between the	angles their directions mapped to is greater 
 						than 180deg, add 360deg to the direction of the gradient 
@@ -1877,7 +1878,7 @@
 						that a transition from, for example, "right" (270deg) to 
 						"bottom" (0deg) rotates the gradient a quarter-turn 
 						clockwise, as expected, rather than rotating 
-						three-quarters of a turn counter-clockwise.</span></p>
+						three-quarters of a turn counter-clockwise.</span></li>
 					</ul>
 				</dd>
 				
Received on Thursday, 7 July 2011 00:25:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 7 July 2011 00:25:02 GMT