[css-ruby] Add section on text decoration. Clarify that margin boxes of internal ruby boxes are accomodated in layout.

Author: fantasai

css-ruby/Overview.bs

@@ -663,7 +663,7 @@ Ruby Layout</h2>
 	aligned according to its 'vertical-align' property
 	exactly as if its <i>ruby bases</i> were a regular sequence of inline boxes.
 	Each <i>ruby base container</i> is sized and positioned
-	to contain exactly the full height of its <i>ruby bases</i>.
+	to contain exactly all of its <i>ruby bases</i>’ margin boxes.
 
 	<p><i>Ruby annotations</i> associated with the <i>base level</i>
 	are then positioned with respect to their <i>ruby base boxes</i>
@@ -672,7 +672,15 @@ Ruby Layout</h2>
 	are aligned to each other as if they were inline boxes
 	participating in the same inline formatting context.
 	Each <i>ruby annotation container</i> is sized and positioned
-	to contain exactly the full height of its <i>ruby annotations</i>.
+	to contain exactly all of its <i>ruby annotations</i>’ margin boxes.
+
+	<p><i>Ruby annotation containers</i> are stacked outward
+	over or under their corresponding <i>ruby base container</i>,
+	without any intervening space.
+
+	<p class="issue">Should block-axis margins collapse?
+	This makes layout more robust,
+	but is inconsistent with how inlines behave along the inline-axis.
 
 	<p>A ruby container (or fragment thereof)
 	measures as wide as the content of its widest level.
@@ -687,6 +695,9 @@ Ruby Layout</h2>
 	when ruby content is narrower than the measure of its box
 	is specified by the 'ruby-align' property.
 
+	<p class="issue">Should the ruby bases and annotations size to the column,
+	or size to the content?
+
 <h3 id="inter-character-layout">
 Inter-character Ruby Layout</h3>
 
@@ -1234,6 +1245,27 @@ Ruby Text Distribution: the 'ruby-align' property</h3>
 		elements. This ratio is computed by taking into consideration the widest
 		element within each column.</p>
 -->
+
+<h3 id="ruby-text-decoration">
+Ruby Text Decoration</h3>
+
+	<p>Text decoration does not propagate from the base text to the annotations.
+	<p>When text decoration is specified on an ancestor of the ruby,
+	it is drawn across the entire content area of the ruby base container,
+	including any extra space added on either side of the ruby base contents to accommodate long annotations.
+	When text decoration is specified on a ruby base itself,
+	this extra space is not decorated,
+	similar to how a box's own padding is not decorated when text decoration is specified directly on that box. [[!CSS3-TEXT-DECOR]]
+
+	<p>Text decoration may be specified directly on ruby base containers
+	and ruby annotation containers:
+	in such cases it is propagated to all of the container's bases or annotations (respectively),
+	and is also drawn between them.
+
+	<p class="issue">This section needs some clarification about
+	drawing decorations between the content of adjacent bases/annotations.
+	Depends on if those boxes are as wide as their column or not.
+
 <h2 id="edge-effects">
 Edge Effects</h2>
 

css-ruby/Overview.html

@@ -246,6 +246,8 @@ <h2 class="no-num no-toc no-ref heading settled" id="contents"><span class="cont
 Sharing Annotation Space: the <span class="property" data-lt="ruby-merge">ruby-merge</span> property</span></a>
       <li><a href="#ruby-align-property"><span class="secno">4.3</span> <span class="content"><span></span>
 Ruby Text Distribution: the <span class="property" data-lt="ruby-align">ruby-align</span> property</span></a>
+      <li><a href="#ruby-text-decoration"><span class="secno">4.4</span> <span class="content">
+Ruby Text Decoration</span></a>
      </ul>
     <li><a href="#edge-effects"><span class="secno">5</span> <span class="content">
 Edge Effects</span></a>
@@ -1180,7 +1182,7 @@ <h2 class="heading settled" data-level="3" id="ruby-layout"><span class="secno">
 	aligned according to its <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css2/visudet.html#propdef-vertical-align">vertical-align</a> property
 	exactly as if its <i>ruby bases</i> were a regular sequence of inline boxes.
 	Each <i>ruby base container</i> is sized and positioned
-	to contain exactly the full height of its <i>ruby bases</i>.
+	to contain exactly all of its <i>ruby bases</i>’ margin boxes.
 
 	</p>
    <p><i>Ruby annotations</i> associated with the <i>base level</i>
@@ -1190,7 +1192,17 @@ <h2 class="heading settled" data-level="3" id="ruby-layout"><span class="secno">
 	are aligned to each other as if they were inline boxes
 	participating in the same inline formatting context.
 	Each <i>ruby annotation container</i> is sized and positioned
-	to contain exactly the full height of its <i>ruby annotations</i>.
+	to contain exactly all of its <i>ruby annotations</i>’ margin boxes.
+
+	</p>
+   <p><i>Ruby annotation containers</i> are stacked outward
+	over or under their corresponding <i>ruby base container</i>,
+	without any intervening space.
+
+	</p>
+   <p class="issue" id="issue-b36a4b34"><a class="self-link" href="#issue-b36a4b34"></a>Should block-axis margins collapse?
+	This makes layout more robust,
+	but is inconsistent with how inlines behave along the inline-axis.
 
 	</p>
    <p>A ruby container (or fragment thereof)
@@ -1207,6 +1219,10 @@ <h2 class="heading settled" data-level="3" id="ruby-layout"><span class="secno">
 	when ruby content is narrower than the measure of its box
 	is specified by the <a class="property" data-link-type="propdesc" href="#propdef-ruby-align">ruby-align</a> property.
 
+	</p>
+   <p class="issue" id="issue-2847424d"><a class="self-link" href="#issue-2847424d"></a>Should the ruby bases and annotations size to the column,
+	or size to the content?
+
 </p>
    <h3 class="heading settled" data-level="3.1" id="inter-character-layout"><span class="secno">3.1. </span><span class="content">
 Inter-character Ruby Layout</span><a class="self-link" href="#inter-character-layout"></a></h3>
@@ -2013,6 +2029,32 @@ <h3 class="heading settled" data-level="4.3" id="ruby-align-property"><span clas
 
    <p class="issue" id="issue-c66abaa7"><a class="self-link" href="#issue-c66abaa7"></a>Add a paragraph explaining how to distribute space in situations with spanning annotations.
 
+
+</p>
+   <h3 class="heading settled" data-level="4.4" id="ruby-text-decoration"><span class="secno">4.4. </span><span class="content">
+Ruby Text Decoration</span><a class="self-link" href="#ruby-text-decoration"></a></h3>
+
+	
+   <p>Text decoration does not propagate from the base text to the annotations.
+	</p>
+   <p>When text decoration is specified on an ancestor of the ruby,
+	it is drawn across the entire content area of the ruby base container,
+	including any extra space added on either side of the ruby base contents to accommodate long annotations.
+	When text decoration is specified on a ruby base itself,
+	this extra space is not decorated,
+	similar to how a box’s own padding is not decorated when text decoration is specified directly on that box. <a data-link-type="biblio" href="#biblio-css3-text-decor">[CSS3-TEXT-DECOR]</a>
+
+	</p>
+   <p>Text decoration may be specified directly on ruby base containers
+	and ruby annotation containers:
+	in such cases it is propagated to all of the container’s bases or annotations (respectively),
+	and is also drawn between them.
+
+	</p>
+   <p class="issue" id="issue-01ada3e0"><a class="self-link" href="#issue-01ada3e0"></a>This section needs some clarification about
+	drawing decorations between the content of adjacent bases/annotations.
+	Depends on if those boxes are as wide as their column or not.
+
 </p>
    <h2 class="heading settled" data-level="5" id="edge-effects"><span class="secno">5. </span><span class="content">
 Edge Effects</span><a class="self-link" href="#edge-effects"></a></h2>
@@ -2478,15 +2520,15 @@ <h3 class="no-num heading settled" id="normative"><span class="content">Normativ
    <dd>Bert Bos; et al. <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607">Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification</a>. 7 June 2011. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a>
    <dt id="biblio-css3-display"><a class="self-link" href="#biblio-css3-display"></a>[CSS3-DISPLAY]
    <dd>Tab Atkins. <a href="http://www.w3.org/TR/2014/WD-css-display-3-20140220/">CSS Display Module Level 3</a>. 20 February 2014. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2014/WD-css-display-3-20140220/">http://www.w3.org/TR/2014/WD-css-display-3-20140220/</a>
+   <dt id="biblio-css3-text-decor"><a class="self-link" href="#biblio-css3-text-decor"></a>[CSS3-TEXT-DECOR]
+   <dd>Elika J. Etemad; Koji Ishii. <a href="http://www.w3.org/TR/2013/CR-css-text-decor-3-20130801/">CSS Text Decoration Module Level 3</a>. 1 August 2013. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2013/CR-css-text-decor-3-20130801/">http://www.w3.org/TR/2013/CR-css-text-decor-3-20130801/</a>
    <dt id="biblio-css3text"><a class="self-link" href="#biblio-css3text"></a>[CSS3TEXT]
    <dd>Elika J. Etemad; Koji Ishii. <a href="http://www.w3.org/TR/2012/WD-css3-text-20121113/">CSS Text Module Level 3</a>. 13 November 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-css3-text-20121113/">http://www.w3.org/TR/2012/WD-css3-text-20121113/</a>
    <dt id="biblio-rfc2119"><a class="self-link" href="#biblio-rfc2119"></a>[rfc2119]
    <dd>S. Bradner. <a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>. March 1997. Best Current Practice. URL: <a href="https://tools.ietf.org/html/rfc2119">https://tools.ietf.org/html/rfc2119</a>
   </dl>
   <h3 class="no-num heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
   <dl>
-   <dt id="biblio-css3-text-decor"><a class="self-link" href="#biblio-css3-text-decor"></a>[CSS3-TEXT-DECOR]
-   <dd>Elika J. Etemad; Koji Ishii. <a href="http://www.w3.org/TR/2013/CR-css-text-decor-3-20130801/">CSS Text Decoration Module Level 3</a>. 1 August 2013. W3C Candidate Recommendation. (Work in progress.) URL: <a href="http://www.w3.org/TR/2013/CR-css-text-decor-3-20130801/">http://www.w3.org/TR/2013/CR-css-text-decor-3-20130801/</a>
    <dt id="biblio-css3-writing-modes"><a class="self-link" href="#biblio-css3-writing-modes"></a>[CSS3-WRITING-MODES]
    <dd>Elika J. Etemad; Koji Ishii. <a href="http://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/">CSS Writing Modes Module Level 3</a>. 15 November 2012. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/">http://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/</a>
    <dt id="biblio-css3val"><a class="self-link" href="#biblio-css3val"></a>[CSS3VAL]
@@ -2637,6 +2679,15 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
 	Waiting until layout is better-defined to find out...
 
 <a href="#issue-9b177ca3"> ↵ </a></div>
+   <div class="issue">Should block-axis margins collapse?
+	This makes layout more robust,
+	but is inconsistent with how inlines behave along the inline-axis.
+
+	<a href="#issue-b36a4b34"> ↵ </a></div>
+   <div class="issue">Should the ruby bases and annotations size to the column,
+	or size to the content?
+
+<a href="#issue-2847424d"> ↵ </a></div>
    <div class="issue">Or should it become a quasi-base between two bases?<a href="#issue-029133da"> ↵ </a></div>
    <div class="issue">
 	Insert scanned example so people don’t think this is just the ramblings of an insane spec-writer.
@@ -2645,7 +2696,13 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
    <div class="issue"><span class="issuehead">Issue-107: </span> Roland Steiner has requested the addition of an auto value as default. See <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&amp;hdr-1-name=subject&amp;hdr-1-query=ruby-position%3A+undesirable+default+value+%27before%27+for+complex+ruby&amp;hdr-2-name=from&amp;hdr-2-query=&amp;hdr-3-name=message-id&amp;hdr-3-query=&amp;period_month=&amp;period_year=&amp;index-grp=Public__FULL&amp;index-type=t&amp;type-index=www-style&amp;resultsperpage=20&amp;sortby=date">this thread</a> and <a href="http://www.w3.org/Search/Mail/Public/advanced_search?keywords=&amp;hdr-1-name=subject&amp;hdr-1-query=Styling+of+complex+Ruby&amp;hdr-2-name=from&amp;hdr-2-query=&amp;hdr-3-name=message-id&amp;hdr-3-query=&amp;period_month=&amp;period_year=&amp;index-grp=Public__FULL&amp;index-type=t&amp;type-index=public-i18n-core&amp;resultsperpage=20&amp;sortby=date">this one</a>.<a href="#issue-8b54b949"> ↵ </a></div>
    <div class="issue">Add a paragraph explaining how to distribute space in situations with spanning annotations.
 
+
 <a href="#issue-c66abaa7"> ↵ </a></div>
+   <div class="issue">This section needs some clarification about
+	drawing decorations between the content of adjacent bases/annotations.
+	Depends on if those boxes are as wide as their column or not.
+
+<a href="#issue-01ada3e0"> ↵ </a></div>
    <div class="issue">
 		I suspect overhanging interacts with alignment in some cases;
 		might need to look into this later.