[css-display] Add issue about recursive inlinification.

Author: tabatkins

css-display/Overview.bs

@@ -366,6 +366,8 @@ Automatic Box Type Transformations</h3>
 	The root element’s display type is always <a>blockified</a>.
 	Additionally, a 'display-outside' of ''display-outside/contents'' computes to ''block-level'' on the root element.
 
+	Issue: Move the definition of recursive inlinification from Ruby to here.
+
 
 
 

css-display/Overview.html

@@ -462,6 +462,8 @@ <h3 class="heading settled" data-level=2.5 id=transformations><span class=secno>
 <p>The root element’s display type is always <a data-link-type=dfn href=#blockify title=blockified>blockified</a>.
 	Additionally, a <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> of <a class=css data-link-for=display-outside data-link-type=maybe href=#valdef-display-outside-contents title=contents>contents</a> computes to <a class=css data-link-type=maybe href=#valdef-display-outside-block-level title=block-level>block-level</a> on the root element.</p>
 
+<p class=issue id=issue-d4a1c253><a class=self-link href=#issue-d4a1c253></a>Move the definition of recursive inlinification from Ruby to here.</p>
+
 
 
 
@@ -805,6 +807,6 @@ <h2 class="no-num no-ref heading settled" id=property-index><span class=content>
 
 <h2 class="no-num heading settled" id=issues-index><span class=content>Issues Index</span><a class=self-link href=#issues-index></a></h2><div style="counter-reset: issue"><div class=issue><a class=css data-link-for=display-outside data-link-type=maybe href=#valdef-display-outside-contents title=contents>contents</a> currently only has an effect on box generation and layout.
 			Other things that care about the document tree are unaffected, like counter scopes.
-			Is this what we want?<a href=#issue-1cacf007> ↵ </a></div><div class=issue>Define handling of whitespace containing out-of-flow elements between run-ins,
+			Is this what we want?<a href=#issue-1cacf007> ↵ </a></div><div class=issue>Move the definition of recursive inlinification from Ruby to here.<a href=#issue-d4a1c253> ↵ </a></div><div class=issue>Define handling of whitespace containing out-of-flow elements between run-ins,
 	run-ins that contain block-level content (<a data-link-type=dfn href=#inlinify title=inlinify>inlinify</a> the contents recursively?),
 	and anything else in bz’s feedback.<a href=#issue-803bbb08> ↵ </a></div></div>