[css-values-5] Drop media-progress() and container-progress() for now #11826

Author: fantasai

css-values-5/Overview.bs

@@ -780,31 +780,23 @@ Combination of <<position>></h4>
 ████ █▌   ▐▌   █▌   █████▌ █▌  █▌ █▌
 -->
 
-<h2 id="progress">
-Interpolation Progress Functional Notations</h2>
+<h2 id="progress" oldids="progress-func">
+Interpolation Progress Calculations: the ''progress()'' notation</h2>
 
-	The ''progress()'', ''media-progress()'', and ''container-progress()'' [=functional notations=]
-	represent the proportional distance
+	The <dfn>progress()</dfn> [=functional notation=]
+	represents the proportional distance
 	of a given value (the <dfn noexport>progress value</dfn>)
 	from one value (the <dfn noexport>progress start value</dfn>)
-	to another value (the <dfn noexport>progress end value</dfn>).
-	They allow drawing a progress ratio from
-	[=math functions=], [=media features=], and [=container features=],
-	respectively,
-	following a common syntactic pattern:
-
-	<pre class=prod>
-		<var ignore>progress-function</var>() = <var ignore>progress-function</var>( <var ignore>progress value</var>, <var ignore>start value</var>, <var ignore>end value</var> )
-	</pre>
-
-	Each resolves to a <<number>>
-	by [=calculating a progress function=].
+	to another value (the <dfn noexport>progress end value</dfn>),
+	each represented as a [=calculation=].
+	It is a [=math function=],
+	and can be input into other calculations
+	such as a [=math function=]
+	or a [=mix notation=].
 
 	<div algorithm>
-		To <dfn export>calculate a progress function</dfn>,
-		given a [=progress value=],
-		[=progress start value=],
-		and [=progress end value=]:
+		The ''progress()'' notation resolves to a <<number>>
+		by <dfn noexport lt="calculate a progress function">calculating a progress function</dfn> as follows:
 
 		: If the [=progress start value=] and [=progress end value=] are different values
 		:: <code>([=progress value=] - [=progress start value=]) / ([=progress end value=] - [=progress start value=])</code>.
@@ -813,27 +805,8 @@ Interpolation Progress Functional Notations</h2>
 			depending on whether [=progress value=]
 			is equal to, less than, or greater than
 			the shared value.
-
-		Note: The return value is a plain <<number>>,
-		not [=made consistent=] with its arguments by default.
 	</div>
 
-	The resulting number can then be input into other calculations,
-	such as a [=math function=]
-	or a [=mix notation=].
-
-<h3 id="progress-func">
-Calculated Progress Values: the ''progress()'' notation</h3>
-
-	The <dfn>progress()</dfn> functional notation
-	returns a <<number>> value
-	representing the position of one [=calculation=]
-	(the [=progress value=])
-	between two other [=calculations=]
-	(the [=progress start value=]
-	and [=progress end value=]).
-	''progress()'' is a [=math function=].
-
 	The syntax of ''progress()'' is defined as follows:
 
 	<pre class=prod>
@@ -848,101 +821,11 @@ Calculated Progress Values: the ''progress()'' notation</h3>
 	but must have a [=consistent type=]
 	or else the function is invalid.
 
-	The value of ''progress()'' is a <<number>>,
-	determined by [=calculating a progress function=],
-	then [=made consistent=] with the [=consistent type=] of its arguments.
-
 	ISSUE: Do we need a ''percent-progress()'' notation,
 	or do enough places auto-convert that it's not necessary?
 
 	Note: The ''progress()'' function is essentially syntactic sugar
-	for a particular pattern of ''calc()'' notations,
-	so it's a [=math function=].
-
-<h3 id="media-progress-func">
-Media Query Progress Values: the ''media-progress()'' notation</h3>
-
-	Similar to the ''progress()'' notation,
-	the <dfn>media-progress()</dfn> functional notation
-	returns a <<number>> value
-	representing current value of the specified [=media query=]
-	[[!MEDIAQUERIES-4]]
-	as a [=progress value=]
-	between two explicit values of the [=media query=]
-	(as the [=progress start value=] and [=progress end value=]).
-
-	The syntax of ''media-progress()'' is defined as follows:
-
-	<pre class=prod>
-		<<media-progress()>> = media-progress(<<mf-name>>, <<calc-sum>>, <<calc-sum>>)
-	</pre>
-
-	where the value of the [=media feature=] corresponding to <<mf-name>>
-	represents the [=progress value=],
-	and the two <<calc-sum>> values represent
-	the [=progress start value=] and [=progress end value=],
-	respectively.
-
-	The specified [=media feature=] must be a valid “range” type feature,
-	the specified [=progress start value=] and [=progress end value=]
-	must be valid values for the specified [=media query=],
-	and both [=calculation=] values must have a [=consistent type=],
-	or else the function is invalid.
-
-	The [=progress start value=] and [=progress end value=] [=calculations=]
-	are interpreted as specified for the [=media feature=]
-	(rather than as specified by the context the function is used in).
-
-	The value of ''media-progress()'' is a <<number>>,
-	determined by [=calculating a progress function=].
-
-	Note: ''media-progress()'' is <em>not</em> a [=math function=];
-	it's just a function that evaluates to a <<number>>.
-
-<h3 id="container-progress-func">
-Container Query Progress Values: the ''container-progress()'' notation</h3>
-
-	The <dfn>container-progress()</dfn> functional notation
-	is identical to the ''media-progress()'' functional notation,
-	except that it accepts [=container features=] [[!CSS-CONTAIN-3]]
-	in place of [=media features=].
-
-	The syntax of ''container-progress()'' is defined as follows:
-
-	<pre class=prod>
-		<<container-progress()>> = container-progress(<<mf-name>> [ of <<container-name>> ]?, <<calc-sum>>, <<calc-sum>>)
-	</pre>
-
-	where <<mf-name>> represents a [=size feature=]
-	and the optional <<container-name>> component specifies
-	the named containers to consider when selecting a container
-	to resolve them against.
-	The value of the [=size feature=] is the [=progress value=],
-	and the two <<calc-sum>> values represent
-	the [=progress start value=] and [=progress end value=],
-	respectively.
-
-	The specified <<mf-name>> must be a valid [=size feature=],
-	the specified [=progress start value=] and [=progress end value=]
-	must be valid values for that [=size feature=],
-	and both [=calculation=] values must have a [=consistent type=],
-	or else the function is invalid.
-	''container-progress()'' is only valid in a property value context;
-	it cannot be used in, for example, a [=media query=].
-
-	The [=progress start value=] and [=progress end value=] [=calculations=]
-	are interpreted as specified for the [=size feature=]
-	(rather than as specified by the context the function is used in).
-	If no appropriate containers are found,
-	''container-progress()'' resolves its <<size-feature>> query
-	against the [=small viewport size=].
-
-	The value of ''media-progress()'' is a <<number>>,
-	determined by [=calculating a progress function=].
-
-	Note: ''container-progress()'' is <em>not</em> a [=math function=];
-	it's just a function that evaluates to a <<number>>.
-
+	for a particular pattern of ''calc()'' notations.
 
 <!-- Big Text: *-mix()
 
@@ -4176,35 +4059,14 @@ Acknowledgments</h2>
 <h2 class="no-num" id="changes">
 Changes</h2>
 
-	Changes since the <a href="https://www.w3.org/TR/2024/WD-css-values-5-20240917/">17 September 2024 Working Draft</a>:
+<h3 class=no-num id="changes-recent">
+Recent Changes</h3>
 
-	* Changed the “comma-upgrading” behavior of allowing semicolons
-		to “comma-wrapping” using braces.
-		(<a href="https://github.com/w3c/csswg-drafts/issues/9539">Issue 9539</a>)
-	* Added ''if()''.
-		(<a href="https://github.com/w3c/csswg-drafts/issues/10064">Issue 10064</a>,
-		 <a href="https://github.com/w3c/csswg-drafts/issues/5009#issuecomment-2442787271">Issue 5009</a>)
-	* Added ''inherit()''.
-		(<a href="https://github.com/w3c/csswg-drafts/issues/2864">Issue 2864</a>)
-	* Redesigned ''attr()''.
-		(<a href="https://github.com/w3c/csswg-drafts/issues/10437">Issue 10437</a>,
-		 <a href="https://github.com/w3c/csswg-drafts/issues/5092">Issue 5092</a>,
-		 <a href="https://github.com/w3c/csswg-drafts/issues/5136">Issue 5136</a>)
-	* Changed ''*progress()'' functions to use commas for argument separation,
-		for consistency with ''*mix()'' and ''clamp()''.
-		(<a href="https://github.com/w3c/csswg-drafts/issues/10489">Issue 10489</a>)
-	* Defined new <<boolean-expr[]>> multipler for the [=value definition syntax=].
-		(<a href="https://github.com/w3c/csswg-drafts/issues/10457">Issue 10457</a>)
-	* Imported definition of [=arbitrary substitution function=] from [[CSS-VARIABLES-1]].
-		(<a href="https://github.com/w3c/csswg-drafts/issues/10679">Issue 10679</a>)
-	* Imported the <<syntax>> production from [[css-properties-values-api-1]] (for use in ''attr()'').
-	* Corrected errors in the syntax of ''media-progress()'' and ''container-progress()''.
-
-	Changes since the <a href="https://www.w3.org/TR/2024/WD-css-values-5-20240913/">First Public Working Draft</a> include:
-
-	* Incorporated the definition of <<position>>,
-		extending it to handle [=flow-relative=] positions.
-		(<a href="https://github.com/w3c/csswg-drafts/issues/549#issuecomment-1823607623">Issue 549</a>)
+	Changes since the <a href="https://www.w3.org/TR/2024/WD-css-values-5-20241111/">11 November 2024 Working Draft</a>:
+	* Dropped ''media-progess()'' and ''container-progress()'' in favor of using relevant units in ''progress()''.
+		(<a href="https://github.com/w3c/csswg-drafts/issues/11826">Issue 11826</a>)
+
+	See also <a href="https://www.w3.org/TR/2024/WD-css-values-5-20241111/#changes">earlier changes</a>.
 
 <h3 class=no-num id="additions-L4">
 Additions Since Level 4</h3>