Open
Bug 1250348
Opened 9 years ago
Updated 2 years 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)
Core
Printing: Output
Tracking
()
NEW
| 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.
|
Reporter | |
Updated•9 years ago
|
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)
|
|
Reporter | |
Comment 1•9 years ago
|
||
(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.)
|
||
Comment 2•6 years ago
|
||
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.
|
||
Updated•5 years ago
|
Whiteboard: [layout:print-triage:p1]
|
||
Comment 3•5 years ago
|
||
- 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...
|
|
||
Comment 4•5 years ago
|
||
I'm guessing it's something like this...
|
|
||
Comment 5•5 years ago
|
||
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...
|
|
||
Comment 6•5 years ago
|
||
A test to show that Chrome doesn't fragment either, it just slices the rendering (mid-way through an "A").
|
||
Updated•5 years ago
|
Whiteboard: [layout:print-triage:p1] → [frag2020]
|
|
||
Updated•5 years ago
|
Whiteboard: [frag2020] → [layout:print-triage:p1][frag2020]
|
|
||
Comment 7•4 years ago
|
||
Bug 1640197 / bug 1665214 should fix this when we enable it.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•