Merge branch 'main' into css-style-decl-split

Author: svgeesus

CONTRIBUTING.md

@@ -39,11 +39,29 @@ issues on a regular basis; however note that sometimes this can take awhile
 issue and the work schedules of people involved--this does not mean we are
 ignoring the issue.
 
-For an issue that requires WG discussion or approval, WG members can tag/label
-it 'Agenda+' to bring it to the Working Group's attention. Unfortunately,
+When issues need WG discussion or approval, WG members should label the issue
+'Agenda+' to bring it to the Working Group's attention. Unfortunately,
 GitHub doesn't allow labelling permissions without repository write permissions,
 so if you believe an issue is urgent or discussion has stalled for awhile and
-the WG's attention is needed to move forward, ask one of the editors to flag it.
+the WG's attention is needed to move forward, ask one of the Editors to flag it.
+
+In general, you should not directly commit changes to a draft unless you are an
+Editor of that draft, or have their explicit permission. If you are not an 
+Editor of a draft, but wish to contribute changes, the best practice is to either 
+work directly with an Editor to review proposed text, or file your proposal as a 
+pull request (PR). Substantive changes need WG consensus, not merely Editor 
+agreement; typographic error and markup fixes are generally okay to commit, but 
+any substantive changes should have clear WG consensus. Substantial changes or
+additions to non-normative text should still have clear Editor approval.
+
+In any case, WG consensus is expected prior to merging changes, and consensus is 
+determined by the Chairs (not self-assessed) via synchronous decisions during 
+meetings, and occasionally via async CFCs. Some degree of discretion is afforded 
+to Editors to make changes prior to WG consensus, particularly early in a spec or 
+feature's lifecycle, although Editors must confirm those changes with the WG 
+prior to republishing on TR. References to the discussion and the WG consensus 
+should be placed in the issue or commit. Agreement from an Editor in an issue 
+is not a substitute for WG consensus.
 
 The Working Group, aside from managing issues on GitHub, mainly discusses
 specifications and requests on [the www-style public mailing list](https://lists.w3.org/Archives/Public/www-style/),

css-2023/Overview.bs

@@ -307,7 +307,7 @@ Classification of CSS Specifications</h2>
 		<dd>
 			Introduces a flexible linear layout model for CSS.
 
-		<dt><a href="https://www.w3.org/TR/css-ui-3/">CSS User Interface Module Level 3</a>
+		<dt><a href="https://www.w3.org/TR/css-ui-3/">CSS Basic User Interface Module Level 3</a>
 		[[!CSS-UI-3]]
 		<dd>
 			Extends and supersedes CSS2&sect;18.1 and CSS2&sect;18.4,
@@ -414,15 +414,15 @@ Fairly Stable Modules with limited implementation experience</h3>
 			defining properties for text manipulation and specifying their processing model.
 			It covers line breaking, justification and alignment, white space handling, and text transformation.
 
-		<dt><a href="https://www.w3.org/TR/css-text-decor-3/">CSS Text Decoration Level 3</a>
+		<dt><a href="https://www.w3.org/TR/css-text-decor-3/">CSS Text Decoration Module Level 3</a>
 		[[CSS-TEXT-DECOR-3]]
 		<dd>
 			Extends and supersedes CSS2&sect;16.3,
 			providing more control over text decoration lines
 			and adding the ability to specify text emphasis marks
 			and text shadows.
 
-		<dt><a href="https://www.w3.org/TR/css-masking-1/">CSS Masking Level 1</a>
+		<dt><a href="https://www.w3.org/TR/css-masking-1/">CSS Masking Module Level 1</a>
 		[[CSS-MASKING-1]]
 		<dd>
 			Replaces CSS2&sect;11.1.2

css-2024/Overview.bs

@@ -306,7 +306,7 @@ Classification of CSS Specifications</h2>
 		<dd>
 			Introduces a flexible linear layout model for CSS.
 
-		<dt><a href="https://www.w3.org/TR/css-ui-3/">CSS User Interface Module Level 3</a>
+		<dt><a href="https://www.w3.org/TR/css-ui-3/">CSS Basic User Interface Module Level 3</a>
 		[[!CSS-UI-3]]
 		<dd>
 			Extends and supersedes CSS2&sect;18.1 and CSS2&sect;18.4,
@@ -413,15 +413,15 @@ Fairly Stable Modules with limited implementation experience</h3>
 			defining properties for text manipulation and specifying their processing model.
 			It covers line breaking, justification and alignment, white space handling, and text transformation.
 
-		<dt><a href="https://www.w3.org/TR/css-text-decor-3/">CSS Text Decoration Level 3</a>
+		<dt><a href="https://www.w3.org/TR/css-text-decor-3/">CSS Text Decoration Module Level 3</a>
 		[[CSS-TEXT-DECOR-3]]
 		<dd>
 			Extends and supersedes CSS2&sect;16.3,
 			providing more control over text decoration lines
 			and adding the ability to specify text emphasis marks
 			and text shadows.
 
-		<dt><a href="https://www.w3.org/TR/css-masking-1/">CSS Masking Level 1</a>
+		<dt><a href="https://www.w3.org/TR/css-masking-1/">CSS Masking Module Level 1</a>
 		[[CSS-MASKING-1]]
 		<dd>
 			Replaces CSS2&sect;11.1.2

css-align-3/Overview.bs

@@ -762,6 +762,11 @@ Distributed Alignment: the ''<content-distribution>/stretch'', ''space-between''
 
 			The default [=fallback alignment=] for this value is ''flex-start''.
 			<span class='note'>(For layout modes other than flex layout, ''flex-start'' is identical to ''start''.)</span>
+
+			Note: This `align-content/stretch` definition applies to the [=content-distribution properties=];
+			the [=self-alignment properties=] 'justify-self'/'align-self' have their own ''justify-self/stretch'' value,
+			which can grow <em>or shrink</em> the [=alignment subject=]
+			to ensure it exactly fits the [=alignment container=].
 	</dl>
 
 	These values are represented with the <<content-distribution>> grammar term: