Hi,
We have looked into the issue. The root of the problem is the following CSS rule:
Code: C#
.page-break:last-child {
page-break-after: avoid !important;
}
This rule is applied to the first "page-break" DIV (which contains the big table) and it has the effect of sticking this DIV together with the element immediately after it. This cause the whole DIV to be treated as an unbreakable section, in the best effort not to break this DIV, the converter moves the whole section from the first page to the second page since the second page has more available space than the first page. To avoid this problem you will need to remove the above rules.
The fact that the converter treats two adjacent elements as unbreakable if the first element has "page-break-after:avoid" does seem to be excessive and causes issues like yours that's hard to troubleshoot. We will change our next build to only create a small unbreakable area between the first and second element. This will work better for your situation but will still have its limitation ---- for example, if there is a large space between the first and the second element (such as introduced by the first element's margin-bottom), then even if you have page-break-after:avoid on the first element, the small page break avoid section will not be large enough to cover this space between the two elements and page break can still occur.
Thanks!