[css-ruby] Define blockification of internal ruby boxes.

Author: fantasai

css-ruby/Overview.html

@@ -54,7 +54,7 @@
 </p>
   <h1 class="p-name no-ref" id=title>CSS Ruby Layout Module Level 1</h1>
   <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>Editor’s Draft,
-    <span class=dt-updated><span class=value-title title=20140712>12 July 2014</span></span></span></h2>
+    <span class=dt-updated><span class=value-title title=20140718>18 July 2014</span></span></span></h2>
   <div data-fill-with=spec-metadata><dl>
 	<dt>This version:
 	<dd><a class=u-url href=http://dev.w3.org/csswg/css-ruby-1/>http://dev.w3.org/csswg/css-ruby-1/</a>
@@ -130,7 +130,8 @@ <h2 class="no-num no-toc no-ref heading settled heading" id=contents><span class
 		<ul class=toc>
 		<li><a href=#ruby-display><span class=secno>2.1</span>  Ruby-specific <span class=property data-link-type=propdesc title=display>display</span> Values</a>
 			<ul class=toc>
-			<li><a href=#display-inside-outside><span class=secno>2.1.1</span>  Ruby-specific <span class=property data-link-type=propdesc title=display-inside>display-inside</span> and <span class=property data-link-type=propdesc title=display-outside>display-outside</span> values</a></ul>
+			<li><a href=#display-inside-outside><span class=secno>2.1.1</span>  Ruby-specific <span class=property data-link-type=propdesc title=display-inside>display-inside</span> and <span class=property data-link-type=propdesc title=display-outside>display-outside</span> values</a>
+			<li><a href=#block-ruby><span class=secno>2.1.2</span>  Non-Inline Ruby</a></ul>
 		<li><a href=#box-fixup><span class=secno>2.2</span>  Anonymous Ruby Box Generation</a>
 		<li><a href=#ruby-pairing><span class=secno>2.3</span>  Annotation Pairing</a>
 			<ul class=toc>
@@ -369,7 +370,7 @@ <h3 class="heading settled heading" data-level=2.1 id=ruby-display><span class=s
 	like inline boxes, they break across lines and
 	their base-level contents participate in the same inline formatting context as the <a data-link-type=dfn href=#ruby-container title="ruby container">ruby container</a> itself.
 	<a data-link-type=dfn href=#ruby-base-box title="ruby bases">Ruby bases</a>, <a data-link-type=dfn href=#ruby-annotation-box title="ruby annotations">ruby annotations</a>, <a data-link-type=dfn href=#ruby-base-container-box title="ruby base containers">ruby base containers</a>, and <a data-link-type=dfn href=#ruby-annotation-container-box title="ruby annotation containers">ruby annotation containers</a>
-	are <dfn data-dfn-type=dfn data-noexport="" id=internal-ruby-boxes>internal ruby boxes<a class=self-link href=#internal-ruby-boxes></a></dfn>:
+	are <dfn data-dfn-type=dfn data-noexport="" id=internal-ruby-boxes title="internal ruby boxes|internal ruby display types">internal ruby boxes<a class=self-link href=#internal-ruby-boxes></a></dfn>:
 	like <i data-link-type=dfn title="internal table elements">internal table elements</i>,
 	they have specific roles in ruby layout.
 	<span class=issue id=issue-ca88244c><a class=self-link href=#issue-ca88244c></a>Are internal ruby boxes inline-level?</span>
@@ -407,7 +408,13 @@ <h4 class="heading settled heading" data-level=2.1.1 id=display-inside-outside><
 		    <td><span class=css data-link-type=maybe title=auto>auto</span>
 	</table>
 
-	<p id=block-ruby>If an element has a computed <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-inside title=display-inside>display-inside</a> of <a class=css data-link-type=maybe href=#ruby title=ruby>ruby</a>
+	<p>See the <a href=http://www.w3.org/TR/css-display/>CSS Display Module</a>
+	for more information on <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-inside title=display-inside>display-inside</a> and <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-outside title=display-outside>display-outside</a>. <a data-biblio-type=normative data-link-type=biblio href=#biblio-css3-display title=biblio-css3-display>[CSS3-DISPLAY]</a>
+
+<h4 class="heading settled heading" data-level=2.1.2 id=block-ruby><span class=secno>2.1.2 </span><span class=content>
+Non-Inline Ruby</span><a class=self-link href=#block-ruby></a></h4>
+
+	<p>If an element has a computed <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-inside title=display-inside>display-inside</a> of <a class=css data-link-type=maybe href=#ruby title=ruby>ruby</a>
 	and a computed <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-outside title=display-outside>display-outside</a> other than <span class=css data-link-type=maybe title=inline-level>inline-level</span>,
 	then it generates two boxes:
 	a principal block container box of the required <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-outside title=display-outside>display-outside</a> type,
@@ -417,9 +424,18 @@ <h4 class="heading settled heading" data-level=2.1.1 id=display-inside-outside><
 	This allows styling the element as a block,
 	while correctly maintaining the internal ruby structure.
 
+	<p class=issue id=issue-b4dd0f5f><a class=self-link href=#issue-b4dd0f5f></a>
+	Note: There is no dedicated block-level <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> shorthand keyword
+	because ruby is fundamentally an inline layout feature.
+	<span class=issue id=issue-feac3754><a class=self-link href=#issue-feac3754></a>We might need one to handle <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> blockification, though. :(</span>
 
-	<p>See the <a href=http://www.w3.org/TR/css-display/>CSS Display Module</a>
-	for more information on <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-inside title=display-inside>display-inside</a> and <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-outside title=display-outside>display-outside</a>. <a data-biblio-type=normative data-link-type=biblio href=#biblio-css3-display title=biblio-css3-display>[CSS3-DISPLAY]</a>
+	<p>Absolute positioning or floating an element causes its <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> value
+	to compute to a block-level equivalent. (See <a data-biblio-type=normative data-link-type=biblio href=#biblio-css21 title=biblio-css21>[CSS21]</a> section 9.7.)
+	This is equivalent to setting its <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#propdef-display-outside title=display-outside>display-outside</a> to <span class=css data-link-type=maybe title=block-level>block-level</span>.
+	<span class=issue id=issue-de71092e><a class=self-link href=#issue-de71092e></a>This should go into the Display module.</span>
+	For the <a data-link-type=dfn href=#internal-ruby-boxes title="internal ruby display types">internal ruby display types</a>,
+	this causes their <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> value to compute to <span class=css data-link-type=maybe title=block>block</span>.
+	<span class=issue id=issue-93d00b01><a class=self-link href=#issue-93d00b01></a>Once that’s done, this can become a note.</span>
 
 <h3 class="heading settled heading" data-level=2.2 id=box-fixup><span class=secno>2.2 </span><span class=content>
 Anonymous Ruby Box Generation</span><a class=self-link href=#box-fixup></a></h3>
@@ -1682,6 +1698,7 @@ <h2 class="no-num no-ref heading settled heading" id=index><span class=content>
 <li>inter-character, <a href=#valdef-ruby-position.inter-character title="section 4.1">4.1</a>
 <li>inter-level white space, <a href=#inter-level-white-space title="section 2.2">2.2</a>
 <li>internal ruby boxes, <a href=#internal-ruby-boxes title="section 2.1">2.1</a>
+<li>internal ruby display types, <a href=#internal-ruby-boxes title="section 2.1">2.1</a>
 <li>inter-segment white space, <a href=#inter-segment-white-space title="section 2.2">2.2</a>
 <li>intra-level white space, <a href=#intra-level-white-space title="section 2.2">2.2</a>
 <li>intra-ruby white space, <a href=#intra-ruby-white-space title="section 2.2">2.2</a>
@@ -1749,7 +1766,17 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 
 <div class=issue>Are internal ruby boxes inline-level?<a href=#issue-ca88244c> ↵ </a></div>
 
-	<div class=issue>The goal of this is to simplify the layout model by suppressing any line breaks within ruby annotations.
+	<div class=issue>
+	Note: There is no dedicated block-level <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> shorthand keyword
+	because ruby is fundamentally an inline layout feature.
+	<span class=issue>We might need one to handle <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> blockification, though. :(</span>
+
+	<a href=#issue-b4dd0f5f> ↵ </a></div><div class=issue>We might need one to handle <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> blockification, though. :(<a href=#issue-feac3754> ↵ </a></div>
+
+	<div class=issue>This should go into the Display module.<a href=#issue-de71092e> ↵ </a></div>
+	For the <div class=issue>Once that’s done, this can become a note.<a href=#issue-93d00b01> ↵ </a></div>
+
+<div class=issue>The goal of this is to simplify the layout model by suppressing any line breaks within ruby annotations.
 			Alternatively we could try to define some kind of acceptable behavior for them.
 
 		<a href=#issue-8af70305> ↵ </a></div><div class=issue>Make this into an example:

css-ruby/Overview.src.html

@@ -212,7 +212,7 @@ <h3 id="ruby-display">
 	like inline boxes, they break across lines and
 	their base-level contents participate in the same inline formatting context as the <i>ruby container</i> itself.
 	<i>Ruby bases</i>, <i>ruby annotations</i>, <i>ruby base containers</i>, and <i>ruby annotation containers</i>
-	are <dfn>internal ruby boxes</dfn>:
+	are <dfn title="internal ruby boxes|internal ruby display types">internal ruby boxes</dfn>:
 	like <i>internal table elements</i>,
 	they have specific roles in ruby layout.
 	<span class="issue">Are internal ruby boxes inline-level?</span>
@@ -250,7 +250,13 @@ <h4 id="display-inside-outside">
 		    <td>''auto''
 	</table>
 
-	<p id="block-ruby">If an element has a computed 'display-inside' of ''ruby''
+	<p>See the <a href="http://www.w3.org/TR/css-display/">CSS Display Module</a>
+	for more information on 'display-inside' and 'display-outside'. [[!CSS3-DISPLAY]]
+
+<h4 id="block-ruby">
+Non-Inline Ruby</h4>
+
+	<p>If an element has a computed 'display-inside' of ''ruby''
 	and a computed 'display-outside' other than ''inline-level'',
 	then it generates two boxes:
 	a principal block container box of the required 'display-outside' type,
@@ -259,13 +265,19 @@ <h4 id="display-inside-outside">
 	(and if inheritable, inherit to the <i>ruby container box</i>).
 	This allows styling the element as a block,
 	while correctly maintaining the internal ruby structure.
-<!--
+
+	<p class="issue">
 	Note: There is no dedicated block-level 'display' shorthand keyword
 	because ruby is fundamentally an inline layout feature.
--->
-
-	<p>See the <a href="http://www.w3.org/TR/css-display/">CSS Display Module</a>
-	for more information on 'display-inside' and 'display-outside'. [[!CSS3-DISPLAY]]
+	<span class="issue">We might need one to handle 'display' blockification, though. :(</span>
+
+	<p>Absolute positioning or floating an element causes its 'display' value
+	to compute to a block-level equivalent. (See [[!CSS21]] section 9.7.)
+	This is equivalent to setting its 'display-outside' to ''block-level''.
+	<span class="issue">This should go into the Display module.</span>
+	For the <i>internal ruby display types</i>,
+	this causes their 'display' value to compute to ''block''.
+	<span class="issue">Once that's done, this can become a note.</span>
 
 <h3 id="box-fixup">
 Anonymous Ruby Box Generation</h3>