>>Just wondering, did you consider a plan where you tell TLF that the table >> is another container? Or maybe each cell is another container in >> row-major order? Would that eliminate some or all of these issues? > >Not sure I understand what you¹re asking. The way I¹m currently handling >cells, is by creating containers for each one. Tables are composed using >TextFlowTableBlocks for each visual section of the table. Right now it seems like you have to create a tree of TextFlows. IIUC, one TextFlow cannot represent a document with tables and cells in it. This also seems to create challenges around selection and also the wrapping of tables in paragraphs.
IIRC, TLF already supports composing a single TextFlow into multiple containers, but I believe it only knows how to fill up a container before moving to the next container. I was wondering if a table/cell element could have just caused a jump to the next container. -Alex
