Feature request: Support cell spanning (rowspan/colspan) / merged cells

[ideaviewes]

Hi! Thanks for this project. Do you have any plans to support cell spanning (rowspan/colspan), i.e., merged cells in the table body?

[xelon-ua]

Thanks for the request!
At the moment, row spanning rowspan / merged rows isn’t something we can support with the current architecture. The table body is built around lazy/virtualized row loading, so rows aren’t all present/layouted at the same time, which makes reliable row-merging impractical without a major redesign.
Column spanning colspan / merged columns is potentially more feasible, but it’s not in the near-term roadmap. Even there, we’d need to solve a few non-trivial issues first:
Column reordering: columns can change order, so span definitions must remain stable and predictable.
Grouping/sorting tools: we’d need to define how grouping/sorting behaves when columns are merged which header “owns” interactions, what happens to merged children, etc..
If you can share a concrete use case headers vs body, static vs dynamic spans, interaction requirements, it’ll help evaluate a practical design and prioritize it. It would also be very helpful if you could share how you envision describing spans in the object model/API e.g., per-cell rowSpan/colSpan, a separate “merge ranges” descriptor, or a higher-level grouped column definition, especially considering column reordering and grouping/sorting behavior. Contributions/design proposals are welcome.