869440 - inline-tables are cropped at page-boundary

Status: NEW

(Core :: Printing: Output, defect)

Description

[andre.silva]

Attachment: Reproduction of Print Problem

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31

Steps to reproduce:

Write a html table, that occupy two pages.


Actual results:

If CSS is applied, print preview only displays the first page.


Expected results:

 Firefox should display all pages.

Comment 1

[Loic]

Maybe a dupe.

Comment 2

[Ralph Daub [:rdaub]]

Possibly related to bug 849408.

andre.silva, can  you verify that it's the same issue that you're encountering?

Thanks!! =)

Comment 3

[Loic]

There is bug 863912 too but overflow:hidden is involved in this case, and there is no such an element in the current testcase.

Comment 4

[Loic]

Print output is affected too.

Comment 5

[Daniel Holbert [:dholbert]]

Attachment: reduced testcase 1: inline table

Comment 6

[Daniel Holbert [:dholbert]]

Yeah, this isn't related to bug bug 849408.

The issue here is that we don't seem to paginate inline-flavored <table> elements.

We don't seem to paginate inline-block for that matter, either, though -- I suspect that might be intentional, since having a single line span multiple pages is a bit crazy.

Comment 7

[Daniel Holbert [:dholbert]]

Attachment: reduced testcase 2: inline-block [just to demonstrate; this is also tracked in bug 534182]

Comment 8

[Daniel Holbert [:dholbert]]

Looks like bug 534182 tracks this for inline-block.

Comment 9

[Glenn]

Still present.  
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0

Comment 10

[Achim Mildenberger]

Problem still exists.

Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
Windows 32 bit also.

A fix would be very nice.

Comment 11

[andre.silva]

Achim, Gleen, if that problem matters to you, please vote.

Comment 12

[Glenn]

Implementation of Print CSS seemed to solve this problem for me.  I had inquired about my situation here and also got some excellently useful feedback:  https://support.mozilla.org/en-US/questions/967636?esab=a&s=Print+CSS&r=3&as=s

So at this point, while I believed that what I was witnessing was a part of this bug, (the bug description seemed to match my observed behavior) I am neither technically savvy enough nor knowledgeable enough about Mozilla to know if what I was witnessing was really related to this bug or not.  I hope others will comment to clarify one way or the other.  

In the mean time, I don't know if I should vote for this bug since I don't know if, in fact, what I was experiencing was related to this bug as I thought it was originally.

Comment 13

[Mats Palmgren (inactive)]

Attachment: testcase #3