
Page break inside table with numeric :position option causes layout to go haywire
Reported by mbunkus | September 16th, 2009 @ 03:29 AM
If a table is rendered with a numeric :position argument and if a page break occurs within such a table then the following pages' layouts are broken. On the following pages the bounding box seems to stay shrunk down to the bounding box used for offsetting the original table, and therefore all following tables are only drawn at the very bottom of the page resulting in more and more pages being created.
Using ":position => :center" (default) and ":position => :left" both work fine.
I'll be attaching both an example Ruby file and the resulting PDF file.
This is with prawn-core and prawn-layout from Git on 2009-09-15.
Comments and changes to this ticket
-
mbunkus September 16th, 2009 @ 03:30 AM
Oops, the Ruby script still contains :position => :left from my tests. Please replace the :left with any number (0 will do) in order to reproduce the bug. I'll also upload a new version for your convenience :)
-
Sakchai Siripanyawuth January 10th, 2011 @ 03:58 PM
- Milestone order changed from 0 to 0
I am having the exact same issue.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป