Closed
Bug 332531
Opened 19 years ago
Closed 16 years ago
page-break-before:always on adjacent divs garbles the second one
Categories
(Core :: Layout: Block and Inline, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 132035
People
(Reporter: jpage, Unassigned)
Details
Attachments
(1 file)
|
1.67 KB,
text/html
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; Media Center PC 2.8)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
If you have two consecutive divs and the second one has a page-break-before:always on it, the second div is not printed correctly. It is too tall and its contents are missing. It is wong on the printout and in the print preview. Inserting almost any inline element between them seems to fix it. (EG: < br>)
Reproducible: Always
Steps to Reproduce:
1.Put the html below in to a file and display it.
2.Look at print preview or print it.
3.
Actual Results:
Second page does not contain the correct div contents. The top border of the second div is on the wrong page and it has no contents
Expected Results:
Two pages that look alike.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<style>
.box {border:1px solid red; width:100mm; height:40mm;}
</style>
</HEAD>
<BODY>
<div class="box">Page 1</div>
<div class="box" style="page-break-before:always">Page 2</div>
</BODY>
</HTML>
|
||
Updated•19 years ago
|
Assignee: nobody → dbaron
Component: General → Style System (CSS)
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → Trunk
Assignee: dbaron → nobody
Component: Style System (CSS) → Layout: Block and Inline
QA Contact: ian → layout.block-and-inline
|
||
Comment 1•17 years ago
|
||
|
|
||
Comment 2•17 years ago
|
||
This is still happening for more complex cases in Firefox 3.0 such as test case #2 which I just posted. But the initial test case above no longer produces the issue.
|
||
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•