I run a fantasy sports site. On one page, there is information about each player arranged as tabular data. One column is "Basketball Statistics." This, IN AND OF ITSELF, is tabular data. Therefore, a nested table would be at least semantically correct.
ah right... well <table> is a valid child element of <td>, and in the situation you described it does seem to make sense to structure ur html like that
You can definitely nest tables.
But I would avoid it if possible, it can get VERY messy!
Why not have "independent" tables for each of your stats sections?
You can definitely nest tables.
But I would avoid it if possible, it can get VERY messy!
Why not have "independent" tables for each of your stats sections?
Probably because it would get hard to follow. Each player had a stat table, and there are, I think, 8 players in this ONE table.
Table is not a four-letter word. I can nest tables inside tables inside tables with no difficulty whatsoever. These days, of course, I only use css for layout (we must be politically correct!)
Table is not a four-letter word. I can nest tables inside tables inside tables with no difficulty whatsoever. These days, of course, I only use css for layout (we must be politically correct!)
Thing is, it had absolutely zip to do with layout. It had to do with a subset of information for each player.
Bookmarks