Open Bug 1363575 Opened 7 years ago Updated 2 years ago

Print problem, The footer(css float) overlaps the body

Categories

(Core :: Layout: Floats, defect, P2)

All
Windows 10
defect

Tracking

()

Tracking Status
firefox55 --- affected

People

(Reporter: alice0775, Unassigned)

References

Details

(4 keywords)

Attachments

(4 files)

Attached file testcase
+++ This bug was initially created as a clone of Bug #1361787 +++

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170413192749

Print problem, The footer(css float) overlaps the body.
Edge and Chrome are no problem.

Reproducible: always


Steps to reproduce:
1. Open http://essentialseeing.com/phototrip/exclusive-namibia-namibrand-photo-workshop/  (this page hangs when print, see Bug 1361787)
2. print or print preview

Alternate Steps to reproduce:
1. Open attached testcase
2. print or print preview

Actual results:
Footer parts  overlaps the main body

Expected results;
Should not overlap
Attached image screenshot
Whiteboard: [parity-chrome] [parity-edge] → [DUPEME],[parity-Chrome][parity-Edge]
Assignee: nobody → fatseng
Priority: -- → P1
Assignee: fatseng → nobody
TY, it seems a reflow issue in printing layout. Could you take a look?
Flags: needinfo?(tlin)
Priority: P1 → P2
Component: Printing: Output → Layout: Floats
Flags: needinfo?(tlin)
Attached file float-print.html
I reduce the test case further. The frame tree dump is here. 
https://pastebin.mozilla.org/9070302

There's something fishy in the frame tree. We put the <div class="footer">'s placeholder frame (7f6124158f58) in the first page, but its out-of-the-flow float frame (7f6124158ea8) is on the second page.  

Also, the Block(body)(2)@7f6124159338 on the second page has 0 height. Perhaps that's why the float frame (7f6124158ea8) is at y=0.

I have no idea how to fix this the moment.
Re comment 3:

> Also, the Block(body)(2)@7f6124159338 on the second page has 0 height. Perhaps that's why the float frame (7f6124158ea8) is at y=0.

This statement makes no sense. Please ignore it.
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Whiteboard: [DUPEME],[parity-Chrome][parity-Edge] → [DUPEME],
Whiteboard: [DUPEME], → [DUPEME]
Keywords: dupeme
Whiteboard: [DUPEME]

This issue is reproducible on my machine win 7x64 using Firefox 103.0b8. Please see screenshot.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: