Skip to content

Commit 391222f

Browse files
committed
Mark paragraph about which side of box is broken as a note, since this is covered in CSS2.1 and Writing Modes.
1 parent f09e2cc commit 391222f

2 files changed

Lines changed: 28 additions & 13 deletions

File tree

css3-background/Overview.html

Lines changed: 20 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3877,13 +3877,16 @@ <h3 id=the-box-decoration-break><span class=secno>7.1. </span>Drawing at
38773877
&lsquo;<code class=css>clone</code>&rsquo;.
38783878
</div>
38793879

3880-
<p>For inline elements, which side of a fragment is the broken edge is
3881-
determined by the parent element's inline progression direction, not its
3882-
containing block. For example, if an inline element whose parent has
3883-
&lsquo;<code class=css>direction: rtl</code>&rsquo; and whose containing
3884-
block has &lsquo;<code class=css>direction: ltr</code>&rsquo; breaks
3885-
across two lines, the left edge of the fragment on the first line will be
3886-
the broken edge.
3880+
<p class=note> For inline elements, which side of a fragment is the broken
3881+
edge is determined by the parent element's inline progression direction.
3882+
For example, if an inline element whose parent has &lsquo;<code
3883+
class=css>direction: rtl</code>&rsquo; breaks across two lines, the
3884+
<em>left</em> edge of the fragment on the first line will be the broken
3885+
edge. (Note in particular that neither the element's own &lsquo;<code
3886+
class=property>direction</code>&rsquo; nor its containing block's
3887+
&lsquo;<code class=property>direction</code>&rsquo; is used.) See <a
3888+
href="#CSS3-WRITING-MODES"
3889+
rel=biblioentry>[CSS3-WRITING-MODES]<!--{{CSS3-WRITING-MODES}}--></a>.
38873890

38883891
<p>UAs may also apply &lsquo;<a href="#box-decoration-break"><code
38893892
class=property>box-decoration-break</code></a>&rsquo; to control rendering
@@ -4715,6 +4718,16 @@ <h3 class=no-num id=other-references> Other References</h3>
47154718
</dd>
47164719
<!---->
47174720

4721+
<dt id=CSS3-WRITING-MODES>[CSS3-WRITING-MODES]
4722+
4723+
<dd>Elika J. Etemad; Koji Ishii; Shinyu Murakami. <a
4724+
href="http://www.w3.org/TR/2011/WD-css3-writing-modes-20110901/"><cite>CSS
4725+
Writing Modes Module Level 3.</cite></a> 1 September 2011. W3C Working
4726+
Draft. (Work in progress.) URL: <a
4727+
href="http://www.w3.org/TR/2011/WD-css3-writing-modes-20110901/">http://www.w3.org/TR/2011/WD-css3-writing-modes-20110901/</a>
4728+
</dd>
4729+
<!---->
4730+
47184731
<dt id=CSS3COLOR>[CSS3COLOR]
47194732

47204733
<dd>Tantek &#199;elik; Chris Lilley; L. David Baron. <a

css3-background/Overview.src.html

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2773,12 +2773,14 @@ <h3 id="the-box-decoration-break">Drawing at Breaks: the 'box-decoration-break'
27732773
''slice'', on the right the value ''clone''.
27742774
</div>
27752775

2776-
<p>For inline elements, which side of a fragment is the broken edge is
2777-
determined by the parent element's inline progression direction, not
2778-
its containing block. For example, if an inline element whose parent has
2779-
''direction: rtl'' and whose containing block has ''direction: ltr''
2780-
breaks across two lines, the left edge of the fragment on the first line
2781-
will be the broken edge.
2776+
<p class=note>
2777+
For inline elements, which side of a fragment is the broken edge is
2778+
determined by the parent element's inline progression direction.
2779+
For example, if an inline element whose parent has ''direction: rtl''
2780+
breaks across two lines, the <em>left</em> edge of the fragment on
2781+
the first line will be the broken edge. (Note in particular that
2782+
neither the element's own 'direction' nor its containing block's
2783+
'direction' is used.) See [[CSS3-WRITING-MODES]].
27822784

27832785
<p>UAs may also apply 'box-decoration-break' to control rendering
27842786
at bidi-imposed breaks, i.e. when bidi reordering causes an inline

0 commit comments

Comments
 (0)