[css-position-3][editorial] Update/clear changes list

Author: fantasai

css-position-3/Overview.bs

@@ -1730,143 +1730,14 @@ Acknowledgments</h2>
 
 <h2 class="no-num" id="changes">Changes</h2>
 
-	The following significant changes were made since the
-	<a href="https://www.w3.org/TR/2024/WD-css-position-3-20240810/">10 August 2024 Working Draft</a>:
-	<ul>
-		<li>None. Editorial updates only (as of 10 March 2025).
-	</ul>
-
-
-	The following significant changes were made since the
-	<a href="https://www.w3.org/TR/2023/WD-css-position-3-20230403/">3 April 2023 Working Draft</a>:
-	<ul>
-		<li>Adjusted alignment of [=absolutely positioned boxes=]
-			to, by default, constrain the box to its [=containing block=].
-			See [[#abspos-layout]].
-			(<a href="https://github.com/w3c/csswg-drafts/issues/10316">Issue 10316</a>)
-		<li>Specified the [=static-position rectangle=] of [=top layer=] boxes to be the [=initial containing block=].
-			(<a href="https://github.com/w3c/csswg-drafts/issues/9939">Issue 9939</a>)
-		<li>Clarified that the [=fixed positioning containing block=]
-			corresponds to the [=layout viewport=] (specifically) in [=continuous media=].
-			(<a href="https://github.com/w3c/csswg-drafts/issues/6453">Issue 6453</a>)
-	</ul>
 
-	The following significant changes were made since the
-	<a href="https://www.w3.org/TR/2023/WD-css-position-3-20230217/">17 February 2023 Working Draft</a>:
-	<ul>
-		<li>Updated the [[#def-cb|containing block formed by inline boxes fragmented across multiple lines]]
-			to use the endmost edge of all the fragments in each axis;
-			this proposed definition is still under discussion, however.
-			(<a href="https://github.com/w3c/csswg-drafts/issues/8284">Issue 8284</a>)
-	</ul>
-
-	The following significant changes were made since the
-	<a href="https://www.w3.org/TR/2022/WD-css-position-3-20220901/">01 September 2022 Working Draft</a>:
-	<ul>
-		<li>Added [[#stacking]] and defined [=sticky-positioned boxes=]
-			to always form a [=stacking context=].
-			(<a href="https://github.com/w3c/csswg-drafts/issues/1053">Issue 1053</a>)
-		<li>Updated [=sticky positioning=] to using its offsetted positioning
-			for scroll operations.
-			(<a href="https://github.com/w3c/csswg-drafts/issues/7930">Issue 7930</a>)
-		<li>Fixed incorrect/ambiguous translation from CSS2
-			regarding the edges of a fragmented inline box forming a [=containing block=]
-			in the presence of bidi.
-			(<a href="https://github.com/w3c/csswg-drafts/issues/7917">Issue 7917</a>)
-		<li>Defined the [=containing block=] formed by edges of a fragmented inline box
-			to match the Blink implementation
-			(<a href="https://github.com/w3c/csswg-drafts/issues/609">Issue 609</a>)
-			while opening up a discussion on what’s the best thing to do
-			(<a href="https://github.com/w3c/csswg-drafts/issues/8284">Issue 8284</a>)
-		<li>Imported the definition of [=static-position containing block=] from CSS2.
-		<li>Clarified [=writing modes=] used to calculate [=static positions=].
-			(<a href="https://github.com/w3c/csswg-drafts/issues/7599">Issue 7599</a>,
-			 <a href="https://github.com/w3c/csswg-drafts/issues/7612">Issue 7612</a>)
-		<li>Added a note about treating HTML form controls as [=non-replaced=] elements
-			for the purpose of [=absolute positioning=].
-			(<a href="https://github.com/w3c/csswg-drafts/issues/6789">Issue 6789</a>)
-		<li>Corrected duplicate, conflicting “Animation type” lines for 'position'.
-			(<a href="https://github.com/w3c/csswg-drafts/issues/6846">Issue 6846</a>)
-		<li>Clarified “equivalent alignment”.
-			(<a href="https://github.com/w3c/csswg-drafts/issues/6607">Issue 6607</a>)
-	</ul>
+	Significant changes since the <a href="https://www.w3.org/TR/2025/WD-css-position-3-20250311/">11 March 2025 Working Draft</a>:
 
-	The following significant changes were made since the
-	<a href="https://www.w3.org/TR/2021/WD-css-position-3-20211216/">16 December 2021 Working Draft</a>:
+	* Defined the [=initial fixed containing block=] and its relationship to the [=initial containing block=],
+		to give this concept a name.
 
-	<ul>
-		<li>Fixed conceptual definitions of [=static position=] and [=static-position rectangle=]
-			to be consistent with their actual usage.
-		<li>Explicitly defined that [=absolute positioning=] forces the box
-			to establish an [=independent formatting context=]
-			(as previously noted in [[CSS-DISPLAY-3]]).
-			(<a href="https://github.com/w3c/csswg-drafts/issues/7124">Issue 7124</a>)
-	</ul>
-
-	The following significant changes were made since the
-	<a href="https://www.w3.org/TR/2020/WD-css-position-3-20200519/">19 May 2020 Working Draft</a>:
-
-	<ul>
-		<li>Defined automatic sizing of non-replaced absolutely-positioned boxes with an aspect ratio.
-			(<a href="https://github.com/w3c/csswg-drafts/issues/5151">Issue 5151</a>
-			<blockquote>
-				<p><ins>However, if the box has an aspect-ratio,
-				then an [=automatic size=] in the [=ratio-dependent axis=]
-				is instead resolved as a [=max-content size=].
-				When both axes have an [=automatic size=],
-				if only one axis has an ''inset/auto'' inset
-				then that axis is the [=ratio-dependent axis=],
-				else the [=block axis=] is the [=ratio-dependent axis=].
-				An [=automatic size=] in the [=ratio-determining axis=]
-				is determined as above.</ins></p>
-			</blockquote>
-
-		<li>Aligned resolution of auto margins and automatic sizes of positioned boxes with [[CSS2]].
-			(<a href="https://github.com/w3c/csswg-drafts/issues/5374">Issue 5374</a>,
-			 <a href="https://github.com/w3c/csswg-drafts/issues/5077">Issue 5077</a>,
-			 <a href="https://github.com/w3c/csswg-drafts/issues/5327">Issue 5327</a>)
-			<blockquote>
-				<p>If this results in a [=sticky view rectangle=] size in any axis
-				less than the size of the [=border box=] of the [=sticky=] box in that axis,
-				then the effective [=end=]-edge inset in the affected axis is reduced
-				(possibly becoming negative)
-				to bring the [=sticky view rectangle=]’s size up to
-				the size of the [=border box=] in that axis
-				<ins>(where [=end=] is interpreted relative to the [=writing mode=] of the [=containing block=])</ins>.
-			</blockquote>
-			<blockquote>
-				If neither is ''top/auto'',
-				the position is over-constrained;
-				<ins>(with respect to the [=writing mode=] of its [=containing block=])</ins>
-				the [=computed value|computed=] [=CSS/end=] side value is ignored,
-				and its [=used value=] becomes the negation of the [=CSS/start=] side.
-			</blockquote>
-			<blockquote>
-				However,
-				<ins>(all with respect to the [=writing mode=] of the [=containing block=]),
-				if in the [=inline axis=]</ins>
-				the <var>remaining space</var> is negative
-				and both margins are ''margin/auto'',
-				the [=inline-start|start=] margin resolves to zero
-				and the [=inline-end|end=] margin receives the <var>remaining space</var>.
-			</blockquote>
-			<blockquote>
-				<dl class=switch>
-					: If its [=self-alignment property=] in the relevant axis is ''align-self/stretch''
-					: Or if it is ''align-self/normal''
-						and the box is [=non-replaced=] <ins>and has no ''inset/auto'' [=inset property|inset=] in the relevant axis</ins>
-					::
-						Its [=automatic size=] is its [=stretch-fit size=].
-				</dl>
-			</blockquote>
-	</ul>
-
-	The following significant changes were made since the
-	<a href="https://www.w3.org/TR/2016/WD-css-position-3-20160517/">17 May 2016 Working Draft</a>:
-
-	<ul>
-		<li>Rewrote the whole spec for editorial clarity, technical precision, and compatibility with [[CSS-ALIGN-3]], [[CSS-WRITING-MODES-3]], [[CSS-BREAK-3]], and [[CSS-DISPLAY-3]].
-	</ul>
+	See also <a href="https://www.w3.org/TR/2025/WD-css-position-3-20250311/#changes
+">Previous Changes</a>.
 
 <h2 class=no-num id=privacy>
 Privacy Considerations</h2>