W3C home > Mailing lists > Public > public-css-commits@w3.org > February 2012

csswg/css3-background Overview.html,1.275,1.276 Overview.src.html,1.290,1.291

From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 15 Feb 2012 17:03:06 +0000
To: public-css-commits@w3.org
Message-Id: <E1RxiG2-00021e-Mm@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-background
In directory hutz:/tmp/cvs-serv7744

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Update to latest wording for box fragments, fix error in bidi breaking paragraph.

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-background/Overview.html,v
retrieving revision 1.275
retrieving revision 1.276
diff -u -d -r1.275 -r1.276
--- Overview.html	9 Feb 2012 15:53:37 -0000	1.275
+++ Overview.html	15 Feb 2012 17:03:03 -0000	1.276
@@ -22,13 +22,13 @@
 
    <h1>CSS Backgrounds and Borders Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 9 February
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 15 February
     2012</h2>
 
    <dl>
     <dt>This version:
 
-    <dd><!-- <a href="http://www.w3.org/TR/2012/CR-css3-background-20120209">http://www.w3.org/TR/2012/ED-css3-background-20120209/</a> -->
+    <dd><!-- <a href="http://www.w3.org/TR/2012/CR-css3-background-20120215">http://www.w3.org/TR/2012/ED-css3-background-20120215/</a> -->
      <a
      href="http://dev.w3.org/csswg/css3-background/">http://dev.w3.org/csswg/css3-background/</a>
      
@@ -3801,62 +3801,65 @@
    elements, at a line break<!-- ISSUE-182-->, the &lsquo;<a
    href="#box-decoration-break"><code
    class=property>box-decoration-break</code></a>&rsquo; property specifies
-   whether individual boxes are treated as broken pieces of one continuous
-   box, or whether each box is individually wrapped with the border and
+   whether box fragments are treated as broken fragments of one continuous
+   box, or whether each fragment is individually wrapped with the border and
    padding. For backgrounds it defines how the <a class=index
    href="#background-positioning-area"
    id=background-positioning-area2>background positioning area</a> is derived
-   from these multiple boxes and how the element's background is drawn within
-   them. Values have the following meanings:
+   from these multiple fragments and how the element's background is drawn
+   within them. Values have the following meanings:
 
   <dl>
    <dt><dfn id=clone>&lsquo;<code class=css>clone</code>&rsquo;</dfn>
 
-   <dd>Each box is independently wrapped with the border and padding. The
-    &lsquo;<a href="#border-radius"><code
+   <dd>Each box fragment is independently wrapped with the border and
+    padding. The &lsquo;<a href="#border-radius"><code
     class=property>border-radius</code></a>&rsquo; and &lsquo;<a
     href="#border-image"><code class=property>border-image</code></a>&rsquo;
     and &lsquo;<a href="#box-shadow"><code
     class=property>box-shadow</code></a>&rsquo;, if any, are applied to each
-    box independently. The background is drawn independently in each box of
-    the element. A no-repeat background image will thus be rendered once in
-    each box of the element.
+    fragment independently. The background is drawn independently in each
+    fragment of the element. A no-repeat background image will thus be
+    rendered once in each fragment of the element.
 
    <dt><dfn id=slice>&lsquo;<code class=css>slice</code>&rsquo;</dfn>
 
    <dd>
-    <p>No border and no padding are inserted at the break. No box-shadow is
-     drawn at the broken edge; &lsquo;<a href="#border-radius"><code
+    <p>No border and no padding are inserted at a break. No box-shadow is
+     drawn at a broken edge; &lsquo;<a href="#border-radius"><code
      class=property>border-radius</code></a>&rsquo; does not apply to its
      corners; and the &lsquo;<a href="#border-image"><code
      class=property>border-image</code></a>&rsquo; is rendered for the whole
      box as if it were unbroken. The effect is as though the element were
-     rendered with no break present, and then sliced by the break afterward.
+     rendered with no breaks present, and then sliced by the breaks
+     afterward.
 
     <p>Backgrounds are drawn as if, after the element has been laid out
      (including any justification, bidi reordering, page breaks, etc.), all
-     the element's boxes are taken and put one after the other in visual
-     order. The background is applied to the bounding box of this composite
-     box and then the boxes are put back, with their share of the background.</p>
+     the element's box fragments were taken and put one after the other in
+     visual order. The background is applied to the bounding box of this
+     composite box and then the fragments are put back, with each with its
+     share of the background.</p>
 
-    <p>For boxes broken across lines, first boxes on the same line are
-     connected in visual order. Then boxes on subsequent lines are ordered
-     according to the element's inline progression direction and aligned on
-     the baseline. For example in a left-to-right containing block
+    <p>For boxes broken across lines, first fragments on the same line are
+     connected in visual order. Then fragments on subsequent lines are
+     ordered according to the element's inline progression direction and
+     aligned on the baseline. For example in a left-to-right containing block
      (&lsquo;<code class=property>direction</code>&rsquo; is &lsquo;<code
-     class=css>ltr</code>&rsquo;), the first box is the leftmost box on the
-     first line and boxes from subsequent lines are put to the right of it.
-     In a right-to-left containing block, the first box is the rightmost on
-     the first line and subsequent boxes are put to the left of it.</p>
+     class=css>ltr</code>&rsquo;), the first fragment is the leftmost
+     fragment on the first line and fragments from subsequent lines are put
+     to the right of it. In a right-to-left containing block, the first
+     fragment is the rightmost on the first line and subsequent fragments are
+     put to the left of it.</p>
 
     <p>For boxes broken across columns, the columns are treated as one
      continuous element, as if the column boxes were glued together in the
      block progression direction of the multi-column element. For boxes
      broken across pages, the page content areas are glued together in the
      block progression direction of the root element. In these cases, if the
-     pieces have different widths (heights, if the root element /
-     multi-column element is in vertical text mode), then each piece draws
-     its background assuming that the whole element has the same width
+     box fragments have different widths (heights, if the root element /
+     multi-column element is in a vertical writing mode), then each piece
+     draws its background assuming that the whole element has the same width
      (height) as this piece. This ensures that right-aligned images stay
      aligned to the right edge, left-aligned images stay aligned to the left
      edge, and centered images stay centered.
@@ -3874,11 +3877,13 @@
     &lsquo;<code class=css>clone</code>&rsquo;.
   </div>
 
-  <p>For inline elements side of the box that breaks is determined by the
-   element's inline progression direction, not that of the containing block.
-   For example, the first part of an inline element with &lsquo;<code
-   class=css>direction: rtl</code>&rsquo; inside a block with &lsquo;<code
-   class=css>direction: ltr</code>&rsquo; will break on the left side.
+  <p>For inline elements, which side of a fragment is the broken edge is
+   determined by the parent element's inline progression direction, not its
+   containing block. For example, if an inline element whose parent has
+   &lsquo;<code class=css>direction: rtl</code>&rsquo; and whose containing
+   block has &lsquo;<code class=css>direction: ltr</code>&rsquo; breaks
+   across two lines, the left edge of the fragment on the first line will be
+   the broken edge.
 
   <p>UAs may also apply &lsquo;<a href="#box-decoration-break"><code
    class=property>box-decoration-break</code></a>&rsquo; to control rendering

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-background/Overview.src.html,v
retrieving revision 1.290
retrieving revision 1.291
diff -u -d -r1.290 -r1.291
--- Overview.src.html	9 Feb 2012 15:53:37 -0000	1.290
+++ Overview.src.html	15 Feb 2012 17:03:04 -0000	1.291
@@ -2708,53 +2708,54 @@
 <p>When a box is broken at a page break, column break, or, for inline
 elements, at a line break<!-- ISSUE-182-->, the
 'box-decoration-break' property specifies
-whether individual boxes are treated as broken pieces of one continuous box,
-or whether each box is individually wrapped with the border and padding.
+whether box fragments are treated as broken fragments of one continuous box,
+or whether each fragment is individually wrapped with the border and padding.
 For backgrounds it defines how the <span class=index>background
-positioning area</span> is derived from these multiple boxes and how
+positioning area</span> is derived from these multiple fragments and how
 the element's background is drawn within them. Values have the following
 meanings:
 
 <dl>
   <dt><dfn>''clone''</dfn>
-  <dd>Each box is independently wrapped with the border and padding.
+  <dd>Each box fragment is independently wrapped with the border and padding.
     The 'border-radius' and 'border-image' and 'box-shadow', if any,
-    are applied to each box independently. The background is drawn
-    independently in each box of the element. A no-repeat background
-    image will thus be rendered once in each box of the element.
+    are applied to each fragment independently. The background is drawn
+    independently in each fragment of the element. A no-repeat background
+    image will thus be rendered once in each fragment of the element.
 
   <dt><dfn>''slice''</dfn>
-  <dd><p>No border and no padding are inserted at the break. No box-shadow
-    is drawn at the broken edge; 'border-radius' does not apply to its
+  <dd><p>No border and no padding are inserted at a break. No box-shadow
+    is drawn at a broken edge; 'border-radius' does not apply to its
     corners; and the 'border-image' is rendered for the whole box as if
     it were unbroken. The effect is as though the element were rendered
-    with no break present, and then sliced by the break afterward.
+    with no breaks present, and then sliced by the breaks afterward.
 
     <p>Backgrounds are drawn as if, after the element has been laid out
     (including any justification, bidi reordering, page breaks, etc.),
-    all the element's boxes are taken and put one after the other in
-    visual order. The background is applied to the bounding box of
-    this composite box and then the boxes are put back, with their
-    share of the background.</p>
+    all the element's box fragments were taken and put one after the
+    other in visual order. The background is applied to the bounding box
+    of this composite box and then the fragments are put back, with each
+    with its share of the background.</p>
 
-    <p>For boxes broken across lines, first boxes on the same line are
-    connected in visual order. Then boxes on subsequent lines are
+    <p>For boxes broken across lines, first fragments on the same line are
+    connected in visual order. Then fragments on subsequent lines are
     ordered according to the element's inline progression direction and
     aligned on the baseline.
     For example in a left-to-right containing block ('direction' is
-    ''ltr''), the first box is the leftmost box on the first line and
-    boxes from subsequent lines are put to the right of it. In a
-    right-to-left containing block, the first box is the rightmost on
-    the first line and subsequent boxes are put to the left of it.</p>
+    ''ltr''), the first fragment is the leftmost fragment on the first
+    line and fragments from subsequent lines are put to the right of it.
+    In a right-to-left containing block, the first fragment is the
+    rightmost on the first line and subsequent fragments are put to the
+    left of it.</p>
 
     <p>For boxes broken across columns, the columns are treated as
     one continuous element, as if the column boxes were glued together
     in the block progression direction of the multi-column element.
     For boxes broken across pages, the page content areas are glued
     together in the block progression direction of the root element.
-    In these cases, if the pieces have different widths (heights, if
-    the root element / multi-column element is in vertical text mode),
-    then each piece draws its background assuming that the
+    In these cases, if the box fragments have different widths (heights,
+    if the root element / multi-column element is in a vertical writing
+    mode), then each piece draws its background assuming that the
     whole element has the same width (height) as this piece. This
     ensures that right-aligned images stay aligned to the right edge,
     left-aligned images stay aligned to the left edge, and centered
@@ -2772,11 +2773,12 @@
   ''slice'', on the right the value ''clone''.
 </div>
 
-<p>For inline elements side of the box that breaks is determined
-by the element's inline progression direction, not that of the
-containing block. For example, the first part of an inline element
-with ''direction: rtl'' inside a block with ''direction: ltr''
-will break on the left side.
+<p>For inline elements, which side of a fragment is the broken edge is
+determined by the parent element's inline progression direction, not
+its containing block. For example, if an inline element whose parent has
+''direction: rtl'' and whose containing block has ''direction: ltr''
+breaks across two lines, the left edge of the fragment on the first line
+will be the broken edge.
 
 <p>UAs may also apply 'box-decoration-break' to control rendering
 at bidi-imposed breaks, i.e. when bidi reordering causes an inline
Received on Wednesday, 15 February 2012 17:03:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:50 UTC