Closed
Bug 203022
Opened 22 years ago
Closed 16 years ago
page-break-after not working when assinged to a <tr> element
Categories
(Core :: Printing: Output, defect)
Core
Printing: Output
Tracking
()
RESOLVED
DUPLICATE
of bug 136714
People
(Reporter: pedro, Unassigned)
Details
(Keywords: css2, testcase)
Attachments
(1 file)
|
307 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
After assigning the page-break-after:always to the <tr> element, found that only
the first (of 7) pages was correctly displayed. Print preview showed that the
document had 2 pages (instead of 7) and the second one was empty. Works in other
browsers as expected
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Expected Results:
7 pages of information
|
||
Comment 1•22 years ago
|
||
Please attach a testcase?
Summary: page-break-after not winking when assinged to a <tr> element → page-break-after not working when assinged to a <tr> element
|
||
Comment 2•20 years ago
|
||
This bug is still present as of Mozilla 1.7.1, Windows.
It seems to require an outer table and an inner table, with the inner table
containing the "page-break-after: always" instruction.
Here's a minimal test case:
<html>
<body>
<!-- Outer Table -->
<table><tr><td>
<!-- Inner Table -->
<table>
<tr style="page-break-after: always">
<td>Content here</td>
</tr>
<tr>
<td>Content here</td>
</tr>
<!-- Close Inner Table -->
</table>
<!-- Close Outer Table -->
</td></tr></table>
</body>
</html>
If you do a print preview on a file containing these tags, you'll get two pages,
with the second blank. Only the first row from the inner table is displayed
(and this remains true regardless of how many rows there are).
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
|
|
||
Comment 3•20 years ago
|
||
Steve, can you _attach_ the testcase, instead of pasting it in? That would
allow easy testing of the bug and all...
|
|
||
Comment 4•20 years ago
|
||
Certainly.
|
||
Updated•20 years ago
|
|
||
Comment 5•20 years ago
|
||
See discussion in bug 136714.
|
|
||
Comment 6•20 years ago
|
||
The discussion in that bug is related, and comment #5 of that bug describes this
problem exactly. I don't think they're duplicates, however.
Bug 136714 covers the problem that page-break-after doesn't behave in the
intuitive way that IE allows (inserting a page break after the row).
This bug covers the specific problem that Mozilla throws away all table content
after the row containing the "page-break-after: always" tag. Whether or not the
W3C allows the tag, I don't think this is appropriate behavior -- if Bug 136714
is declared WONTFIX/INVALID, then ignore the tag and show the content.
|
||
Comment 7•16 years ago
|
||
We have numerous issues regarding page-break-after and page-break-before. We need to herd the bug reports together. Resolving as duplicate of bug 136714.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•