Closed
Bug 279322
Opened 20 years ago
Closed 19 years ago
page-break-before/after is ignored on first/last row and row-group
Categories
(Core :: Layout: Tables, defect)
Core
Layout: Tables
Tracking
()
RESOLVED
DUPLICATE
of bug 136714
People
(Reporter: MatsPalmgren_bugz, Unassigned)
Details
(Keywords: testcase)
Attachments
(3 files)
page-break-before/after is ignored on first row and row-group
STEPS TO REPRODUCE:
1. load testcases
2. Print Preview
See text in testcase for expected results.
|
Reporter | |
Comment 1•20 years ago
|
||
|
|
Reporter | |
Comment 2•20 years ago
|
||
|
|
Reporter | |
Updated•20 years ago
|
Summary: page-break-before/after is ignored on first row and row-group → page-break-before/after is ignored on first/last row and row-group
|
||
Comment 3•19 years ago
|
||
I've found that the problem also appears when the element page-break-after is
applied to is nested in a table (I didn't try other containing block-level
elements). Consider:
<html>
<head>
<STYLE type="text/css">
P.page-break {
page-break-after: always;
}
</STYLE>
</head>
<body>
<P class="page-break">On Page 1</P>
<P class="page-break">On Page 2</P>
<table>
<tr>
<td>
<P class="page-break">Should be on page 3</P>
<P class="page-break">Should be on page 4</P>
</td>
</tr>
</table>
</body>
</html>
|
|
Reporter | |
Comment 4•19 years ago
|
||
Aaron, please upload the example file using the "Create a New Attachment" link
on the bug page instead of pasting markup in comments. Thanks.
|
|
||
Comment 5•19 years ago
|
||
as requested.
|
||
Comment 6•19 years ago
|
||
Duplicate of bug 136714?
|
|
||
Comment 7•19 years ago
|
||
(In reply to comment #6)
> Duplicate of bug 136714?
>
Looking through 136714, it does appear to me to be so, at least in the test cases I sent. Incidentally, I agree with the messages on that thread. I think MZ should work similarly here to IE.
|
|
||
Comment 8•19 years ago
|
||
*** This bug has been marked as a duplicate of 136714 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•