Open Bug 1250348 Opened 6 years ago Updated 1 year ago

Tall <iframe> elements are truncated at page boundaries (instead of being split across pages, like tall images are)

Categories

(Core :: Printing: Output, defect, P3)

defect

Tracking

()

Tracking Status
firefox47 --- affected

People

(Reporter: dholbert, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: dataloss, testcase, Whiteboard: [layout:print-triage:p1][frag2020])

Attachments

(2 files)

STR:
 1. Load attached testcase; note that you can scroll down and see the "DO YOU SEE ME" text.
 2. Print or print-preview the page.

ACTUAL RESULTS:
Printed output is truncated to 1 page. "DO YOU SEE ME" text isn't visible.

EXPECTED RESULTS:
Full output should have been printed.

This is because we can't split tall <iframe> elements across pages, I believe. We do this for img elements, so we could in theory do it for <iframe> as well.
Blocks: 521204
Summary: Tall <iframe> elements are truncated at page boundaries (instead of being split like tall images) → Tall <iframe> elements are truncated at page boundaries (instead of being split across pages, like tall images are)
(This issue was originally reported on bug 1106301; I spun it off as this new bug, to start fresh without a backlog of diagnosis back-and-forth.)

Just ran into this bug. In desperation, switched from <iframe> to <object>, to no avail. Not sure if tall <object> elements should be added to this bug, or a different bug created for tall <object> elements. Would be nice if there were some action on this bug.

Whiteboard: [layout:print-triage:p1]
Blocks: 1601429
  1. Load attached testcase; note that you can scroll down and see the "DO YOU SEE ME" text.

It seems you forgot to attach the testcase...

Attached file Testcase #1

I'm guessing it's something like this...

Somewhat related to bug 534182 although in this case with the additional complication that it'd be extremely hard to support real fragmentation in this case...

Blocks: 534182
Keywords: dataloss, testcase
OS: Unspecified → All
Priority: -- → P3
Hardware: Unspecified → All
Attached file Testcase #2

A test to show that Chrome doesn't fragment either, it just slices the rendering (mid-way through an "A").

Whiteboard: [layout:print-triage:p1] → [frag2020]
Whiteboard: [frag2020] → [layout:print-triage:p1][frag2020]

Bug 1640197 / bug 1665214 should fix this when we enable it.

You need to log in before you can comment on or make changes to this bug.