Artifacts Printed When a Page Breaks Just After a GIF Image




Printing: Output
14 years ago
13 years ago


(Reporter: Jiri Moudry, Unassigned)


Windows 2000

Firefox Tracking Flags

(Not tracked)





14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316

When viewing a long page (57 printed pages), everything looks OK, like

(a GIF image)
Figure 9.

When printing, I see

(a GIF image)
27 of 57
-------------- ( a page break; yes, the page should break here)
(a GIF image compressed vertically about 4 times)
Figure 9.

Reproducible: Always
Steps to Reproduce:
1. View - if it changes, I have an original
2. Print it on a letter-sized page (HP Laserjet IIID)

Actual Results:  
When a page breaks between a GIF image and an immediately following text, the
GIF prints correctly, but the next page contains an image artifact before the text. 

Expected Results:  
No artifact should be printed. 

Sometimes an artifact prints at the bottom of the first page, followed by a good
GIF on the next page - see Figure 7 in the above document.
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.