Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

incorrect movement of the table on the next page, if it is in span #371

igor04 opened this Issue Jul 8, 2012 · 5 comments


None yet
3 participants

igor04 commented Jul 8, 2012

If table is used without span all is fine, but if we set table into span transfer is wrong. For example: https://www.dropbox.com/s/agfq3d8vdy5ja8v/pdf.jpg

Maybe this is not bug, but would be nice if this situatian will work correct.


bradediger commented Jul 8, 2012

From your example, I'm not sure what the problem is that you're trying to show. Can you explain further?

There is one slightly non-intuitive behavior of tables in spans that is by design and that we rely on. That is that when tables wrap to a new page, they start at the top of their bounding box (or span) rather than their start position on the first page. We use this, for example, in billing systems to have a longer header on the first page, followed by continuation pages with a shorter header and longer table.

If that's not the problem you're seeing, post more details and someone may be able to help.

igor04 commented Jul 8, 2012

On picrure you can see how "table in span" covers footer of the page with orange line. In normal situation last row must be on a new page, because there isn't enough space for row, but in our case it stays on the same page.


bradediger commented Jul 8, 2012

A span is basically a bounding box without a height, so it is always "stretchy" (will never limit height on its own). If you need to reserve some space for the footer, you should use a bounding box with a height.

igor04 commented Jul 8, 2012

Thanks! But i thought that margin in options of document would reserve this space, or was i mistaken? If i am mistaken, what should i do for getting indents on all pages and span doesn't cover it? Also, if text in span works( not cover), why does the table in span go on margins and cover them?


practicingruby commented Mar 17, 2014

We've made some improvements to spans, but I'm not sure if they resolve this issue or not. If not, please provide a code sample for me to run which illustrates the problem, and I'll re-open.

@practicingruby practicingruby removed the stale label Mar 17, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment