> >>Consider the rough example: > >> > >><table> > >> <tr> > >> <th scope="row">Title:</th> > >> <td>President</td> > >> </tr> > >> <tr> > >> <th scope="row">Name:</th> > >> <td>Joe Smith</td> > >> </tr> > >></table> > >> > >>And explain to me how you could do the same using the <thead> element. > > > > > > I normally would use a horizontal structure, not a vertical > > Then add another 23 key-value pairs and have fun with horizontal > scrolling. Well, I see what you mean, but it's rather an exception having a table flat like this, ain't it? Again, what about the <thead /> element now? Assuming you can't use it in this case -- if it was optional, why should we keep it when <th /> offers a better solution for (semantically) highlighting the corresponding content (that's what it seems to do)? Otherwise, if the <thead /> was mandatory, what should I do in this case? The reason why I formulate this topic that provocative (by asking 'stupid' questions) is really simple: Maybe (or definitely) there are elements not needed that urgent, or there is an inconsequent model for a specific module (like the Tables Module here). I can't conceal that I miss some 'elegance' here. Best regards, Jens. -- Jens Meiert Interface Architect http://meiert.comReceived on Wednesday, 15 October 2003 01:37:24 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:58 GMT