294817 - Position difference between screen rendering and printing

Status: VERIFIED INCOMPLETE

(Firefox :: General, defect)

Description

[aescallon]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

The HTML Rendering of an absolute positioning DIV to the screen and to the
printer   has location differences relative to the DIV's origin.

The differences are not the same for all the HTML Elements. In the case of Text,
 it renders to the screen 5px down in comparison with the printing, in the case
of radio buttons, the shift is down and right by 4 pixels.

This problem happends in Mozilla 1.7.8 as well.


In conclution a well formated html page will never print right.




Reproducible: Always

Steps to Reproduce:
1.Create a file with an absolute position DIV (add a border o backgroud to it to
se the real location)
2.ad text at position 0,0 in the div
3.print and compare.



Expected Results:  
Rendering shoud have the same positioning

Mozilla 1.7.8 has the same problem

Comment 1

[Kevin Brosnan]

WFM - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050519
Firefox/1.0+

Comment 2

[Marcus]

I am having on-screen rendering problems with nested "layers" using the <div> 
command.  The nested layers are absolute.  This is a problem with Nescape, 
Mozilla, and Firefox.  So, it appears to be a core programming error.  All 
other browsers (IE, Safari, Opera) all accurately render the nested <div> 
layers.  So, it appears to be a core programming error in the 
browser's "engine". I would definately switch browers if this one error was 
corrected, because, otherwise, Firefox is a superior browser.

Comment 3

[Samuel Sidler (old account; do not CC)]

Resolving as INCOMPLETE. Comment 1 implies it worked fine after Firefox 1 and there was no testcase attached. Comment 2 is completely different.

If you're able to reproduce this using Firefox 2.0.0.3 or later and are willing to attach a testcase, please reopen this bug.