Closed
Bug 456112
Opened 17 years ago
Closed 17 years ago
Print & Print Preview Truncates tables and pushes them to a new page
Categories
(Core :: Printing: Output, defect)
Core
Printing: Output
Tracking
()
RESOLVED
DUPLICATE
of bug 129941
People
(Reporter: pizza23, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080919032843 Minefield/3.1b1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080919032843 Minefield/3.1b1pre
If a table is longer then on page, Firefox only prints the first page of the table. It will also push the table to another page if it will not fit on the current page completely.
Reproducible: Always
Steps to Reproduce:
1. Go to the URL
2. Tell it to Print, or Print Preview
Actual Results:
You see the Div border extended to the bottom of the first page, with no content,
The second page has the first page of the table, the third page has the close of the div. The three other pages of the table (according to other browsers) is gone.
Expected Results:
The table should have started on the first page, and continued on as many additional pages as necessary.
I have seen some OLD bug Listings that where close, but did not fully address the issue. Nor where they current. This is up to date as of today the 19th of Sept, 2008
Updated•17 years ago
|
Group: core-security
Severity: critical → major
Component: General → Printing: Output
Product: Firefox → Core
QA Contact: general → printing
Version: unspecified → Trunk
Comment 1•17 years ago
|
||
(In reply to comment #0)
> If a table is longer then on page, Firefox only prints the first page of the
> table.
That's the long-standing bug 129941 -- elements with "overflow: [non-visible]" are clipped at one page. In this case, it's specifically from a div with class="fixed_frame_body", which gets "overflow: auto" from that class.
FWIW, as a workaround, I think this could be alleviated by using a separate printing-only set of style rules, using "overflow: visible" (or leaving overflow unset) in that one.
> It will also push the table to another page if it will not fit on the
> current page completely.
That part is actually a feature, not a bug. :) For elements that we can't currently split (like overflow:non-visible elements), it's better to push them to a new page, to reduce the amount that we have to clip.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Updated•17 years ago
|
OS: Windows XP → All
Hardware: PC → All
| Reporter | ||
Updated•17 years ago
|
| Reporter | ||
Comment 2•17 years ago
|
||
Thank you for your comment, My confusion then would be is Overflow: auto; not visible It is displayed within the boundaries of it's container.
Comment 3•17 years ago
|
||
I don't entirely understand what you're asking. Can you use complete sentences? :)
If my comment wasn't clear, bug 129941 affects all values of overflow *other* than visible, including "overflow: auto".
| Reporter | ||
Comment 4•17 years ago
|
||
Thank you, Yes, that clarifies your prior comment.
You need to log in
before you can comment on or make changes to this bug.
Description
•