Skip to content

Explain verified workarounds for clipped long tables #157

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.

Sign up for GitHub

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

Open
krflol wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Explain verified workarounds for clipped long tables #157

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,34 @@ in CSS. Fullbleed does not search system fonts. Also check that the source text
is decoded as UTF-8. The [Chinese-font recipe](guides/chinese-pdf.md) provides a
verified bilingual invoice, font preparation, and missing-character diagnostics.

## Why are table rows or column text cut off? {#tables-cut-off}

In **2.5.34** and **2.6.0a14**, clipping an auto-height table or its container can
keep rows below the physical page instead of continuing them onto another page.
For long tables, remove fixed `height`/`max-height` constraints and clipping from
the table and its wrappers. Keep a `<thead>` for repeated column headings:

```css
.report-table {
table-layout: auto;
overflow: visible;
}
```

In **2.6.0a14**, percentage column widths can also push neighboring text past the
table edge when a label needs more than its assigned share. Remove percentage
`width` declarations from the affected `th`, `td`, and `<col>` elements so the
automatic layout can allocate space from the content. Remove widths from
`style` attributes too; a normal stylesheet rule does not override inline CSS.

The combined workaround was checked with an 80-row table on both versions:
every row appears once, headings repeat, and glyphs stay within the page and
table bounds. Review the final PDF with your actual fonts and data. Complete
text extraction alone does not prove the text is visible on the page.

Follow the fixes for [clipped-container pagination](https://github.com/fullbleed-engine/fullbleed-official/pull/127)
and [percentage column sizing](https://github.com/fullbleed-engine/fullbleed-official/pull/128).

## Does choosing a PDF profile prove conformance?

No. Profile selection configures output. Verify the final artifact and retain the validator reports. The [accessibility workflow](accessibility/overview.md) and [print-output reference](guides/print-output.md) describe the available checks and current limits.
Expand Down
3 changes: 2 additions & 1 deletion docs/guides/pandas-to-pdf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,7 +147,8 @@ signed axis if negative categories need visual comparison. For wider tables,
choose the useful columns and set their widths deliberately. Very long labels or
a row taller than a page need a different layout. Review every preview after
changing data, fonts, or CSS; the [CSS coverage](../css-coverage.md) page describes
the engine's supported layout surface.
the engine's supported layout surface. If rows or cell text are cut off, see
[table troubleshooting](../faq.md#tables-cut-off).

This workflow exports a DataFrame as a text table and styles it with document
CSS. It does not promise a pixel-identical reproduction of an arbitrary pandas
Expand Down
Loading