166737 - Background images on sized, positioned divs scaled to a tiny image when Printed

Status: RESOLVED DUPLICATE of bug 161179

(Core :: Printing: Output, defect)

Description

[Adam van den Hoven]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721

I have a web design where I have a masthead that is a series of div tags with
images inside. When I go to print, I hide the images and add a background image
to the div. Basically I'm changing from color to greyscale so it prints better. 

In print preview, the background image looks correct. It is the same view (more
or less) as you'd see in IE or another browser. If you go to print, the images
are rendered at a fraction of the print preview size (best guess: 1/5 of the
actual size. The printed effect happens even when you bypass the print preview.

Even if my HTML/CSS is wrong, the Print Preview and the actual printed output
should NEVER be so fundamentally different.

Unfortunately, the code that I see this with is still behind a password (we're
in QA of an online banking app) so I can't give you a meaningful URL. Instead
I've compiled the CSS into the HTML and retrieved all the images. I will upload
these files as a zip so you can see the behaviour


Reproducible: Always

Steps to Reproduce:
1.Open OddPrinting.html
2.Goto Print Preview
3.Print the page


Actual Results:  
The images in the "masthead" area (CoastCapital and pcdirect logos) appear their
full, natural size in print preview but a fraction of the actual size on the
printed page

Expected Results:  
Printed the page exactly as it appeared in print preview

Comment 1

[Adam van den Hoven]

Attachment: Files to reproduce the error

This zip file contains all the files needed to reproduce the defect. Simply
open the OddPrinting.html file

Comment 2

[rods (gone)]

-

Comment 3

[Ken Warkentyne]

The behaviour is not quite as Adam described it. What happens is:

The first time you print or preview the page, you get the two images in the
masthead squished.

The second time you print or preview the page, the images are printed/shown at
the correct size.

This is in production now and we are getting complaints from some people still
using Netscape.

Here is the production URL:
https://www5.memberdirect.net/direct/login.jsp?inst=/bc/coast

Comment 4

[Pat]

This also happens on Linux with 1.2.1

Comment 5

[Ken Warkentyne]

Attachment: minimal test case

This file contains a minimal test case for this issue. There is a single image
and some CSS that hides the image on the screen but displays it for printing.
To reproduce the error, load the page and then do a "print preview." The image
will be squished to a tiny size. If you do it a second time, the image is the
correct size. To squish it again, go to your advanced preferences and clear
your memory cache (no need to clear the disk cache).

Comment 6

[Chris Haff]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210

I still get this.  In genaral this, or a similar problem also occurs when
printing images across page boundaries.  A squished version of the image prints
in the remaining area on the page and then on the following page another
squished image fills the rest of the space that the image would have occupied if
the image had just printed as one continuous image (and there had been no line
break).

Shouldn't the status be CONFIRMED?

Comment 7

[Wolfgang Rosenauer [:wolfiR]]

confirming with 1.4a on Linux. -> set OS to 'all'

But I see this with another example where no background images are used but
'normal' images. If the image at the bottom of the (printed) is too big to fit
on the page it will be printed vertical scaled. On the next page it will be 
printed vertical scaled to the remaining 'unscaled' size which would be needed
for the correct image. So you have the same image two times (1x bottom of the
page; 1x top of the next page) in a unusable scaled version, if the whole unscaled
image is too big to fit the page.

Comment 8

[rcummins]

I can't duplicate this problem with any of the testcases using build 2003071008
under Windows 98 - anyone try this lately with a recent build?

Comment 9

[Ken Warkentyne]

Image in minimal test case displays correctly using Mozilla 1.4 (Linux
20030611). Looks like this bug has been fixed. Recommend closing.

Comment 10

[Murray Bryant]

I can reproduce the error on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.5b) Gecko/20030827.

Using the files provided in the zip

I have also been getting the same error on pages of my own creation.

Comment 11

[Gervase Markham [:gerv]]

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/

Comment 12

[Daniel Wang]

Attachment: testcase

testcase based on the first attachment

Comment 13

[Daniel Wang]

duping to bug 161179 because the testcases, though not exactly the same, are
similar. probably same bug

*** This bug has been marked as a duplicate of 161179 ***

*** This bug has been marked as a duplicate of 161179 ***