Forum Moderators: open
I am wondering if (by the highest possible standards only) if forum threads should or should not be considered tabular data?
- John
For example, the data you’re currently reading describes the intersect of the set “all conversation” and “fourth time slice”. The data to the left of this is the intersect of “user information” and “fourth time slice”.
Yes, it’s tenuous :)
[edited by: Robin_reala at 12:59 pm (utc) on Nov. 11, 2006]
But I don't think you can justify putting the content of the thread (ie, the posts) into a table unless you can bear one row per post.
Semantically invalid IMHO:
<table>
<tr><td rowspan="2">ingolemo</td><td>Post #1, posted on 1st jan 1970<td></tr>
<tr><td>Well, my opinion is...</td></tr>
...
</table> Semantically valid, but a little inelegant:
<table>
<thead>
<tr>
<th>Post number</th><th>User</th><th>Date</th>
<th>Content</th>
</tr>
</thead>
<tbody>
<tr>
<td>1</td><td>ingolemo</td><td>1st jan 1970</td>
<td>Well, my opinion is...</td>
</tr>
...
</tbody>
</table>
1) Tables will continue to be supported by all browsers.
2) If you understand both tables and CSS and decide that tables provided a simpler, more elegant, more versatile solution then you should use tables.
There are a lot of people that think tables are amateurish, evil, etc. etc. Quite simply, disregard these views - there are a lot of idiots in this world and it's never a good idea to follow their advice.
As Ingolemo hinted, the best solution may be to use both.
Kaled.
ITEM COLOR COST
Dog Brown $1
Cat Black $1
The backend of a forum uses similar data sets to maintain order and present information, but the subjective view of the user is individual posts nested inside topics, nested inside forums.