[css3-layout] Replaced CR exit criteria with standard section on

conformance. Updated the changes section.

Author: bert-github

css3-layout/Overview.src.html

@@ -110,10 +110,6 @@ <h2 class="no-num no-toc" id=status>Status of this document</h2>
 <p>This draft combines ideas from earlier drafts on Template Layout,
 Grid Positioning [[CSS3GRID]] and Grid Layout [[CSS3-GRID-LAYOUT]].
 
-<p>The section on <a href="#cr-exit-criteria">“CR exit criteria”</a>
-lists some conditions for this specification to become a W3C
-Recommendation.
-
 <p>Issues on this draft are mentioned in the text itself and/or in the
 on-line Tracker under <a
 href="http://www.w3.org/Style/CSS/Tracker/products/15" >“Details on
@@ -3310,61 +3306,6 @@ <h2 id=chains>Chaining slots: the 'chains' property</h2>
 
 <!--=================================================================-->
 
-<h2 id=cr-exit-criteria>CR exit criteria</h2>
-
-<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.
-
-<p>A <a href="/Style/CSS/Test/" >test suite</a> will be developed during
-the Candidate Recommendation phase of this specification.
-
-<!--=================================================================-->
-
 <h2 id=history>History</h2>
 
 <p>The following sections contain some of the use cases and design
@@ -4264,6 +4205,11 @@ <h4 id=next-same>Automatic placement of elements</h4>
 
 <!--=================================================================-->
 
+<h2 id=conformance>Conformance</h2>
+<!--conformance-->
+
+<!--=================================================================-->
+
 <h2 id=changes>Changes</h2>
 
 <p>Summary of major changes since the <a
@@ -4305,23 +4251,13 @@ <h2 id=changes>Changes</h2>
 of slots than in a chain of columns, but it requires some new code,
 nevertheless.)
 
-<li>Moved page-based templates ('@page') to level 4. The scope of slot
-names, automatic chaining of slots on different pages, and especially
-the question of how to create more than three page templates
-(':first', ':left' and ':right') need more investigation.
-
-<li>Moved region-based styling (i.e., pseudo-element selectors for
-styling elements differently based on which slots they fall into) to
-level 4. It is only useful in combination with chaining of slots (the
-'chains' property) or page-based templates.
-
-<li>Renamed the keyword ''fit-content'' to ''auto''. The former has a
-specific meaning in [[CSS3BOX]], which is related, but not the same.
+<li>The 'content' property is now allowed on slots analogously to how
+it is allowed on ''before'' and ''after'' pseudo-elements and on
+margin boxes. One effect of this is that slots in page-based templates
+can be used for running headers.
 
-<li>The margin properties are now allowed on slots. Even though this
-is redundant with the possibility to create empty slots in the grid
-template, it seems more consistent, because slots also have borders
-(which, unlike in tables, do not collapse).
+<li>The margin properties are now allowed on slots. This allows, e.g.,
+slots ot overlap by means of negative margins.
 
 <li>Different set of constraints and a different function to optimize
 when calculating the size of rows and columns: the row heights and