[css-contain-1] Updates for REC

Author: svgeesus

css-contain-1/Overview.bs

@@ -2,7 +2,10 @@
 Title: CSS Containment Module Level 1
 Level: 1
 Shortname: css-contain
-Status: ED
+Status: REC
+Date: 2022-10-25
+Deadline: 2023-01-10
+Prepare for TR: yes
 Implementation Report: https://drafts.csswg.org/css-contain-1/implementation-report-2022-09
 Work Status: completed
 Group: csswg
@@ -13,7 +16,7 @@ Previous Version: https://www.w3.org/TR/2019/REC-css-contain-1-20191121/
 Editor: Tab Atkins, Google, http://xanthir.com/contact/, w3cid 42199
 Editor: Florian Rivoal, On behalf of Bloomberg, https://florian.rivoal.net/, w3cid 43241
 Abstract: This CSS module describes the 'contain' property, which indicates that the element's subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
-Status Text: <p>This document was published by the CSS Working Group as a Recommendation using the <a href="https://www.w3.org/2021/Process-20211102/#recs-and-notes">Recommendation track</a>. It includes <a href="https://www.w3.org/2021/Process-20211102/#proposed-corrections">proposed corrections</a>.</p><p class="correction proposed">Proposed corrections are marked in the document.</p>
+Status Text: <p>This document was published by the CSS Working Group as a Recommendation using the <a href="https://www.w3.org/2021/Process-20211102/#recs-and-notes">Recommendation track</a>. It includes <a href="https://www.w3.org/2021/Process-20211102/#proposed-corrections">proposed corrections</a>.</p><p class="correction proposed">Proposed corrections are marked in the document.</p><p>W3C recommends the wide deployment of this specification as a standard for the Web.</p>
 WPT Path Prefix: css/css-contain/
 Include MDN Panels: no
 </pre>
@@ -404,7 +407,7 @@ Strong Containment: the 'contain' property</h2>
 	</div>
 
 	<div class="correction proposed" id=c3>
-		<span class=marker>Candidate Correction 3:</span>
+		<span class=marker>Proposed Correction 3:</span>
 		The CSS Working Group had forgotten to consider the effects of containment
 		on the HTML <{html}> and <{body}> elements,
 		particularly in consideration of the fact that
@@ -617,7 +620,7 @@ Size Containment</h3>
 			</wpt>
 
 			<div class="correction proposed" id=c2>
-				<span class=marker>Candidate Correction 2:</span>
+				<span class=marker>Proposed Correction 2:</span>
 				The way the two normative sentences above are written was somewhat ambiguous,
 				causing implementers to have some doubts about the precise intended effects
 				in certain cases.
@@ -1767,6 +1770,7 @@ container-queries/unsupported-axis.html
 container-queries/viewport-units-dynamic.html
 container-queries/viewport-units.html
 container-queries/whitespace-update-after-removal.html
+container-queries/crashtests/chrome-layout-root-crash.html
 content-visibility/animation-display-lock.html
 content-visibility/content-visibility-080.html
 content-visibility/content-visibility-081.html
@@ -1815,6 +1819,14 @@ content-visibility/slot-content-visibility-6-crash.html
 content-visibility/slot-content-visibility-7-crash.html
 content-visibility/slot-content-visibility-8-crash.html
 content-visibility/slot-content-visibility-9-crash.html
+content-visibility/content-visibility-resize-observer-no-error.html
+content-visibility/content-visibility-with-top-layer-000.html
+content-visibility/content-visibility-with-top-layer-001.html
+content-visibility/content-visibility-with-top-layer-002.html
+content-visibility/content-visibility-with-top-layer-003.html
+content-visibility/content-visibility-with-top-layer-004.html
+content-visibility/content-visibility-with-top-layer-hide-after-addition.html
+content-visibility/dynamic-change-paint-fully-obscuring-child-001.html
 contain-inline-size-bfc-floats-001.html
 contain-inline-size-bfc-floats-002.html
 contain-inline-size-fieldset.html