No bottom cell border drawn, when table cell breaks across pages

[mpth]

Not sure if this is just my lack of CSS knowledge but I expected a bottom border for a table cell that breaks over to the next page, especially when the table header is repeated. The screenshot below shows that now orange border is drawn at the bottom of the page.

Hope the image gives enough context, happy to add a full sample if necessary.

[liZe]

Hi!

This is normal: when a box is split between pages, the bottom border is not drawn on the first page, and the top border is not drawn on the second page.

If you want to repeat the top/bottom borders on each page, you can set box-decoration-break: clone on your td.

[mpth]

Thanks! I knew there was a CSS property for that but couldn't remember it.

It looks like it doesn't work in combination with table { border-collapse: collapse } though ?

[liZe]

It looks like it doesn't work in combination with table { border-collapse: collapse } though ?

I have no idea whether this behavior is specified. Let me check that.

[mpth]

Thanks for checking 👍

[JamesHutchison]

Perhaps this is related - I'm seeing margin's not being applied when a div crosses the page boundary

Structure would be:

<div>
  ---- page breaks here
<div>

<div>
    <div style="border: 1px solid black; height: 0; width: 100%;", class="my-4" />
<div>

<div>

<div>

[liZe]

I’ve checked, and as far as I can tell, it’s unfortunately not defined. The feature seems to be simple, but it’s not, as it’s easy to find corner cases where the result is far from obvious.

So, we won’t implement this feature in WeasyPrint for now.

If you’re (or anyone else is) interested in getting this feature, the next step is probably to open an issue on the CSS working group drafts repository and ask if it could be possible to define how box-decoration-break influences tables with collapsed borders.

[liZe]

Perhaps this is related - I'm seeing margin's not being applied when a div crosses the page boundary

@JamesHutchison It’s not related. Could you please open a new issue, with a complete example that shows your problem?

[liZe]

Closing, as it’s not a bug in WeasyPrint, but an undefined behavior. If someone wants to improve the specification and open an issue on the CSS working group’s repositiory, feel free to add a comment so that we can follow!