Merge branch 'w3c:main' into main

Author: khushalsagar

CONTRIBUTING.md

@@ -39,11 +39,30 @@ 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) originating from your own fork. 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-anchor-position-1/Overview.bs

@@ -171,9 +171,10 @@ for a given positioned element.
 with the ''implicit'' keyword,
 rather than referring to some 'anchor-name' value.
 
-A ''::before'', ''::after'' or ''::backdrop'' [=pseudo-element=]
-has the same [=implicit anchor element=]
-as its [=originating element=].
+[=Pseudo-element=]
+have the same [=implicit anchor element=]
+as its [=originating element=],
+unless otherwise specified.
 
 Note: Without this, these [=pseudo-elements=], which are often inaccessible
 by other specifications, cannot be positioned with [=implicit anchor elements=].
@@ -267,6 +268,13 @@ or nothing (a missing specifier).
 		before reaching |query el|'s [=containing block=]
 		is either not [=absolutely positioned=]
 		or precedes |query el| in the tree order.
+
+	* |el| is either an [=element=],
+		or a [=pseudo-element=] that acts like one.
+
+		Issue: define the term that actually means this,
+		matching ::before/after/backdrop/etc
+		(but not ::marker/placeholder/etc whose box is not detectable).
 </div>
 
 <!-- Big Text: default
@@ -308,22 +316,16 @@ in ''anchor()'' and ''anchor-size()''.
 <div class=example>
 	For example, in the following code
 	both ''.foo'' and ''.bar'' elements
-	can use the same positioning properties and fallback,
+	can use the same positioning properties,
 	just changing the anchor element they're referring to:
 
 	<pre highlight=css>
 	.anchored {
 		position: absolute;
-		position-fallback: --under-then-over;
-	}
-
-	@position-fallback --under-then-over {
-		@try {
-			// No &lt;anchor-element> specified,
-			// so it takes from 'anchor-default'.
-			top: calc(.5em + anchor(outside));
-			bottom: auto;
-		}
+		top: calc(.5em + anchor(outside));
+		/* Since no anchor name was specified,
+		   this automatically refers to the
+		   default anchor element. */
 	}
 
 	.foo.anchored {