Re: table row order invariance vs. incremental layout efficiency (was Re: Specifying intrinsic width and table layout behavior)

> the constraints of Web-compatibility) requires doing two passes over the
> table, the first for non-column-spanning cells and the second for

Are you sure you mean two, rather than three; don't you need to an additional
pass to actually render the text into the finally chosen width?

Also, other than that it doesn't require author education to enable, does
this really gain you much compared with table-layout: fixed?  In fact, as
it is a change in algorithm, won't you still have the author education
problem that I suspect is the main reason that table-layout: fixed is
almost never used, as you will need to retain the current mode as default.

Received on Saturday, 16 September 2006 09:44:38 UTC