3 ms·
At the cost of poor performance on the client [1], so you're just pushing any time saved in development onto your user. The only way around the poor performanc
by whostolemyhat 10y ago
At the cost of poor performance on the client [1], so you're just pushing any time saved in development onto your user.
The only way around the poor performance of table layouts is to use table-layout: fixed, which then means you lose all responsive layout so you'd need to create a new version for every screen size you wanted to support (and implicitly, not be able to support every size of mobile screen since percentages don't play well with fixed layout. In this case, you haven't saved any time and in fact have created more work for yourself along with a worse version of your site since fewer people will be able to view it properly.
[1] http://www.stubbornella.org/content/2009/03/27/reflows-repaints-css-performance-making-your-javascript-slow/#tables http://www.stubbornella.org/content/2009/03/27/reflows-repai...