@@ -679,7 +679,7 @@ <h4 id=nested-pairing><span class=secno>2.3.1. </span> Nested Ruby</h4>
679679 < h3 id =autohide > < span class =secno > 2.4. </ span > Autohiding Annotations</ h3 >
680680
681681 < p > If a < a href ="#ruby-annotation-box "> < i > ruby annotation</ i > </ a > has the
682- exact same content as its base, it is < dfn id =hidden
682+ exact same text content as its base, it is < dfn id =hidden
683683 title ="hidden ruby annotation | hidden annotation "> hidden</ dfn > . Hiding a
684684 < a href ="#ruby-annotation-box "> < i > ruby annotation</ i > </ a > does not affect
685685 annotation pairing or the block-axis positioning of boxes in other < a
@@ -717,13 +717,14 @@ <h3 id=autohide><span class=secno>2.4. </span> Autohiding Annotations</h3>
717717 </ div >
718718 </ div >
719719
720- < p class =note > Future levels of CSS Ruby may add controls for this, however
721- in this level it is always forced.
720+ < p class =note > Future levels of CSS Ruby may add controls for this, but in
721+ this level it is always forced.
722722
723723 < p > The content comparison for this auto-hiding behavior takes place prior
724- to white space collapsing. < span class =issue > Is this easier? Or after
725- collapsing is easier? We should do whatever is easier, as it really
726- doesn't matter much which way to go. </ span >
724+ to white space collapsing and ignores elements (considers only the
725+ < code > textContent</ code > of the boxes). < span class =issue > Is before or
726+ after white space collapsing easier?We should do whatever is easier, as it
727+ really doesn't matter much which way to go. </ span >
727728
728729 < h3 id =white-space > < span class =secno > 2.5. </ span > White Space</ h3 >
729730
0 commit comments