W3C home > Mailing lists > Public > public-html@w3.org > March 2011

Re: Working Group Decision on ISSUE-130: table-layout

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Fri, 11 Mar 2011 17:16:39 -0500
Message-ID: <AANLkTiknaDxm4hZJr0huBpkKeMuZGATwqNV5jbKjnq8S@mail.gmail.com>
To: Sam Ruby <rubys@intertwingly.net>
Cc: HTML WG <public-html@w3.org>
On Thu, Mar 10, 2011 at 12:36 PM, Sam Ruby <rubys@intertwingly.net> wrote:
>  * Compared to CSS, tables take more bandwidth, they aren't as
>   cacheable, they require you to cut images, they result in pages that
>   aren't as maintainable, and aren't rendered incrementally in many
>   browsers.

Nitpick: all major browsers render tables incrementally, as far as I
know.  They just have to re-render them in some cases after the table
has fully loaded, causing the page to jump, because the table sizing
algorithm depends on the full contents of the table.
Received on Friday, 11 March 2011 22:17:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:26 GMT