[css-display-3] Clarify that 'inline-foo' and 'inline foo' compute to each other. #5575

fantasai · fantasai · commit 48ba2b328401 · 2021-08-24T16:19:12.000-07:00
diff --git a/css-display-3/Overview.bs b/css-display-3/Overview.bs
@@ -235,7 +235,7 @@ Box Layout Modes: the 'display' property</h2>
 	Initial: inline
 	Applies to: all elements
 	Inherited: no
-	Computed value: see prose in a variety of specs
+	Computed value: a pair of keywords representing the [=inner display type|inner=] and [=outer display type|outer=] display types plus optional ''list-item'' flag, or a <<display-internal>> or <<display-box>> keyword; see prose in a variety of specs for computation rules
 	Animation type:	not animatable
 	</pre>
 
@@ -771,21 +771,29 @@ Precomposed Inline-level Display Values</h3>
 	<dl dfn-type=value dfn-for="display, <display-legacy>">
 		<dt><dfn>inline-block</dfn>
 		<dd>
-			Behaves as ''inline flow-root''.
+			Computes to ''inline flow-root''.
 
 		<dt><dfn>inline-table</dfn>
 		<dd>
-			Behaves as ''inline table''.
+			Computes to ''inline table''.
 
 		<dt><dfn>inline-flex</dfn>
 		<dd>
-			Behaves as ''inline flex''.
+			Computes to ''inline flex''.
 
 		<dt><dfn>inline-grid</dfn>
 		<dd>
-			Behaves as ''inline grid''.
+			Computes to ''inline grid''.
 	</dl>
 
+	Note: Although these keywords and their equivalents compute to the same value,
+	their [=specified values=] remain distinct.
+
+	Note: The {{Window/getComputedStyle()}} serialization rules
+	will always output these precomposed keywords
+	rather than the equivalent two-keyword pairs
+	due to the [[cssom#serializing-css-values|shortest, most backwards-compatible serialization principle]].
+
 <!--
 ████████  ██        ███████   ██████  ██    ██ ████ ████████ ██    ██
 ██     ██ ██       ██     ██ ██    ██ ██   ██   ██  ██        ██  ██
@@ -1865,7 +1873,24 @@ Changes Since 2020 Candidate Recommendation</h3>
 			Defined that [=replaced elements=] with a [=layout-internal=] 'display'
 			are treated as ''display: inline''.
 			(<a href="https://github.com/w3c/csswg-drafts/issues/6000">Issue 6000</a>)
-		<li id="blockification-computed">
+		<li id="change-legacy-computation">
+			Clarified that the <<display-legacy>> values actually [=computed value|compute=]
+			to the same value as their two-keyword equivalents.
+			(<a href="https://github.com/w3c/csswg-drafts/issues/5575">Issue 5575</a>)
+			<blockquote>
+				<dl>
+					<dt>inline-&hellip;
+					<dd>
+						<del>Behaves as</del> <ins>Computes to</ins> ''inline &hellip;''.
+				</dl>
+				<p class="note"><ins>Note: Although these keywords and their equivalents compute to the same value,
+				their [=specified values=] remain distinct.</ins></p>
+				<p class="note"><ins>Note: The {{Window/getComputedStyle()}} serialization rules
+				will always output these precomposed keywords
+				rather than the equivalent two-keyword pairs
+				due to the [[cssom#serializing-css-values|shortest, most backwards-compatible serialization principle]].</ins></p>
+			</blockquote>
+		<li id="change-blockification-computed">
 			Clarified that [=blockification=] and [=inlinification=] are [=computed value=] changes.
 			(<a href="https://github.com/w3c/csswg-drafts/issues/6251">Issue 6251</a>)
 			<blockquote>
