rporrata
Tables are generally for structured content. They work and are perfect - Excel for example. Hundreds of cells on a page? Rendering / performance would be a nightmare.
CSS grids for layout - perfect and may cause some pain. Once you get it right the performance is there.
With css/tags there can be abuse and we must think of how we plan to present our content to the user who ultimately judges our work.
They do not care about the how it was implemented, they just want it now and that it works consistently.
We need to ensure we keep our sanity the balance is in between the two.
On another note, the use of colgroups should be mentioned with the above. It does help with rendering performance. http://www.w3.org/TR/html5/single-page.html#the-colgroup-ele...
- Enjoy!
Part of the madness was due to tools that auto generated attributes and browser implementations when repainting/reflow occurred.
If the time, and potential knowledge was there, to better organize the structure vs. the layout thing may have been different. We would probably still be wrestling with browser issues.
I have worked in places where corporate sites had tables were littered with font tags for each cell, littered with a half dozen iframes(!?!)
The use for tables in layout was easy, but the long term debt was never paid.
Granted this is less of a case now; wading through this was not fun.