[css-values-5] Never mind, media-progress() and container-progress() should eval their calculations in the MQ/CQ context, so should *not* be consistent. #10890

Author: tabatkins

css-values-5/Overview.bs

@@ -548,9 +548,8 @@ Interpolation Progress Functional Notations</h2>
 			is equal to, less than, or greater than
 			the shared value.
 
-		In either case, the result is a <<number>>,
-		[=made consistent=] with the [=consistent type=]
-		of the three arguments.
+		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,
@@ -583,7 +582,8 @@ Calculated Progress Values: the ''progress()'' notation</h3>
 	or else the function is invalid.
 
 	The result will be a <<number>>,
-	determined by [=calculating a progress function=].
+	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?
@@ -616,8 +616,10 @@ Media Query Progress Values: the ''media-progress()'' notation</h3>
 	The specified [=media query=] must be a valid “range” type query,
 	and the specified [=progress start value=] and [=progress end value=]
 	must be valid values for the specified [=media query=],
-	and must have a [=consistent type=],
 	or else the function is invalid.
+	Units in the [=progress start value=] and [=progress end value=]
+	are interpreted as specified for the [=media feature=]
+	(rather than as specified by the context the function is used in).
 
 	The result will be a <<number>>,
 	determined by [=calculating a progress function=].
@@ -647,9 +649,12 @@ Container Query Progress Values: the ''container-progress()'' notation</h3>
 	must be valid values for the specified <<size-feature>>,
 	and must have a [=consistent type=],
 	or else the function is invalid.
+	Units in the [=progress start value=] and [=progress end value=]
+	are interpreted as specified for the [=size feature=]
+	(rather than as specified by the context the function is used in).
 
 	The result will be a <<number>>,
-	[=made consistent=] with the [=consistent type=] of the arguments.
+	determined by [=calculating a progress function=].
 
 	If no appropriate containers are found,
 	''container-progress()'' resolves its <<size-feature>> query