Div with large margin-top isn't visible in print / print-preview

NEW
Unassigned

Status

()

11 years ago
7 years ago

People

(Reporter: dholbert, Unassigned)

Tracking

({testcase})

Trunk
x86
Linux
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments)

(Reporter)

Description

11 years ago
Created attachment 312407 [details]
testcase 1 (text not visible in print-preview)

Steps to reproduce:
 - Print-preview (or print) the attached testcase.

Expected behavior:
 - The string "This text should be visible in print preview" should be visible somewhere.

Actual behavior: 
  - 2 blank pages (with headers/footers) are printed.


If I stick some content (e.g. a single character, a <br/>, or a specified-height div) before the div, then it fixes the issue -- the string becomes visible at the very top of the second page.  (see upcoming reference case for an example)


This happens in FF2 as well, so this bug may already filed somewhere -- sorry if it's a dupe.
(Reporter)

Comment 1

11 years ago
Created attachment 312409 [details]
reference case 1 (text visible at top of 2nd page)
(Reporter)

Updated

10 years ago
Component: Print Preview → Printing
(Reporter)

Comment 2

10 years ago
Created attachment 322657 [details]
testcase 2 (multiple lines of text)

This testcase shows that it's actually just the *first line* of the div that's not visible.  The later lines seem to be snipped into a separate container which is pushed to the second page.

Viewing this testcase in FF3rc1, I get 
 First page: blank
 Second page: starts with "should... here's some more text, just to make [etc.]"
   (i.e. first line of the paragraph is cut off.)
(Reporter)

Comment 3

10 years ago
Created attachment 322658 [details]
reference 2

This version just adds a 1px-high div at the beginning, which pushes the "margin-top" div in its entirety to the second page and makes it completely visible there.
(Reporter)

Updated

7 years ago
Duplicate of this bug: 722968
You need to log in before you can comment on or make changes to this bug.