fix: banded rows start on the first body row

The stripe began one row late: regionsAt counted the second body row as the
first band. Probed on a five-row fixture with a red band1Horz — LibreOffice
shades row 0 where the style paints no header region, and the row under the
header where it does.

The corpus cannot see this (no fixture uses the editor's own registry), so it
stayed at 739; checked by eye and by the unit test's inverted expectations. A
document with a table style assigned re-bands on its next open.
This commit is contained in:
Steffen Becker committed 2026-08-13 07:06:13 +00:00
1 parent b6a8db8584
commit 04d1fed5f0
4 files changed
+29 -24

No files matched your search

+3 -1
View File
@@ -31,7 +31,9 @@ We deliberately keep TipTap's `resizable: false` (so its own columnResizing plug
`lastColumn` < `firstColumn` < `lastRow` < `headerRow`), with `wholeTable` as the base.
`resolveTableCell(style, coords, look)` is the single source of truth for **all four**
consumers (apply, CSS, export bake, preview tiles): it layers the matching regions, counts
banding over *body* rows (a header row doesn't shift the stripes) and decides each border
banding over *body* rows — a header row doesn't shift the stripes, and the **first** body
row is the first stripe (probed: LibreOffice shades the row under the header, and row 0
where the style paints no header) — and decides each border
**per grid line** from both sides, so two facing cells never disagree once collapsed.
**Table Style Options** are Word's per-table `w:tblLook`: a `TableLook` (one flag per region)
stored space-separated in the table's `tableLook` attr, absent ⇒ `DEFAULT_TABLE_LOOK` (Word's