- From: Aleksandar Totic via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Nov 2019 17:49:26 +0000
- To: public-css-archive@w3.org
> I guess I think of computing the number of columns in the table as part of the rendering tree construction rather than part of layout, so in my mind this doesn't make layout multi-pass. :-) I just remembered the `table-layout: fixed`single-pass promise from long time ago, and wanted to live up to it in Chrome's new implementation. Unfortunatelly, there is no way for us to compute number of columns during rendering tree construction, those pesky rowspan/colspan attributes make it unfeasible. `table-layout: fixed` is still faster, because we do not have to compute min/max sizes of all cells, we just have to traverse them. Clarification accomplished, closing this issue. -- GitHub Notification of comment by atotic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4512#issuecomment-555130360 using your GitHub account
Received on Monday, 18 November 2019 17:49:27 UTC