|
Use tables ONLY for tabular data, meaning one row equals one record set.
If you're using multiple record sets per row/s it becomes real nightmare in maintaining and generation of table's rows and cells in your application, you will have to enable processes to count how many rows and cells there are, put some obscure conditions and the whole thing comes out not being elegantly implemented. It is simply not logical and not the best solution to use tables in such way. Also table is not rendered in a browser until it is fully loaded.
For the rows of thumbs/titles/etc which are basically separate sets of records its best to stack them in to rows with DIV containers and having content positioned appropriately within them through the use of css classes
|