[css-display] Per WG resolution, make all the appendix B resolutions normative.

Author: tabatkins

css-display/Overview.bs

@@ -951,53 +951,18 @@ HTML Elements {#unbox-html}
 
 	: <{br}>
 	: <{wbr}>
-	::
-		Issue: Ask the WG.
-		Probably should just treat as ''display: none'',
-		because they normally don't have contents,
-		but theoretically they could be treated as "containing" a line feed or zwnj, respectively.
-
-	: <{button}>
-	::
-		Issue: Ask the WG.
-		<{button}> is rendered via standard CSS,
-		but it's often a form control,
-		and looks identical to <code>&lt;input type=button></code>,
-		which is *definitely* in the "semi-replaced" camp
-		that gets ''display: none''.
-		Which should it be consistent with?
-
 	: <{meter}>
 	: <{progress}>
-	::
-		Issue: Ask the WG.
-		These elements are probably replaced elements,
-		but they do have reasonable contents inside of them.
-
 	: <{applet}>
 	: <{canvas}>
 	: <{embed}>
 	: <{object}>
-	::
-		When acting as a [=replaced element=],
-		''display: contents'' behaves as ''display: none''.
-
-		Issue: When non-replaced and displaying their contents,
-		should we treat as a normal element
-		and just strip the wrapper?
-
 	: <{audio}>
 	: <{iframe}>
 	: <{img}>
 	: <{video}>
-	::
-		''display: contents'' behaves as ''display: none''.
-
 	: <{frame}>
 	: <{frameset}>
-	::
-		''display: contents'' behaves as ''display: none''.
-
 	: <{input}>
 	: <{textarea}>
 	: <{select}>
@@ -1010,6 +975,7 @@ HTML Elements {#unbox-html}
 		so it does not have magical display behavior.
 		(Thus, it reacts to ''display: contents'' normally.)
 
+	: <{button}>
 	: <{details}>
 	: <{fieldset}>
 	::
@@ -1024,65 +990,21 @@ HTML Elements {#unbox-html}
 SVG Elements {#unbox-svg}
 ---------------------------
 
-<div class=issue>
-	Discussed in <a href="https://github.com/w3c/svgwg/issues/305">GitHub</a>.
-
-	SVG can be broken down into the following categories of elements:
-
 	: Root <{svg}>
 	::
-		Establishes the SVG formatting context.
-		Three options:
-
-		1. Treat as ''display: none''. (Contents can't usefully be hoisted.)
-		2. Strip the element,
-			but generate an anonymous SVG rendering context around contiguous SVG contents.
-			(In other words, internal SVG elements auto-wrap themselves,
-			like internal table elements do.)
-		3. Strip the element,
-			treat internal SVG elements similar to unknown HTML elements
-			(render as inline by default).
+		''display: contents'' behaves as ''display: none''.
 
 	: Nested <{svg}>
 	: <{g}>
 	: <{use}> (treated as a Shadow DOM container)
-	::
-		Basically just a wrapping element,
-		could reasonably handle ''display: contents'' normally.
-
-	: Shape elements
-	::
-		Core rendering elements,
-		and usually empty.
-		(Contents, if present, are completely ignored.)
-		Could either strip normally and hoist contents,
-		or just treat as ''display: none''.
-
-	: <{text}>
-	::
-		Renders contained text,
-		but text doesn't display without a <{text}> wrapper.
-		Therefore, should probably ''display: none''.
-
 	: <{tspan}>
 	::
-		Like a <{span}>,
-		can probably usefully be stripped and have the contents hoisted.
-
-	: <{defs}>
-	:: Could theoretically be stripped and display its contents,
-		but that has negative usefulness,
-		so should probably just continue to not display contents.
-		(In other words, continue to ignore 'display' and suppress all boxes, as normal.)
+		''display: contents'' strips the element from the formatting tree,
+		and hoists its contents up to display in its place.
 
-	: all other elements
+	: all other SVG elements
 	::
-		Don't generate boxes anyway,
-		so they ignore 'display' entirely.
-</div>
-
-
-
+		''display: contents'' behaves as ''display: none''.
 
 <h2 class=no-num id="acknowledgments">
 Acknowledgments</h2>