- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 14 Jan 2012 00:37:46 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-flexbox
In directory hutz:/tmp/cvs-serv22797
Modified Files:
Overview.html Overview.src.html
Log Message:
Editorial: Update the spec's header, footer, and propdefs per http://wiki.csswg.org/spec/format-update
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-flexbox/Overview.html,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -d -r1.90 -r1.91
--- Overview.html 13 Jan 2012 23:08:41 -0000 1.90
+++ Overview.html 14 Jan 2012 00:37:44 -0000 1.91
@@ -20,11 +20,11 @@
<h1 id=head-box-flexible>CSS Flexible Box Layout Module</h1>
- <h2 class="no-num no-toc" id=w3c-working>Editor's Draft, 13 January 2012</h2>
+ <h2 class="no-num no-toc" id=w3c-working>Editor's Draft, 14 January 2012</h2>
<dl>
<dt>This version:
- <!--<dd><a href="http://www.w3.org/TR/2012/ED-css3-flexbox-20120113/">http://www.w3.org/TR/2012/ED-css3-flexbox-20120113/</a>-->
+ <!--<dd><a href="http://www.w3.org/TR/2012/ED-css3-flexbox-20120114/">http://www.w3.org/TR/2012/ED-css3-flexbox-20120114/</a>-->
<dd><a
@@ -39,6 +39,12 @@
href="http://www.w3.org/TR/css3-flexbox/">http://www.w3.org/TR/css3-flexbox/</a>
+ <dt>Editor's Draft:
+
+ <dd><a
+ href="http://dev.w3.org/csswg/css3-flexbox/">http://dev.w3.org/csswg/css3-flexbox/</a>
+
+
<dt>Previous versions:
<dd><a
@@ -53,6 +59,17 @@
href="http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/">http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/</a>
+ <dt>Issues List:
+
+ <dd>
+ <p class=issue>Will be a bugzilla URL once I get a component added.</p>
+
+ <dt>Discussion:
+
+ <dd><a
+ href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a>
+ with subject line "<code>[css3-flexbox] …message topic…</code>"
+
<dt>Editors:
<dd><a href="http://www.xanthir.com/contact">Tab Atkins Jr.</a>, Google
@@ -146,6 +163,12 @@
<ul class=toc>
<li><a href="#intro"><span class=secno>1. </span> Introduction</a>
+ <ul class=toc>
+ <li><a href="#placement"><span class=secno>1.1. </span> Module
+ interactions</a>
+
+ <li><a href="#values"><span class=secno>1.2. </span> Values</a>
+ </ul>
<li><a href="#box-model"><span class=secno>2. </span> The Flexbox Box
Model</a>
@@ -211,6 +234,27 @@
<li><a href="#layout-interface"><span class=secno>9. </span> Box
Properties and Sizing</a>
+ <li><a href="#conformance"><span class=secno>10. </span> Conformance</a>
+ <ul class=toc>
+ <li><a href="#conventions"><span class=secno>10.1. </span> Document
+ conventions</a>
+
+ <li><a href="#conformance-classes"><span class=secno>10.2. </span>
+ Conformance classes</a>
+
+ <li><a href="#partial"><span class=secno>10.3. </span> Partial
+ implementations</a>
+
+ <li><a href="#experimental"><span class=secno>10.4. </span> Experimental
+ implementations</a>
+
+ <li><a href="#testing"><span class=secno>10.5. </span> Non-experimental
+ implementations</a>
+
+ <li><a href="#cr-exit-criteria"><span class=secno>10.6. </span> CR exit
+ criteria</a>
+ </ul>
+
<li class=no-num><a href="#acknowledgments">Acknowledgments</a>
<li class=no-num><a href="#references">References</a>
@@ -226,8 +270,14 @@
</ul>
<!--end-toc-->
+ <p class=issue>Add "Animatable" and "Canonical Order" fields to all the
+ propdef tables, per <a
+ href="http://wiki.csswg.org/spec/format-update">http://wiki.csswg.org/spec/format-update</a>.
+
<h2 id=intro><span class=secno>1. </span> Introduction</h2>
+ <p><em>This section is not normative.</em>
+
<p>CSS 2.1 defined four layout modes — algorithms which determine the
size and position of boxes based on their relationships with their sibling
and ancestor boxes: block layout, designed for laying out documents and
@@ -255,6 +305,33 @@
in can also be controlled explicitly, relative either to the current
writing mode (logical directions) or explicit physical directions.
+ <h3 id=placement><span class=secno>1.1. </span> Module interactions</h3>
+
+ <p>This module extends the definition of the ‘<code
+ class=property>display</code>’ property. It also defines a new type
+ of primitive value, the <a href="#flex-function">flex() notation</a>,
+ which is accepted by the ‘<code class=property>width</code>’
+ and ‘<code class=property>height</code>’ properties.
+
+ <h3 id=values><span class=secno>1.2. </span> 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 <a href="#CSS21"
+ rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>. Value types not defined in
+ this specification are defined in CSS Level 2 Revision 1 <a
+ href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>. Other CSS
+ modules may expand the definitions of these value types: for example <a
+ href="#CSS3COLOR" rel=biblioentry>[CSS3COLOR]<!--{{CSS3COLOR}}--></a>,
+ when combined with this module, expands the definition of the
+ <color> value type as used in this specification.
+
+ <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=box-model><span class=secno>2. </span> The Flexbox Box Model</h2>
<p>An element with ‘<code class=css>display:flexbox</code>’ or
@@ -375,7 +452,7 @@
<td>display
<tr>
- <th>New value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">New value</a>:
<td>flexbox | inline-flexbox
</table>
@@ -553,7 +630,7 @@
<td><dfn id=flex-direction>flex-direction</dfn>
<tr>
- <th>Values:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>row | row-reverse | column | column-reverse
@@ -591,7 +668,7 @@
<td><dfn id=flex-wrap>flex-wrap</dfn>
<tr>
- <th>Values:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>no-wrap | wrap | wrap-reverse
@@ -629,7 +706,7 @@
<td><dfn id=flex-flow0>flex-flow</dfn>
<tr>
- <th>Values:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td><'flex-direction'> || <'flex-wrap'>
@@ -780,7 +857,7 @@
<td><dfn id=flex-order0>flex-order</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td><number>
@@ -984,7 +1061,7 @@
<td><dfn id=flex-pack0>flex-pack</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>start | end | center | justify
@@ -1104,7 +1181,7 @@
<td><dfn id=flex-align0>flex-align</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>start | end | center | baseline | stretch
@@ -1142,7 +1219,7 @@
<td><dfn id=flex-item-align>flex-item-align</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>auto | start | end | center | baseline | stretch
@@ -1406,7 +1483,7 @@
<td><dfn id=flex-line-pack0>flex-line-pack</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>start | end | center | justify
@@ -1764,6 +1841,182 @@
width/height keywords on both the flexbox and flexbox items, the writing
modes of both the flexbox and flexbox items, and the flexbox direction.
+ <h2 id=conformance><span class=secno>10. </span> Conformance</h2>
+
+ <h3 id=conventions><span class=secno>10.1. </span> Document conventions</h3>
+
+ <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. <a
+ href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a>
+
+ <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.
+
+ <h3 id=conformance-classes><span class=secno>10.2. </span> Conformance
+ classes</h3>
+
+ <p>Conformance to CSS Flexbox Layout Module is defined for three
+ conformance classes:
+
+ <dl>
+ <dt><dfn id=style-sheet 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 id=renderer>renderer</dfn>
+
+ <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>
+
+ <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 Flexbox Layout Module if all of its
+ statements that use syntax defined in this module are valid according to
+ the generic CSS grammar and the individual grammars of each feature
+ defined in this module.
+
+ <p>A renderer is conformant to CSS Flexbox Layout Module if, in addition to
+ interpreting the style sheet as defined by the appropriate specifications,
+ it supports all the features defined by CSS Flexbox Layout Module 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 Flexbox Layout Module 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><span class=secno>10.3. </span> 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.
+
+ <h3 id=experimental><span class=secno>10.4. </span> 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.
+
+ <h3 id=testing><span class=secno>10.5. </span> 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><span class=secno>10.6. </span> CR exit criteria</h3>
+
+ <p class=issue>[Change or remove the following CR exit criteria if the spec
+ is not a module, but, e.g., a Note or a profile. This text was <a
+ href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on
+ 2008-06-04.</a>]
+
+ <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.
+
<hr title="Separator from footer">
<h2 class=no-num id=acknowledgments>Acknowledgments</h2>
@@ -1781,6 +2034,25 @@
<dl class=bibliography>
<dt style="display: none"><!-- keeps the doc valid if the DL is empty -->
<!---->
+
+ <dt id=CSS21>[CSS21]
+
+ <dd>Bert Bos; et al. <a
+ href="http://www.w3.org/TR/2011/REC-CSS2-20110607"><cite>Cascading Style
+ Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 7 June
+ 2011. W3C Recommendation. URL: <a
+ href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a>
+ </dd>
+ <!---->
+
+ <dt id=RFC2119>[RFC2119]
+
+ <dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key
+ words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet
+ RFC 2119. URL: <a
+ href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+ </dd>
+ <!---->
</dl>
<!--end-normative-->
@@ -1791,6 +2063,15 @@
<dl class=bibliography>
<dt style="display: none"><!-- keeps the doc valid if the DL is empty -->
<!---->
+
+ <dt id=CSS3COLOR>[CSS3COLOR]
+
+ <dd>Tantek Çelik; Chris Lilley; L. David Baron. <a
+ href="http://www.w3.org/TR/2011/REC-css3-color-20110607"><cite>CSS Color
+ Module Level 3.</cite></a> 7 June 2011. W3C Recommendation. URL: <a
+ href="http://www.w3.org/TR/2011/REC-css3-color-20110607">http://www.w3.org/TR/2011/REC-css3-color-20110607</a>
+ </dd>
+ <!---->
</dl>
<!--end-informative-->
@@ -1947,6 +2228,9 @@
<!--begin-index-->
<ul class=indexlist>
+ <li>authoring tool, <a href="#authoring-tool"
+ title="authoring tool"><strong>10.2.</strong></a>
+
<li>‘<code class=css>auto</code>’, <a
href="#flex-item-align-auto" title="''auto''"><strong>5.2.</strong></a>
@@ -2077,6 +2361,9 @@
<li>preferred size, <a href="#preferred-size"
title="preferred size"><strong>4.1.</strong></a>
+ <li>renderer, <a href="#renderer"
+ title=renderer><strong>10.2.</strong></a>
+
<li>resolve the flexible lengths, <a href="#resolve-the-flexible-lengths"
title="resolve the flexible lengths"><strong>7.</strong></a>
@@ -2096,6 +2383,12 @@
<li>stretch, <a href="#flex-align-stretch"
title=stretch><strong>5.2.</strong></a>
+ <li>style sheet
+ <ul>
+ <li>as conformance class, <a href="#style-sheet"
+ title="style sheet, as conformance class"><strong>10.2.</strong></a>
+ </ul>
+
<li>wrap, <a href="#flex-flow-wrap" title=wrap><strong>3.1.</strong></a>
<li>wrap-reverse, <a href="#flex-flow-wrap-reverse"
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-flexbox/Overview.src.html,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -d -r1.90 -r1.91
--- Overview.src.html 13 Jan 2012 23:08:41 -0000 1.90
+++ Overview.src.html 14 Jan 2012 00:37:44 -0000 1.91
@@ -25,11 +25,20 @@
<!--<dd><a href="[LATEST]">[LATEST]</a>-->
<dd><a href="http://www.w3.org/TR/css3-flexbox/">http://www.w3.org/TR/css3-flexbox/</a>
+ <dt>Editor's Draft:
+ <dd><a href="http://dev.w3.org/csswg/css3-flexbox/">http://dev.w3.org/csswg/css3-flexbox/</a>
+
<dt>Previous versions:
<dd><a href="http://www.w3.org/TR/2011/WD-css3-flexbox-20111129/">http://www.w3.org/TR/2011/WD-css3-flexbox-20111129/</a>
<dd><a href="http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/">http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/</a>
<dd><a href="http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/">http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/</a>
+ <dt>Issues List:</dt>
+ <dd><p class=issue>Will be a bugzilla URL once I get a component added.</p>
+
+ <dt>Discussion:</dt>
+ <dd><a href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a> with subject line "<code>[css3-flexbox] …message topic…</code>"
+
<dt>Editors:
<dd><a href="http://www.xanthir.com/contact">Tab Atkins Jr.</a>, Google Inc.</dd>
<dd>Alex Mogilevsky, Microsoft Corporation, <a href="mailto:alexmog@microsoft.com">alexmog@microsoft.com</a>
@@ -56,16 +65,32 @@
<h2 class="no-num no-toc" id="table">Table of contents</h2>
<!--toc-->
+<p class=issue>Add "Animatable" and "Canonical Order" fields to all the propdef tables, per <a href="http://wiki.csswg.org/spec/format-update">http://wiki.csswg.org/spec/format-update</a>.</p>
+
<h2 id="intro">
Introduction</h2>
+ <p><em>This section is not normative.</em>
+
<p>CSS 2.1 defined four layout modes — algorithms which determine the size and position of boxes based on their relationships with their sibling and ancestor boxes: block layout, designed for laying out documents and simple applications; inline layout, designed for laying out text; table layout, designed for laying out information in a tabular format; and positioned layout, designed for very explicit positioning without much regard for other elements in the document. This module introduces a new layout mode, flexbox layout, which is designed for laying out more complex applications and webpages.</p>
<p>Flexbox layout is superficially similar to block layout. It lacks many of the more complex text or document-formatting properties that can be used in block layout, such as 'float' and 'columns', but in return it gains more simple and powerful tools for aligning its contents in ways that webapps and complex web pages often need. </p>
<p>The contents of a flexbox can be laid out in any direction, can have their order swapped around dynamically, and can "flex" their sizes and positions to respond to the available space. If a flexbox is <i>multi-line</i>, the flexbox items flow in two dimensions, wrapping into separate lines in a fashion similar to how text is wrapped into multiple lines. The direction that these lines are stacked in can also be controlled explicitly, relative either to the current writing mode (logical directions) or explicit physical directions.</p>
+<h3 id="placement">
+Module interactions</h3>
+
+ <p>This module extends the definition of the 'display' property. It also defines a new type of primitive value, the <a href="#flex-function">flex() notation</a>, which is accepted by the 'width' and 'height' properties.
+
+<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 <color> 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='box-model'>
The Flexbox Box Model</h2>
@@ -109,7 +134,7 @@
<th>Name:
<td>display
<tr>
- <th>New value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">New value</a>:
<td>flexbox | inline-flexbox
</table>
@@ -215,7 +240,7 @@
<th>Name:</th>
<td><dfn>flex-direction</dfn>
<tr>
- <th>Values:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>row | row-reverse | column | column-reverse
<tr>
<th>Initial:
@@ -239,7 +264,7 @@
<th>Name:</th>
<td><dfn>flex-wrap</dfn>
<tr>
- <th>Values:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>no-wrap | wrap | wrap-reverse
<tr>
<th>Initial:
@@ -263,7 +288,7 @@
<th>Name:</th>
<td><dfn>flex-flow</dfn>
<tr>
- <th>Values:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td><'flex-direction'> || <'flex-wrap'>
<tr>
<th>Initial:
@@ -340,7 +365,7 @@
<th>Name:
<td><dfn>flex-order</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td><number>
<tr>
<th>Initial:
@@ -455,7 +480,7 @@
<th>Name:
<td><dfn>flex-pack</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>start | end | center | justify
<tr>
<th>Initial:
@@ -505,7 +530,7 @@
<th>Name:
<td><dfn>flex-align</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>start | end | center | baseline | stretch
<tr>
<th>Initial:
@@ -529,7 +554,7 @@
<th>Name:
<td><dfn>flex-item-align</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>auto | start | end | center | baseline | stretch
<tr>
<th>Initial:
@@ -678,7 +703,7 @@
<th>Name:
<td><dfn>flex-line-pack</dfn>
<tr>
- <th>Value:
+ <th><a href="http://dev.w3.org/csswg/css-module/#values">Value</a>:
<td>start | end | center | justify
<tr>
<th>Initial:
@@ -863,6 +888,181 @@
<p class='issue'>Define how flexboxes are sized, paying attention to width/height keywords on both the flexbox and flexbox items, the writing modes of both the flexbox and flexbox items, and the flexbox direction.</p>
+<h2 id="conformance">
+Conformance</h2>
+
+<h3 id="conventions">
+Document conventions</h3>
+
+ <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 Flexbox Layout Module
+ 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 Flexbox Layout Module
+ if all of its statements that use syntax defined in this module are valid
+ according to the generic CSS grammar and the individual grammars of each
+ feature defined in this module.
+
+ <p>A renderer is conformant to CSS Flexbox Layout Module
+ if, in addition to interpreting the style sheet as defined by the
+ appropriate specifications, it supports all the features defined
+ by CSS Flexbox Layout Module 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 Flexbox Layout Module
+ 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 class=issue>[Change or remove the following CR exit criteria if
+ the spec is not a module, but, e.g., a Note or a profile. This text was <a
+ href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on 2008-06-04.</a>]</p>
+
+ <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.
+
+
<hr title="Separator from footer">
<h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
Received on Saturday, 14 January 2012 00:37:49 UTC