Status

()

Core
Printing: Output
RESOLVED EXPIRED
15 years ago
12 years ago

People

(Reporter: Andrew Thomas, Unassigned)

Tracking

1.4 Branch
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425

This sort of page can either completely lock up Mozilla, or results in MANY
blank pages (both 1.3 & 1.4 show the same problem). In this specific case it
creates 344 pages (!!) of which 342-344 are the actual content, the rest are all
blanks! This can be seen by looking at it in Print Preview.

See also: http://www.nytimes.com/aponline/automobiles/AP-Mexico-Last-Bug.html

In Print Preview it looks fine but a blank page actually appears 1st - this
seems to be INDEPENDENT of the printer driver - I have access to multiple
network printers - Postscript and PCL - all exhibit the same property.

Aside: I do not usually use IE(6) but IE copes with these pages fine. IE does
not cope with "Shink to fit" pages however.



Reproducible: Always

Steps to Reproduce:
1.
2.
3.



Expected Results:  
3 physical pages should print - 1-3
This has nothing to do with Bugzilla.  Moving to Browser.

Next time please read the form you're filling out before you submit it.  At the
top of the form was a big red stop sign with a box of text next to it (in a
large font) stating you were in the wrong place if you were reporting a bug
about Mozilla, and suggesting where the correct place was.
Assignee: gerv → printing
Component: Reporting/Charting → Printing
Product: Bugzilla → Browser
QA Contact: mattyt-bugzilla → sujay
Version: unspecified → 1.4 Branch

Updated

15 years ago
Summary: Incrrect "paging" → Incorrect "paging"

Comment 2

14 years ago
does it still happen with a current mozilla version ?
cant test cause it requires login ...
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.