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

csswg/css3-images Overview.html,1.200,1.201 Overview.src.html,1.208,1.209

From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 10 Nov 2011 23:46:57 +0000
To: public-css-commits@w3.org
Message-Id: <E1ROeKf-0000Al-BI@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-images
In directory hutz:/tmp/cvs-serv638

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Switch over the current module template.  No content changes.

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.html,v
retrieving revision 1.200
retrieving revision 1.201
diff -u -d -r1.200 -r1.201
--- Overview.html	9 Nov 2011 21:32:35 -0000	1.200
+++ Overview.html	10 Nov 2011 23:46:55 -0000	1.201
@@ -1,15 +1,33 @@
 <!DOCTYPE html>
 
 <html lang=en>
- <head><meta content="text/html; charset=utf-8" http-equiv=Content-Type>
+ <head profile="http://www.w3.org/2006/03/hcard"><meta
+  content="text/html; charset=utf-8" http-equiv=Content-Type>
 
   <title>CSS Image Values and Replaced Content Module Level 3</title>
-  <!--<link rel="stylesheet" type="text/css" href="../default.css">-->
-  <link href="http://dev.w3.org/csswg/css-module/default.css" rel=stylesheet
-  type="text/css">
[...1267 lines suppressed...]
+
+    <tr>
+     <th><span class=property>Name:</span>
+
+     <td>Value:
+
+     <td>Initial:
+
+     <td>Applies to:
+
+     <td>Inherited:
+
+     <td>Percentages:
+
+     <td>Media:
+  </table>
+  <!--end-properties-->
 </html>
 <!-- Keep this comment at the end of the file
 Local variables:

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.src.html,v
retrieving revision 1.208
retrieving revision 1.209
diff -u -d -r1.208 -r1.209
--- Overview.src.html	9 Nov 2011 21:32:35 -0000	1.208
+++ Overview.src.html	10 Nov 2011 23:46:55 -0000	1.209
@@ -1,19 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-<head>
-  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-  <title>CSS Image Values and Replaced Content Module Level 3</title>
-  <!--<link rel="stylesheet" type="text/css" href="../default.css">-->
-  <link rel="stylesheet" type="text/css" href="http://dev.w3.org/csswg/css-module/default.css">
-  <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD">
+<head profile="http://www.w3.org/2006/03/hcard">
+	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+	<title>CSS Image Values and Replaced Content Module Level 3</title>
+	<link rel="stylesheet" type="text/css" href="../css-module/default.css">
+	<link rel="stylesheet" type="text/css"
+				href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS].css">
+	<style type="text/css">
+		/* delete this block when you've cleared out all the .replaceme elements */
+		.replaceme {
+			border: solid red;
+			padding: 0 0.5em;
+			margin: 0 0.1em;
+			background: yellow;
+			color: green;
+		}
+		.replaceme:before {
+			 content: "FIXME(";
+			 color: black;
+		}
+		.replaceme:after {
+			 content: ")";
+			 color: black;
+		}
+	</style>
 </head>
 
-<body>
-
 <div class="head">
-	<!--logo-->
+<!--logo-->
 
-	<h1>CSS Image Values and Replaced Content Module Level 3</h1>
+<h1>CSS Image Values and Replaced Content Module Level 3</h1>
 
 	<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
 	<dl>
@@ -34,38 +50,26 @@
 		<dd><a href="http://www.w3.org/TR/2009/WD-css3-images-20090723/">http://www.w3.org/TR/2009/WD-css3-images-20090723/</a></dd>
 
 		<dt>Editors:</dt>
-		<dd><a href="http://fantasai.inkedblade.net/contact">Elika J. Etemad</a> (Mozilla Corporation)</dd>
-		<dd><a href="http://www.xanthir.com/contact/">Tab Atkins Jr.</a> (Google)</dd>
+		<dd class='vcard'>
+			<a class='url fn' href="http://fantasai.inkedblade.net/contact">Elika J. Etemad</a> (<span class='org'>Mozilla Corporation</span>)</dd>
+		<dd class='vcard'>
+			<a class='url fn' href="http://www.xanthir.com/contact/">Tab Atkins Jr.</a> (<span class='org'>Google</span>)</dd>
 	</dl>
-	<!--begin-copyright-->
-	<p>[Here will be included the file "../copyright.inc"]</p>
-	<!--end-copyright-->
 
-	<hr title="Separator for header">
-</div>
+<!--copyright-->
 
-<!-- ====================================================================== -->
+<hr title="Separator for header">
+</div>
 
-<h2 class="no-num no-toc" id="abstract">
-Abstract</h2>
+<h2 class="no-num no-toc" id="abstract">Abstract</h2>
 
-	<p>This CSS Image Values and Replaced Content module has two parts:
-	First, it defines the syntax for <i>&lt;image></i> values in CSS.
-	<i>&lt;image></i> values can be a single URI to an image, a list of
-	URIs denoting a series of fallbacks, a reference to an element in the document, or
-	gradients. Second, it defines properties used to control the
-	interaction of replaced content and the CSS layout algorithms.
-	These properties can affect the used image resolution for bitmaps,
-	the replaced object's orientation, and whether and how to preserve
-	the object's aspect ratio.</p>
+	<p>CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper,  in speech, etc. This module contains the features of CSS level&nbsp;3 relating to the &lt;image> type and replaced elements. It includes and extends the functionality of CSS level&nbsp;2 [[!CSS21]], which builds on CSS level&nbsp;1 [[CSS1]]. The main extensions compared to level&nbsp;2 are the generalization of the &lt;url> type to the &lt;image> type, several additions to the ''&lt;image>'' type, a generic sizing algorithm for images and other replaced content in CSS, and several properties controlling the interaction of replaced elements and CSS's layout models.</p>
 
-<!-- ====================================================================== -->
+<h2 class="no-num no-toc" id="status">Status of this document</h2>
 
-<h2 class="no-num no-toc" id="status">
-Status of this document</h2>
 <!--status-->
 
-	<p>The following features are at risk:</p>
+	<p>The following features are at risk: &hellip;
 
 	<ol>
 		<li>The <a href="#image-notation">image() function</a></li>
@@ -79,77 +83,31 @@
 		<li>The "snap" keyword for 'image-resolution'</li>
 	</ol>
 
-<!-- ====================================================================== -->
+<h2 class="no-num no-toc" id="contents">Table of contents</h2>
 
-<h2 class="no-num no-toc" id="contents">
-Table of Contents</h2>
 <!--toc-->
 
-<!-- ====================================================================== -->
-
 <h2 id="intro">
 Introduction</h2>
 
-	<p><em>This section is non-normative.</em></p>
-
-	<p>In CSS Levels 1 and 2, image values, such as those used in the
-	'background-image' property, could only be given by a single URI
-	value. This module introduces additional notations that allow a
-	2D image to be given as a list of URIs denoting fallbacks, as a
-	reference to an element in the document, and as a gradient.</p>
-
-<!-- ====================================================================== -->
-
-<h2 id="conformance">
-Conformance</h2>
-
-	<p>A document or implementation cannot conform to CSS Image Values & Replaced Content Level 3
-	 alone, but can claim conformance to CSS Image Values & Replaced Content Level 3 if it satisfies
-	 the conformance requirements in this specification when implementing CSS or
-	 another host language that normatively references this specification.</p>
-
-	<p>Conformance to CSS Image Values & Replaced Content Level 3 is defined for three classes:
-	<dl>
-		<dt><dfn>minimal</dfn></dt>
-		<dd>A device that does not implement CSS Transitions, CSS Animations, nor 
-		CSSOM may ignore the chapters on Serializing and Interpolating values for
-		the purpose of claiming conformance.</dd>
-
-		<dt><dfn>transition-capable</dfn></dt>
-		<dd>A device that implements CSS Transitions or CSS Animations must conform
-		to the <i>minimal</i> class, and additionally must implement the chapter 
-		on Interpolation.</dd>
-
-		<dt><dfn>CSSOM-capable</dfn></dt>
-		<dd>A device that implements CSSOM must conform to the <i>minimal</i> class, 
-		and additionally must implement the chapter on Serialization.</dd>
-	</dl>
-
-	<p>The conformance requirements are expressed with a combination of
-	descriptive assertions and RFC 2119 terminology. The key words "MUST",
-	"MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
-	"RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
-	document are to be interpreted as described in RFC 2119.
-	However, for readability, these words do not appear in all uppercase
-	letters in this specification. All of the text of this specification is
-	normative except sections explicitly marked as non-normative, examples,
-	and notes. [[!RFC2119]]</p>
+	<p><em>This section is not normative.</em>
 
-	<p>Examples in this specification are introduced with the words "for example"
-	or are set apart from the normative text with <code>class="example"</code>,
-	like this:
+	<p>In CSS Levels 1 and 2, image values, such as those used in the 'background-image' property, could only be given by a single URI value. This module introduces additional notations that allow a 2D image to be given as a list of URIs denoting fallbacks, as a reference to an element in the document, and as a gradient.</p>
 
-	<div class="example">
-		<p>This is an example of an informative example.</p>
-	</div>
+	<p>This module also defines several properties for manipulating raster images and for sizing or positioning replaced elements such as images within the box determined by the CSS layout algorithms.  Finally, it defines a generic sizing algorithm for images and other replaced elements for referencing from other specs.</p>
 
-	<p>Informative notes begin with the word "Note" and are set apart from the
-	normative text with <code>class="note"</code>, like this:
+<h3 id="placement">
+Module Interactions</h3>
 
-	<p class="note">Note, this is an informative note.</p>
+	<p>This module replaces and extends the ''&lt;image>'' type defined in [[!CSS3VALUES]].</p>
 
-<!-- ====================================================================== -->
+<h3 id="values">
+Values</h3>
 
+	<p>This specification follows the <a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property definition conventions</a> from [[!CSS21]]. Value types not defined in this specification are defined in CSS Level 2 Revision 1 [[!CSS21]]. Other CSS modules may expand the definitions of these value types: for example [[CSS3COLOR]], when combined with this module, expands the definition of the &lt;color&gt; value type as used in this specification.</p>
+	
+	<p>In addition to the property-specific values listed in their definitions, all properties defined in this specification also accept the <a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a> keyword as their property value. For readability it has not been repeated explicitly.
+	
 <h2 id='resolution-units'>
 Resolution Units: the &lt;resolution&gt; type</h2>
 
@@ -483,7 +441,7 @@
 	<p>All of the following ''linear-gradient()'' examples are presumed to be 
 	backgrounds applied to a box that is 200px wide and 100px tall.</p>
 
-	<div class=example>	
+	<div class=example> 
 		<p>Below are various ways of specifying a basic vertical gradient:</p>
 
 		<pre><code>linear-gradient(yellow, blue);
@@ -495,7 +453,7 @@
 		<p><img src="linear1.png" alt="" ></p>
 	</div>
 
-	<div class=example>	
+	<div class=example> 
 		<p>This demonstrates the use of an angle in the gradient.  Note that, though the angle is not exactly the same as the angle between the corners, the <i>gradient-line</i> is still sized so as to make the gradient yellow exactly at the upper-left corner, and blue exactly at the lower-right corner.</p>
 
 		<pre><code>linear-gradient(135deg, yellow, blue);
@@ -504,7 +462,7 @@
 		<p><img src="linear3.png" alt="" ></p>
 	</div>
 
-	<div class=example>	
+	<div class=example> 
 		<p>This demonstrates a 3-color gradient, and how to specify the location of a stop explicitly:</p>
 
 		<pre><code>linear-gradient(yellow, blue 20%, #0f0);</code></pre>
@@ -549,10 +507,10 @@
 
 	<pre class=prod>
 <dfn>&lt;radial-gradient></dfn> = radial-gradient(
-  [ <var>&lt;shape&gt;</var> , |
-    <var>&lt;shape&gt;</var>? [ at <var>&lt;position&gt;</var> || to <var>&lt;extent&gt;</var> ] ,
-  ]?
-  <var>&lt;color-stop&gt;</var> [ , <var>&lt;color-stop&gt;</var> ]+
+	[ [ <var>&lt;shape&gt;</var> , ] |
+		[ <var>&lt;shape&gt;</var>? [ at <var>&lt;position&gt;</var> || to <var>&lt;extent&gt;</var> ] , ]
+	]?
+	<var>&lt;color-stop&gt;</var> [ , <var>&lt;color-stop&gt;</var> ]+
 )</pre>
 
 	<p>The arguments are defined as follows:
@@ -561,9 +519,6 @@
 		<dt id='radial-shape'><dfn>&lt;shape&gt;</dfn></dt>
 		<dd>Can be either ''circle'' or ''ellipse''; determines whether the
 		gradient's <i>ending shape</i> is a circle or an ellipse, respectively.
-		If <i>&lt;shape&gt;</i> is omitted, the <i>ending shape</i> defaults
-		to a circle if the <i>&lt;extent&gt;</i> is a single &lt;length&gt;,
-		and to an ellipse otherwise.
 
 		<dt id='radial-position'><dfn>&lt;position&gt;</dfn></dt>
 		<dd>Determines the center of the gradient. The <i>&lt;position&gt;</i> notation
@@ -588,7 +543,7 @@
 				<dt><dfn id='radial-closest-side'>''closest-side''</dfn></dt>
 				<dd>The <i>ending shape</i> is sized so that that it exactly meets the
 				side of the box closest to the gradient's center. If the shape is an
-				ellipse, it exactly meets the closest side in each dimension.</dd>
+				ellipse or is omitted, it exactly meets the closest side in each dimension.</dd>
 
 				<dt><dfn id='radial-farthest-side'>''farthest-side''</dfn></dt>
 				<dd>Same as ''closest-side'', except the <i>ending shape</i> is sized
@@ -597,12 +552,12 @@
 				<dt><dfn id='radial-closest-corner'>''closest-corner''</dfn></dt>
 				<dd>The <i>ending shape</i> is sized so that that it passes through the
 				corner of the box closest to the gradient's center. If the shape is an
-				ellipse, the <i>ending shape</i> is given the same aspect-ratio
+				ellipse or is omitted, the <i>ending shape</i> is given the same aspect-ratio
 				it would have if ''closest-side'' were specified.
 
 				<dt><dfn id='radial-farthest-corner'>''farthest-corner''</dfn></dt>
 				<dd>Same as ''closest-corner'', except the <i>ending shape</i> is be
-				sized based on the farthest corner. If the shape is an ellipse,
+				sized based on the farthest corner. If the shape is an ellipse or is omitted,
 				the <i>ending shape</i> is given the same aspect ratio it would
 				have if ''farthest-side'' were specified.
 			</dl>
@@ -629,20 +584,16 @@
 		</dd>
 	</dl>
 
-	<div class='note'>
-		<p>The grammar listed above is kept deliberately simple for readability purposes, with some details instead expressed in the prose.  All of the details can be expressed directly in the grammar, however, and such a grammar is presented here for use by implementors and others writing parsers.  It is officially non-normative, but should match the same set of strings that the normative grammar does when augmented with the prose.
-
-		<pre>
-&lt;radial-gradient> = radial-gradient(
-  [ [ circle | ellipse ]  , |
-    [ circle | ellipse ]? [ at &lt;position> || to &lt;extent-keyword> ] , |
-    circle?               [ at &lt;position> || to &lt;length> ] , |
-    ellipse?              [ at &lt;position> || to [&lt;length> | &lt;percentage>]{2} ] , 
-  ]?
-  &lt;color-stop> [ , &lt;color-stop> ]+
+	<p>The expanded grammar for ''radial-gradient()'' is thus:
+<pre>&lt;radial-gradient> = radial-gradient(
+	[ [ [ circle | ellipse ]  , ] |
+		[ [ circle | ellipse ]? [ at &lt;position> || to &lt;extent-keyword> ] , ] |
+		[ circle? &lt;length>, ] |
+		[ ellipse? [&lt;length> | &lt;percentage>]{2} ]
+	]?
+	&lt;color-stop> [ , &lt;color-stop> ]+
 )
 &lt;extent-keyword> = closest-corner | closest-side | farthest-corner | farthest-side</pre>
-	</div>
 
 <h4 class="no-toc" id="radial-color-stops">
 Placing Color Stops</h4>
@@ -677,7 +628,7 @@
 	<p>All of the following examples are applied to a box that is 200px wide 
 	and 100px tall.</p>
 
-	<div class=example>	
+	<div class=example> 
 		<p>These examples demonstrate the basic syntax for radial gradients:</p>
 
 		<pre><code>radial-gradient(yellow, green);
@@ -692,14 +643,14 @@
 		<p><img src="radial3.png" alt="" ></p>
 	</div>
 
-	<div class=example>	
+	<div class=example> 
 		<p>This image shows a gradient originating from somewhere other than the center of the box:</p>
 
 		<pre><code>radial-gradient(bottom left, farthest-side, red, yellow 50px, green);</code></pre>
 		<p><img src="radial4.png" alt="" ></p>
 	</div>
 
-	<div class=example>	
+	<div class=example> 
 		<p>Here we illustrate a 'contain' gradient.</p>
 
 		<pre><code>radial-gradient(20px 30px, contain, red, yellow, green);
@@ -720,7 +671,22 @@
 	this specification defines ''repeating-linear-gradient()'' and 
 	''repeating-radial-gradient()'' functions.  These two functions take the 
 	same values and are interpreted the same as their respective non-repeating 
-	siblings defined previously.</p>
+	siblings defined previously:</p>
+
+	<pre class=prod><code><dfn>&lt;repeating-linear-gradient></dfn> = repeating-linear-gradient(
+	[ [ &lt;angle> | [ to <code>&lt;side-or-corner></code> ] ] ,]? 
+	&lt;color-stop>[, &lt;color-stop>]+
+)
+
+<dfn>&lt;repeating-radial-gradient></dfn> = repeating-radial-gradient(
+	[&lt;'background-position'&gt;,]? 
+	[[
+		[&lt;shape&gt; || &lt;size&gt;]
+		|
+		[&lt;length> | &lt;percentage>]{2}
+	],]? 
+	&lt;color-stop&gt;[, &lt;color-stop&gt;]+
+)</code></pre>
 
 	<p>When rendered, however, the color-stops are repeated infinitely in both 
 	directions, with their positions shifted by multiples of the difference 
@@ -1327,10 +1293,10 @@
 		found in the image itself. If the image has no resolution, the
 		resolution is set to 300dpi.</p>
 
-	  <pre>
+		<pre>
 img { image-resolution: from-image 300dpi }
 img { image-resolution: 300dpi from-image }
-	  </pre>
+		</pre>
 	</div>
 
 <!-- ====================================================================== -->
@@ -1395,7 +1361,7 @@
 	direction), while negative values cause a rotation to the left.  The computed
 	value of the property is calculated by rounding the specified angle to the 
 	nearest quarter-turn (90deg, 100grad, .25turn, etc.), rounding away from 0 
-	(that is, 45deg is rounded	to 90deg, while -45deg is rounded to -90deg), then
+	(that is, 45deg is rounded  to 90deg, while -45deg is rounded to -90deg), then
 	moduloing the value by 1 turn (360deg, 400grad, etc.).</p>
 
 	<div class="example">
@@ -1411,26 +1377,193 @@
 		or 450deg.</p>
 	</div>
 
-<!-- ====================================================================== -->
+<h2 id="conformance">
+Conformance</h2>
 
-<h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
+<h3 id="conventions">
+Document Conventions</h3>
 
-<p>Thanks to Brad Kemper, Brian Manthos, and Alan Gresley for their contributions to the definition of gradients.</p>
+	<p>Conformance requirements are expressed with a combination of
+	descriptive assertions and RFC 2119 terminology. The key words “MUST”,
+	“MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
+	“RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
+	document are to be interpreted as described in RFC 2119.
+	However, for readability, these words do not appear in all uppercase
+	letters in this specification.
+	
+	<p>All of the text of this specification is normative except sections
+	explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
+	
+	<p>Examples in this specification are introduced with the words “for example”
+	or are set apart from the normative text with <code>class="example"</code>,
+	like this:
+	
+	<div class="example">
+		<p>This is an example of an informative example.</p>
+	</div>
+	
+	<p>Informative notes begin with the word “Note” and are set apart from the
+	normative text with <code>class="note"</code>, like this:
+	
+	<p class="note">Note, this is an informative note.</p>
+
+<h3 id="conformance-classes">
+Conformance Classes</h3>
+
+	<p>Conformance to CSS Image Values and Replaced Content Module Level 3
+	is defined for three conformance classes:
+	<dl>
+		<dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
+			<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
+			style sheet</a>.
+		<dt><dfn>renderer</dfn></dt>
+			<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+			that interprets the semantics of a style sheet and renders
+			documents that use them.
+		<dt><dfn id="authoring-tool">authoring tool</dfn></dt>
+			<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+			that writes a style sheet.
+	</dl>
+	
+	<p>A style sheet is conformant to CSS Image Values and Replaced Content Module Level 3
+	if all of its declarations that use properties defined in this module
+	have values that are valid according to the generic CSS grammar and the
+	individual grammars of each property as given in this module.
+	
+	<p>A renderer is conformant to CSS Image Values and Replaced Content Module Level 3
+	if, in addition to interpreting the style sheet as defined by the
+	appropriate specifications, it supports all the features defined
+	by CSS Image Values and Replaced Content Module Level 3 by parsing them correctly
+	and rendering the document accordingly. However, the inability of a
+	UA to correctly render a document due to limitations of the device
+	does not make the UA non-conformant. (For example, a UA is not
+	required to render color on a monochrome monitor.)
+	
+	<p>An authoring tool is conformant to CSS Image Values and Replaced Content Module Level 3
+	if it writes style sheets that are syntactically correct according to the
+	generic CSS grammar and the individual grammars of each feature in
+	this module, and meet all other conformance requirements of style sheets
+	as described in this module.
+
+<h3 id="partial">
+Partial Implementations</h3>
+
+	<p>So that authors can exploit the forward-compatible parsing rules to
+	assign fallback values, CSS renderers <strong>must</strong>
+	treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
+	as appropriate</a>) any at-rules, properties, property values, keywords,
+	and other syntactic constructs for which they have no usable level of
+	support. In particular, user agents <strong>must not</strong> selectively
+	ignore unsupported component values and honor supported values in a single
+	multi-value property declaration: if any value is considered invalid
+	(as unsupported values must be), CSS requires that the entire declaration
+	be ignored.</p>
+	
+<h3 id="experimental">
+Experimental Implementations</h3>
+
+	<p>To avoid clashes with future CSS features, the CSS2.1 specification
+	reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
+	syntax</a> for proprietary and experimental extensions to CSS.
+	
+	<p>Prior to a specification reaching the Candidate Recommendation stage
+	in the W3C process, all implementations of a CSS feature are considered
+	experimental. The CSS Working Group recommends that implementations
+	use a vendor-prefixed syntax for such features, including those in
+	W3C Working Drafts. This avoids incompatibilities with future changes
+	in the draft.
+	</p>
+ 
+<h3 id="testing">Non-Experimental Implementations</h3>
+
+	<p>Once a specification reaches the Candidate Recommendation stage,
+	non-experimental implementations are possible, and implementors should
+	release an unprefixed implementation of any CR-level feature they
+	can demonstrate to be correctly implemented according to spec.
+	
+	<p>To establish and maintain the interoperability of CSS across
+	implementations, the CSS Working Group requests that non-experimental
+	CSS renderers submit an implementation report (and, if necessary, the
+	testcases used for that implementation report) to the W3C before
+	releasing an unprefixed implementation of any CSS features. Testcases
+	submitted to W3C are subject to review and correction by the CSS
+	Working Group.
+	
+	<p>Further information on submitting testcases and implementation reports
+	can be found from on the CSS Working Group's website at
+	<a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
+	Questions should be directed to the
+	<a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
+	mailing list.
+
+<h3 id="cr-exit-criteria">
+CR Exit Criteria</h3>
+
+	<p>For this specification to be advanced to Proposed Recommendation,
+	there must be at least two independent, interoperable implementations
+	of each feature. Each feature may be implemented by a different set of
+	products, there is no requirement that all features be implemented by
+	a single product. For the purposes of this criterion, we define the
+	following terms:
+	
+	<dl>
+		<dt>independent <dd>each implementation must be developed by a
+		different party and cannot share, reuse, or derive from code
+		used by another qualifying implementation. Sections of code that
+		have no bearing on the implementation of this specification are
+		exempt from this requirement.
+	
+		<dt>interoperable <dd>passing the respective test case(s) in the
+		official CSS test suite, or, if the implementation is not a Web
+		browser, an equivalent test. Every relevant test in the test
+		suite should have an equivalent test created if such a user
+		agent (UA) is to be used to claim interoperability. In addition
+		if such a UA is to be used to claim interoperability, then there
+		must one or more additional UAs which can also pass those
+		equivalent tests in the same way for the purpose of
+		interoperability. The equivalent tests must be made publicly
+		available for the purposes of peer review.
+	
+		<dt>implementation <dd>a user agent which:
+	
+		<ol class=inline>
+			<li>implements the specification.
+	
+			<li>is available to the general public. The implementation may
+			be a shipping product or other publicly available version
+			(i.e., beta version, preview release, or “nightly build”). 
+			Non-shipping product releases must have implemented the
+			feature(s) for a period of at least one month in order to
+			demonstrate stability.
+	
+			<li>is not experimental (i.e., a version specifically designed
+			to pass the test suite and is not intended for normal usage
+			going forward).
+		</ol>
+	</dl>
+	
+	<p>The specification will remain Candidate Recommendation for at least
+	six months.
+
+<h2 class=no-num id="acknowledgments">Acknowledgments</h2>
+
+	<p>Thanks to Brad Kemper, Brian Manthos, and Alan Gresley for their contributions to the definition of gradients.</p>
+
+<h2 class=no-num id="references">References</h2>
 
-<h2 class="no-num" id="references">References</h2>
 
 <h3 class="no-num" id="normative-references">Normative references</h3>
 <!--normative-->
 
-<h3 class="no-num" id="informative-references">Informative references</h3>
+<h3 class="no-num" id="other-references">Other references</h3>
 <!--informative-->
 
-<h2 class="no-num">Property index</h2>
-<!-- properties -->
-
-<h2 class="no-num">Index</h2>
+<h2 class="no-num" id="index">Index</h2>
 <!--index-->
 
+
+<h2 class="no-num" id="property-index">Property index</h2>
+<!-- properties -->
 </body>
 </html>
 <!-- Keep this comment at the end of the file
@@ -1454,3 +1587,4 @@
 sgml-local-ecat-files:nil
 End:
 -->
+ 
Received on Thursday, 10 November 2011 23:46:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 10 November 2011 23:47:00 GMT