[css-display] Remove issue about changing initial values. Remove incorrect note about redundant expansions.

Author: tabatkins

css-display/Overview.bs

@@ -219,28 +219,11 @@ The 'display' shorthand property</h3>
 	Media: see individual properties
 	</pre>
 
-	<p>
-		The single-keyword values listed explicitly in the grammar above are handled specially,
-		for legacy reasons.
-		All other single-keyword values,
-		and all other values in general,
-		are handled as normal for shorthands.
-
-	<p class='issue'>
-		The general rule for new layout modes seems to be that they're block-level by default.
-		However, this conflicts with the default value of 'display-outside', which is ''inline-level''.
-		What's the best way to address this?
-		Simplest answer is to just expand this list of special values as we go along.
-		Another possibility is to magic up the expansion in a different way,
-		so that if the value is just a 'display-inside' keyword,
-		'display-outside' defaults to ''block-level''.
-		If the latter is chosen, we could remove several more of the special expansions below
-		(all the ones that are identical to a 'display-inside' value).
-
-	Note: Several of the "special" expansions below are actually just what the shorthand would expand to normally.
-	They're included here for clarity,
-	as they're very familiar from long usage in CSS 2.1,
-	before the 'display' property became a shorthand.
+	The single-keyword values listed explicitly in the grammar above are handled specially,
+	for legacy reasons.
+	All other single-keyword values,
+	and all other values in general,
+	are handled as normal for shorthands.
 
 	<dl dfn-type="value" dfn-for="display">
 		<dt><dfn>inline</dfn>

css-display/Overview.html

@@ -304,28 +304,11 @@ <h3 class="heading settled heading" data-level=2.4 id=the-display><span class=se
 The <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> shorthand property</span><a class=self-link href=#the-display></a></h3>
 
 <table class="definition propdef"><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-display>display<a class=self-link href=#propdef-display></a></dfn><tr><th>Value:<td class=prod>inline | block | list-item | inline-list-item | inline-block | table | inline-table | table-cell | table-caption | flex | inline-flex | grid | inline-grid | [ <a class=production data-link-type=propdesc href=#propdef-display-inside title=display-inside>&lt;‘display-inside’&gt;</a> || <a class=production data-link-type=propdesc href=#propdef-display-outside title=display-outside>&lt;‘display-outside’&gt;</a> || <a class=production data-link-type=propdesc href=#propdef-display-extras title=display-extras>&lt;‘display-extras’&gt;</a> ]<tr><th>Initial:<td>see individual properties<tr><th>Applies to:<td>see individual properties<tr><th>Inherited:<td>see individual properties<tr><th>Media:<td>see individual properties<tr><th>Computed value:<td>see individual properties<tr><th>Animatable:<td>see individual properties</table>
-	<p>
-		The single-keyword values listed explicitly in the grammar above are handled specially,
-		for legacy reasons.
-		All other single-keyword values,
-		and all other values in general,
-		are handled as normal for shorthands.
-
-	<p class=issue id=issue-49dc1da3><a class=self-link href=#issue-49dc1da3></a>
-		The general rule for new layout modes seems to be that they’re block-level by default.
-		However, this conflicts with the default value of <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a>, which is <a class=css data-link-type=maybe href=#valuedef-inline-level title=inline-level>inline-level</a>.
-		What’s the best way to address this?
-		Simplest answer is to just expand this list of special values as we go along.
-		Another possibility is to magic up the expansion in a different way,
-		so that if the value is just a <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> keyword,
-		<a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> defaults to <a class=css data-link-type=maybe href=#valuedef-block-level title=block-level>block-level</a>.
-		If the latter is chosen, we could remove several more of the special expansions below
-		(all the ones that are identical to a <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> value).
-
-<p class=note>	Note: Several of the "special" expansions below are actually just what the shorthand would expand to normally.
-	They’re included here for clarity,
-	as they’re very familiar from long usage in CSS 2.1,
-	before the <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> property became a shorthand.
+<p>	The single-keyword values listed explicitly in the grammar above are handled specially,
+	for legacy reasons.
+	All other single-keyword values,
+	and all other values in general,
+	are handled as normal for shorthands.
 
 	<dl data-dfn-for=display data-dfn-type=value>
 		<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-inline>inline<a class=self-link href=#valuedef-inline></a></dfn>
@@ -636,17 +619,6 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 		or just have them all be separate properties?
 
 <a href=#issue-70026084> ↵ </a></div><div class=issue>
-		The general rule for new layout modes seems to be that they’re block-level by default.
-		However, this conflicts with the default value of <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a>, which is <a class=css data-link-type=maybe href=#valuedef-inline-level title=inline-level>inline-level</a>.
-		What’s the best way to address this?
-		Simplest answer is to just expand this list of special values as we go along.
-		Another possibility is to magic up the expansion in a different way,
-		so that if the value is just a <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> keyword,
-		<a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> defaults to <a class=css data-link-type=maybe href=#valuedef-block-level title=block-level>block-level</a>.
-		If the latter is chosen, we could remove several more of the special expansions below
-		(all the ones that are identical to a <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> value).
-
-<a href=#issue-49dc1da3> ↵ </a></div><div class=issue>
 		Is there a need for a value that suppresses box generation for layout purposes,
 		but still generates them for the purposes of animations/counters/etc.?