Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always layout a table twice so that BreakPositions are inserted appropriately #384

Merged
merged 1 commit into from
Aug 10, 2017

Commits on Aug 10, 2017

  1. Always layout a table twice so that BreakPositions are inserted appro…

    …priately
    
    - Layout of a table has been done in two phases. The first phase invokes initial layout to measure column widths, in which no BreakPosition for the table is inserted. The second phase does re-layout of the table, inserting BreakPositions for the table, which are used later for fragmentation of the table. If it turned out after the initial layout that the table does not overflow the current column, the re-layout in the second phase was omitted.
    - However, there are some cases where fragmenting the table is necessary even if the table itself does not overflow. For example, if a figure element wrapping the table has some block-end padding and the border edge of the figure overflows the column, the figure element should be fragmented. However, since it is not allowed to fragment the figure element between the padding and the table element, the fragmentation should occur inside the table. In such a case, it is necessary that BreakPositions are inserted inside the table.
    - In this commit, the omission of the second phase has been removed. It means that a table is always laid out twice so that appropriate BreakPositions are always inserted.
    kwkbtr committed Aug 10, 2017
    Configuration menu
    Copy the full SHA
    61bb2f2 View commit details
    Browse the repository at this point in the history