Skip to content

fix(html): read table row groups in rendered order - #4829

Draft
Afloat16 wants to merge 1 commit into
Unstructured-IO:mainfrom
Afloat16:Afloat16/html-table-rendered-order-20261121
Draft

Afloat16 wants to merge 1 commit into
Unstructured-IO:mainfrom
Afloat16:Afloat16/html-table-rendered-order-20261121

Conversation

@Afloat16

@Afloat16 Afloat16 commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

The HTML parser and compact table reader currently follow source order for row groups. A tfoot written before tbody, as older valid table markup allows, is therefore extracted before the data; a late thead is extracted after it.

Follow default HTML table display ordering: the first header precedes other rows and the first footer follows them. Additional header/footer groups keep ordinary row-group order. Normalize nested tables independently and capture source rows/header flags/group identities after ordering, keeping chunking metadata aligned. No CSS cascade interpretation is introduced.

Validation

Five regressions fail on main, with the ordinary-order control passing. The new tests, common table suite, HTML parser suite and chunking base suite pass: 603 passed, 55 existing skips. Whole-repository Ruff 0.15.10 lint and format checks pass. Full repository tests remain pending, so this is a draft.

Reference: https://www.w3.org/TR/CSS2/tables.html#table-display

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant