[css2] added text on page breaks, issue w3c#25

howcom · howcom · commit c91e629fa0f4 · 2007-03-07T00:42:33.000Z
--HG--
extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402639
diff --git a/css2/page.src b/css2/page.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
-<!-- $Id: page.src,v 2.48 2007-02-19 22:05:15 howcome Exp $ -->
+<!-- $Id: page.src,v 2.49 2007-03-07 00:42:33 howcome Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Paged media</TITLE>
@@ -268,11 +268,11 @@ Force one or two page breaks before (after) the generated
 box so that the next page is formatted as a right page.</dd>
 </dl>
 
-<P>Whether the first page of a document is :left or :right depends on
+<p>Whether the first page of a document is :left or :right depends on
 the major writing direction of the document. A conforming user agent
 may interpret the values 'left' and 'right' as 'always'.
 
-<P>A potential page break location is typically under the influence
+<p>A potential page break location is typically under the influence
 of the parent element's <span
 class="propinst-page-break-inside">'page-break-inside'</span>
 property, the <span
@@ -283,10 +283,13 @@ of the following element.  When these properties have values other
 than 'auto', the values 'always', 'left', and 'right' take precedence
 over 'avoid'.  
 
-<P>User Agents must apply these properties to block-level elements
+<p>User Agents must apply these properties to block-level elements
 in the normal flow of the root element. User agents may also apply
 these properties to other elements, e.g., 'table-row' elements.
 
+<p>When a page break splits a box, the box's margins, borders, and
+padding have no visual effect where the split occurs.
+
 
 <h3><a name="break-inside">Breaks inside elements</a>: <span
 class="propinst-orphans">'orphans'</span>, <span
