User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a; MultiZilla v1.1.32 final) Gecko/20021212 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a; MultiZilla v1.1.32 final) Gecko/20021212 The print preview doesnt't allow to flip through the pages of the included testcase. Reproducible: Always Steps to Reproduce: 1. unzip the testcase 2. load dvdx-videoserver.htm 3. go to print preview Actual Results: The page count shows 1 of 1 pages. The page is cut at the end. The printout has more pages. Expected Results: Show at least 2 pages

The printout has also problems (bug 192132). Depending on the print setting (frames separately or as layed out on screen) 5 pages or 1 page are printed.

I also see this with a current build (plain Mozilla) on Win2k. This might be a duplicate, but the possible ones I found were a bit different (e.g. this page has no position:absolute div). -> NEW so somebody finds the original report (or just fixes the bug :-) )

I have the same problem with all pages in Mozilla 1.4a - no matter how large the page, I only get one page printed or shown in print preview. I am using W2K.

I am using Win XP and version 1.3 final and I see only one page in print preview. Also only one page prints where there should have been two.

Changing the severity to major, since it ist a major function not working properly

This apparently isn't a widespread problem and I have no difficulties printing any of the handful of popular sites I tested on Windows and Linux.

It seems this problem also happens when you declare overflow:auto,overflow:hidden and overflow:scroll on body of html. They react all three slightly different. I have made some testpages: http://home.hccnet.nl/m.wargers/test/mozilla/print/ This has nothing to do with the testcase though. I think it has something to do with it that it has frames. I see it happening on all kind of framed pages.

I'm not sure if this has the same cause, but the result is the same. I only see one page of the following URL. http://support.microsoft.com/?kbid=257333

-- October 29 2003 -- By Gary Ridley, WWW Specialist at Math Faculty of the University of Waterloo, Waterloo, Ontario I just came across this bug report when searching for a solution to print problems we are having, using any version of Mozilla/Netscape7 on either Mac os/x or Windows. Our web pages (www.math.uwaterloo.ca/index.shtml) make a lot of use of <div> tags and CSS positioning, on all such math pages Print Preview shows only 1 page and when printing trucates that web page to 1 page discarding the extra. Removing the <div> tags allows the page to print correctly. My test page for this can be found at: http://www.math.uwaterloo.ca/mathcontent/ProtoPages/PrintVersion/ PrintTester2.shtml My email is gwridley@math.uwaterloo.ca. Is there a solution to this bug?

Printing/previewing only one page: pages with (i)frames see bug 247166, pages with Overflow:auto see bug 248440.

This bug was reported many times : 267709 267745 260024

*** Bug 192132 has been marked as a duplicate of this bug. ***

Still valid in Firefox Beta 1

probably related: https://bugzilla.mozilla.org/show_bug.cgi?id=309486

encountered this in FF3 beta 5 while testing to see if FF3 would have fixed the problem.

Bug (1 page only printing) present in FF3.5.2 on WinXP, see: http://www.randomhouse.com/modernlibrary/100rivallist.html. Same problem at some other websites.

Yes, the exact same behaviour as #17 happens on http://www.duden.de/deutsche_sprache/index.php?nid=22 (FF 3.5.3)

The sites in comments 17 & comment 18 both have stylesheets that specify "overflow: hidden" on an element that contains their main content, which means the main content gets clipped when printed, due to bug 129941. In the first site, the element is "#main" and the stylesheet is http://www.randomhouse.com/modernlibrary/css/style.css In the second site, the element is #content, and the stylesheet is http://www.duden.de/global/css/global.css Duping this to bug 129941, because that's generally responsible for most of this type of of issues, and it's definitely responsible for the most recent activity on this bug.

With react, this issue has become prominent than before. Do you plan to act on it? It has been little over 16 years since this bug was open?

With react, this issue has become prominent than before. Do you plan to act on it? It has been little over 16 years since this bug was open?

Duping correctly based on the subject of the original report.