[css-display] Define recursive inlinification.

Author: tabatkins

css-display/Overview.bs

@@ -8,7 +8,7 @@ Group: csswg
 Level: 3
 Editor: Tab Atkins Jr., Google, http://xanthir.com/contact/
 Abstract: This module contains the features of CSS relating to the 'display' property and other box-generation details.
-Ignored Terms: show, display-model, display-role, table row group box
+Ignored Terms: show, display-model, display-role, table row group box, formatting context
 Link Defaults: css-lists-3 (property) counter-increment
 </pre>
 
@@ -363,14 +363,15 @@ Automatic Box Type Transformations</h3>
 		</ul>
 	</div>
 
+	When a box is <a>inlinified</a>,
+	it recursively <a>inlinifies</a> all of its in-flow children
+	unless it itself establishes a new formatting context,
+	so that no block-level descendants
+	break up the inline formatting context in which it participates.
+
 	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.
-
-
-
-
 
 <h2 id='box-suppress'>
 Controlling box generation: the 'box-suppress' property</h2>

css-display/Overview.html

@@ -459,14 +459,15 @@ <h3 class="heading settled" data-level=2.5 id=transformations><span class=secno>
 		</ul>
 	</div>
 
+<p>When a box is <a data-link-type=dfn href=#inlinify title=inlinified>inlinified</a>,
+	it recursively <a data-link-type=dfn href=#inlinify title=inlinifies>inlinifies</a> all of its in-flow children
+	unless it itself establishes a new formatting context,
+	so that no block-level descendants
+	break up the inline formatting context in which it participates.</p>
+
 <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>
-
-
-
-
 
 <h2 class="heading settled" data-level=3 id=box-suppress><span class=secno>3 </span><span class=content>
 Controlling box generation: the <a class=property data-link-type=propdesc href=#propdef-box-suppress title=box-suppress>box-suppress</a> property</span><a class=self-link href=#box-suppress></a></h2>
@@ -807,6 +808,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>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,
+			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,
 	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>