[css-ruby] Shift nested ruby out of box generation rules, assume it will be handled by layout rules.

Author: fantasai

css-ruby/Overview.html

@@ -553,11 +553,6 @@ <h3 class="heading settled heading" data-level=2.2 id=box-fixup><span class=secn
 			is wrapped in an anonymous <a data-link-type=dfn href=#ruby-annotation-container-box title="ruby annotation container">ruby annotation container</a>.
 	</ol>
 
-	<p>For the purpose of the rules above,
-	a <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a> directly parented by a <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a>
-	is considered to be a <a data-link-type=dfn href=#ruby-base-container-box title="ruby base container">ruby base container</a>.
-	See <a data-link-type=dfn href=#nested-ruby title="nested ruby">nested ruby</a>, below.
-
 	<p class=issue id=issue-f2086090><a class=self-link href=#issue-f2086090></a>Make this into an example:
 		<img src=http://lists.w3.org/Archives/Public/www-archive/2014Jun/att-0027/PastedGraphic-1.png style="display: block; width: 100%">
 
@@ -674,9 +669,9 @@ <h4 class="heading settled heading" data-level=2.3.3 id=nested-pairing><span cla
 	Thus, using nested <a data-link-type=dfn href=#ruby-container title="ruby containers">ruby containers</a> allows the representation
 	of complex spanning relationships.
 
-	<p class=issue id=issue-05f90a82><a class=self-link href=#issue-05f90a82></a>This has to be Level 1 because HTML5 allows it, so we have to handle it. Yay HTML5.
-	(Also, if we’re ever going to support it, it has to be designed into level 1
-	or authors will depend on whatever degenerate behavior falls out.)
+	<p class=issue id=issue-9b177ca3><a class=self-link href=#issue-9b177ca3></a>It’s not clear whether this falls out of layout handling of ruby containers inside ruby bases
+	or needs to be handled specially.
+	Waiting until layout is better-defined to find out...
 
 <h3 class="heading settled heading" data-level=2.4 id=autohide><span class=secno>2.4 </span><span class=content>
 Autohiding Base-identical Annotations</span><a class=self-link href=#autohide></a></h3>
@@ -1731,11 +1726,11 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 
 	<a href=#issue-f2086090> ↵ </a></div><div class=issue>Insert diagram<a href=#issue-0230a91a> ↵ </a></div>
 
-<div class=issue>This has to be Level 1 because HTML5 allows it, so we have to handle it. Yay HTML5.
-	(Also, if we’re ever going to support it, it has to be designed into level 1
-	or authors will depend on whatever degenerate behavior falls out.)
+<div class=issue>It’s not clear whether this falls out of layout handling of ruby containers inside ruby bases
+	or needs to be handled specially.
+	Waiting until layout is better-defined to find out...
 
-<a href=#issue-05f90a82> ↵ </a></div><div class=issue>Specify how these anonymous white space boxes impact layout.
+<a href=#issue-9b177ca3> ↵ </a></div><div class=issue>Specify how these anonymous white space boxes impact layout.
 
 	<a href=#issue-1851041e> ↵ </a></div><div class=issue>Or should it become a quasi-base between two bases?<a href=#issue-029133da> ↵ </a></div>
 	A spanning <div class=issue>

css-ruby/Overview.src.html

@@ -399,11 +399,6 @@ <h3 id="box-fixup">
 			is wrapped in an anonymous <i>ruby annotation container</i>.
 	</ol>
 
-	<p>For the purpose of the rules above,
-	a <i>ruby container</i> directly parented by a <i>ruby container</i>
-	is considered to be a <i>ruby base container</i>.
-	See <i>nested ruby</i>, below.
-
 	<p class="issue">Make this into an example:
 		<img src="http://lists.w3.org/Archives/Public/www-archive/2014Jun/att-0027/PastedGraphic-1.png" style="display: block; width: 100%">
 
@@ -520,9 +515,9 @@ <h4 id="nested-pairing">
 	Thus, using nested <i>ruby containers</i> allows the representation
 	of complex spanning relationships.
 
-	<p class="issue">This has to be Level 1 because HTML5 allows it, so we have to handle it. Yay HTML5.
-	(Also, if we're ever going to support it, it has to be designed into level 1
-	or authors will depend on whatever degenerate behavior falls out.)
+	<p class="issue">It's not clear whether this falls out of layout handling of ruby containers inside ruby bases
+	or needs to be handled specially.
+	Waiting until layout is better-defined to find out...
 
 <h3 id="autohide">
 Autohiding Base-identical Annotations</h3>