Closed Bug 281712 Opened 20 years ago Closed 20 years ago

vertical position of absolutely positioned blocks broken on second & subsequent printed pages

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 179135

People

(Reporter: nottheoilrig, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.5 (KHTML, like Gecko) Safari/125.12 Build Identifier: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7.5) Gecko/20050207 Firefox/1.0 (Debian package 1.0+dfsg.1-5) The only way I could figure getting both left & right justified text on the same line - for the dates on my resume - was setting "position: absolute" & "right: <right margin>" - I wish there were a nicer way, but at least this displays correctly on screen in Firefox & on the first page printed by Firefox. The dates on second & subsequent pages printed by Firefox all end up superimposed at the top of the first page. I reproduced this problem using Firefox on both Linux & OS X. http://cgi.sfu.ca/~jdbates/tmp/resume/200502080/resume.xhtml The most relevant bug I found was 265355 - but it deals with blocks' heights & percentages of the canvas. Since the dates are correctly vertically positioned on the first page, I guess vertical position on printed pages is partly correct - & since all the dates are correctly vertically positioned on screen, I guess the problem is associated with pagination? Unfortunately I'm not sure where in the source to investigate - Thanks! Jack Reproducible: Always Steps to Reproduce: 1. open http://cgi.sfu.ca/~jdbates/tmp/resume/200502080/resume.xhtml in Firefox 2. print, or print preview Actual Results: The dates on second & subsequent pages all end up superimposed at the top of the first page. Expected Results: The dates should have ended up at the same positions as they do on screen.
*** This bug has been marked as a duplicate of 179135 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.