> because while it will trigger a column rebalance Column rebalancing on large tables is not really cheap so avoiding it seems reasonable to me. If we don't need that, the better.
Oh I did not see from your first mail that you considered heights. >One question is what "certain" are. I think you can use the cellmap methods to estimate the effect of a cell insertion/removal. Thats the place where rowspans are handled. 1. If we rebuild the cellmap you have to reflow all rows. 2. If the cheaper methods are used one can retrieve the affected rows from them. Further there are an quite subtle code paths that set the cell heights. CalculateRowHeights (see the comment at http://lxr.mozilla.org/seamonkey/source/layout/tables/nsTableRowGroupFrame.cpp#547) This is basically the height equivalent to BasicTableLayoutStrategy. And my all time favorite DidResizeRows (just above it). If there are height constrains on the table, rowgroup, rows or cells things become complicated and you are probably better off by reflowing all rows. Its also pretty nasty if the special height reflow is invoked. Bernd _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
