footer overflows to next page or writes multiple times

rashmim00

How to troubleshoot when the footer is overflowing to next page and in one document its printing all 32 footers as background for one page. There are 32 pages in the document and its printing 32 footers right after one another.

By overflow, I mean it shows as footer on Page 1 but as a header for all other pages.
This is on 4.4.0 version.

Thanks,
Rashmi

admin

Please try to share a minimal playground demo that I can review.
https://playground.jsreport.net/

The problem can be a CSS issue, for example.

rashmim00

The css and these files are in place for last 5-7 years.
We have started seeing this issue since yesterday.

https://playground.jsreport.net/w/anon/bcd_qJM3 is a short document but is not replicating the issue.
It has my css files (HeaderFooter.css and BidPck60_Provisions.css)

badFooter.png is under assets to show the outcome where its printing all page footers one after another as background

Version 4.9.0 is good but version 4.10.0 is bad. Have you changed footer rendering in version 4.10.0.

admin

Thank you. We haven't changed that, but the latest jsreport includes the Chromium update.

Unfortunately, Chromium includes a breaking change in FlexNG for print layout calculation that we weren't aware of.
This hits the CSS we use in our demos for header/footer page.

The quick solution is to replace in the header footer css the following

.main {
    ...
    height: 100%;
}

with

.main {
    ...
    height: 100vh;
}

rashmim00

Thanks Jan. By when can we expect a newer release.
Maybe its affecting index part too - I am not too sure but I am seeing bad page numbers for some pages.

admin

The thing is that this will likely have no implicit solution. Everyone will need to adapt the CSS.
We can't stick with old Chromium due to vulnerabilities, and this behavior is fully controlled by Chromium.
jsreport has no control over it.

We will check the table of contents demos...

rashmim00

Thanks -- Noted. We are changing our css files.

admin

Could you share an example when the index gets broken in 4.10.0?
I don't see this problem in our samples.

rashmim00

False alarm. It end up being css problem - the footer was pushed to next page and showing previous page number. i think we are good now -- instead of height:100vh - i am using height:99.5vh