8000 sync content outside the page box section with CSS2.1 · w3c/csswg-drafts@ee8a844 · GitHub
Skip to content

Commit ee8a844

Browse files
fantasaifantasai
committed
sync content outside the page box section with CSS2.1
1 parent fc706ba commit ee8a844

2 files changed

Lines changed: 18 additions & 14 deletions

File tree

‎css3-page/Overview.html‎

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -593,22 +593,24 @@ <h3 id=content-outside-box><span class=secno>4.1 </span>Content outside
593593
the page box</h3>
594594

595595
<p>When formatting content in the page model, some content may end up
596-
outside the page box. For example, an element whose <span
597-
class=property>&lsquo;<code
598-
class=property>white-space</code>&rsquo;</span> property has the value
599-
<span class=css>&lsquo;<code class=property>pre</code>&rsquo;</span> can
600-
generate a box that is wider than the page box. Also, when boxes are
601-
positioned absolutely, they may end up in "inconvenient" locations. For
602-
example, images may be placed on the edge of the page box. Similarly,
603-
when boxes use fixed or relative positioning, they can end up outside of
604-
the page box.</p>
596+
outside the page box. For example, an element whose &lsquo;<code
597+
class=property>white-space</code>&rsquo; property has the value
598+
&lsquo;<code class=property>pre</code>&rsquo; can generate a box that is
599+
wider than the page box. As another example, when boxes are positioned
600+
absolutely or relatively, they may end up in "inconvenient" locations.
601+
For example, images may be placed on the edge of the page box or 100,000
602+
meters below the page box.</p>
605603

606604
<p>A specification for the exact formatting of such elements lies outside
607605
the scope of this document. However, it is recommended that authors and
608606
user agents observe the following general principles concerning content
609607
outside the page box:</p>
610608

611609
<ul>
610+
<li>
611+
<p>Content should be allowed slightly beyond the page box to allow pages
612+
to "bleed".
613+
612614
<li>
613615
<p>User agents <em class=RFC2119>SHOULD</em> avoid generating a large
614616
number of content-empty pages to honor the positioning of elements

‎css3-page/Overview.src.html‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -320,18 +320,20 @@ <h2 id="page-box-page-rule">The Page Model</h2>
320320
<h3 id="content-outside-box">Content outside the page box</h3>
321321

322322
<p>When formatting content in the page model, some content may end up outside the
323-
page box. For example, an element whose <span class="property">'white-space'</span> property has the value <span class="css">'pre'</span> can generate a box that is wider than the page box. Also,
324-
when boxes are positioned absolutely, they may end up in "inconvenient"
325-
locations. For example, images may be placed on the edge of the page box.
326-
Similarly, when boxes use fixed or relative positioning, they can end up
327-
outside of the page box.</p>
323+
page box. For example, an element whose 'white-space' property has the value
324+
'pre' can generate a box that is wider than the page box. As another example,
325+
when boxes are positioned absolutely or relatively, they may end up in
326+
"inconvenient" locations. For example, images may be placed on the edge of
327+
the page box or 100,000 meters below the page box. </p>
328328

329329
<p>A specification for the exact formatting of such elements lies outside the
330330
scope of this document. However, it is recommended that authors and user agents
331331
observe the following general principles concerning content outside the page
332332
box:</p>
333333

334334
<ul>
335+
<li><p>Content should be allowed slightly beyond the page box to allow pages
336+
to "bleed".
335337
<li><p>User agents <em class="RFC2119">SHOULD</em> avoid generating a large
336338
number of content-empty pages to honor the positioning of elements (e.g.,
337339
printing 100 blank pages is probably neither the author's nor the user's

0 commit comments

Comments
 (0)