361256 - CSS printing page break page-break-before or page-break-after does not work inside WebSphere Portal

Status: RESOLVED DUPLICATE of bug 136714

(Core :: Printing: Output, defect)

Description

[Gasse Jeremy]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

When I used the Css page printing break page-break-before or page-break-after in a WebSphere Portal 5.1.x, the display is a bit strange (some elements are not well aligned) and the break are actually not used when printing (ie: the break is not done and my 2 pages are printed as one)
I tested these Css tags outside of Portal and they were working fine. I tried also with IE 6.x and it worked also fine, both inside and outside of Portal

Reproducible: Always

Steps to Reproduce:
1.Get a WebSphere Portal 5.1.x running
2.Modify one of the JPS to include a page-break-before anywhere
3.Click on "Print View" and see that they are actually not working

Actual Results:  
The print break is not taken into account. For example if I wanted a break after a <div> before starting another <div> then the break is not done and when I print the page, the content of the second <div> is printed on the first page

Expected Results:  
There should have a page break after the first <div> (in the previous example)

I tried with a "clean" new installation of Firefox on 2 different computers with two differents version of Portal (which are properly configured)

Comment 1

[Paul van Schayck]

A reduced testcase will be much appriciated. You can attach the test case using the Create New Attachment link.

Comment 2

[Gasse Jeremy]

Attachment: Test Page for the Bug.

This is a simple test page.
Notice that the <div> elements containing the CSS tags page-break-after are INSIDE a <table> element.
It seems that in this case, the page-break are actually not processed by Firefox and are not working (try to make a Print Preview to check that there is not break done between these two <div>)

Comment 3

[Gasse Jeremy]

After some research from my side, I found that basically Portal has nothing to do with it.
It seems to be that Firefox is not interpreting the CSS page break correctly if those are written in a element which is itself included inside one of these elements:
- tables
- floated elements
- block elements

ie: if you use the css break simply like in a <div style="page-break-before: always">Blablabla</div> this is working properly
But if now this <div> is included inside a <table> for example it is not working:
<table>
  <div style="page-break-before: always">Blablablab</div>
</table>

Then in this case the page break would not actually occur and be displayed in the Print Preview or used in the actual printing process.

Hope this helps!

Comment 4

[Paul van Schayck]

DUPLICATE of bug 136714.

If you look at the spec (http://www.w3.org/TR/REC-CSS2/page.html#page-break-props), this style property is only for block level elements (like div). A table row is not a block level element, but a table-row element.

Also see bug 136714 comment 11 for other implentation issues.

Comment 5

[Steve England [:stevee]]

*** This bug has been marked as a duplicate of 136714 ***

Comment 6

[Gasse Jeremy]

Ok, thanks Paul van Schayck for the link to the other bug, that was interesting.
I tried to look in the database before I posted this one to see if it was a known bug but I guess I missed this one.

I went through the comments. So basically this issue has been brought up in 2004 and the position of the Firefox team until now is that Mozilla comply with the CSS Spec right?

As a developer I really understand that to manage the complex cases like what was posted in the comment 11 of the bug 136714 is basically impossible without turning insane. And moreover the page printing will definitly turns ugly...

So it is still not planned in the future for Firefox to be able to handle the simple cases of 1 table with a collection of rows and with few break inside?

Thanks for the answers anyway.