div overflow:auto printing problems

NEW
Unassigned

Status

()

Core
Printing: Output
P4
normal
16 years ago
4 years ago

People

(Reporter: André Schild, Unassigned)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
When doing a printpreview or print of the url above, then the content is printed
on one page with a scrollbar.

I expected the content to be printed on multiple pages.

The "default" stylesheet who is used to display the DIV tag in 350px height and
overflow:auto is still used in some way when we wish to print the content.

Since we more and more use the div height:XXX and overflow:auto to replace
frames, this is a very nasty problem when the pages are printed.

PC IE5.x and MAC IE5.x doe print the content on multiple pages, just as intended.


André

Comment 1

16 years ago
Relevant part of CSS2(http://www.w3.org/TR/REC-CSS2/visufx.html#propdef-overflow):
scroll
This value indicates that the content is clipped and that if the user agent uses
scrolling mechanism that is visible on the screen (such as a scroll bar or a
panner), that mechanism should be displayed for a box whether or not any of its
content is clipped. This avoids any problem with scrollbars appearing and
disappearing in a dynamic environment. When this value is specified and the
target medium is 'print' or 'projection', overflowing content should be printed.

I believe this means that overflow:scroll should extend the box until all the
text fits within it, and push the rest of the page down.  However, it appears
the correct rendering is not well defined, although what we are doing now is
definitely wrong.
(Reporter)

Comment 2

16 years ago
>I believe this means that overflow:scroll should extend the box until all the
>text fits within it, and push the rest of the page down.  However, it appears
>the correct rendering is not well defined, although what we are doing now is
>definitely wrong.
When using overflow:scroll normaly you set a height to the box, so it has
something to scroll. 

What should be rendered on a printer (ie. all non-scrollbar capable devices) is
not well defined.
But since the intention of the webdesigner for overflow:scroll is to make the
content accessible, it should probably just extend the box.


overflow:auto is actually handled in most modern browsers like scroll, with the
exception that the scrollbars are only displayed when needed.

Comment 3

16 years ago
-->
Assignee: rods → karnaze
(Reporter)

Comment 4

16 years ago
No intention to move this bug to confirmed ?

Comment 5

16 years ago
confirming with 2002110408/trunk/win2k. the div extends for the content, but
doesn't go onto the next page when printed.
Severity: major → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

16 years ago
Priority: -- → P4
Target Milestone: --- → Future

Comment 6

16 years ago
Confirmed with: 
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210

Comment 7

16 years ago
mass reassign to default owner
Assignee: karnaze → table
Component: Printing → Layout: Tables
QA Contact: sujay → madhur
Target Milestone: Future → ---

Updated

16 years ago
Target Milestone: --- → Future

Comment 8

16 years ago
print bugs
Assignee: table → printing
Component: Layout: Tables → Printing
QA Contact: madhur → sujay
Target Milestone: Future → ---
(Reporter)

Comment 9

14 years ago
Created attachment 156141 [details]
Printoutput when printing to PDF
(Reporter)

Comment 10

14 years ago
In Firefox 0.9.3 under WinXP, no scrollbars are printed and two pages are generated.
But the content still flows down the first page, without going to the second
page at the end of the first page.

Comment 11

13 years ago
*** Bug 279985 has been marked as a duplicate of this bug. ***

Comment 12

13 years ago
*** Bug 302754 has been marked as a duplicate of this bug. ***
Assignee: printing → nobody
QA Contact: sujay → printing

Comment 13

4 years ago
I cannot reproduce with recent Nightly under Linux.
Can anyone reproduce?
You need to log in before you can comment on or make changes to this bug.