W3C home > Mailing lists > Public > www-style@w3.org > July 2005

Re: FAQ about reasons behind CSS

From: Laurens Holst <lholst@students.cs.uu.nl>
Date: Fri, 01 Jul 2005 16:59:43 +0200
Message-ID: <42C55A5F.30903@students.cs.uu.nl>
To: Orion Adrian <orion.adrian@gmail.com>
Cc: www-style@w3.org

Orion Adrian wrote:

>colspan, rowspan.
>They're presentational.
>Say, for instance, you have a row that's N/A. Really it's N/A in all
>those intersections between one axis and another. A non-presentational
>version of HTML tables would be:
>  <th>Detroit</td>
>  <c>N/A</c>
>  <c>N/A</c>
>  <c>N/A</c>
>  <c>N/A</c>
>  <c>N/A</c>
>table {
>  col-merge-on-value: "N/A"
>A table is a way of presenting data. There are no row or column spans
>in the matrix that that table represents. There are presentation rules
>however that make it easier to parse. Like merging like values with
>something is N/A.
That is absolute and utter nonsense! Colspan and rowspan are meant to 
reduce repetition, to say that a certain table cell applies to more than 
one row or columns. They are in no way presentational.

As an example, look at: http://map.tni.nl/resources/msxsystemvars.php#USRTAB
Or the third table at: 

They are for that reason also not marked as deprecated in the HTML 

Also, I still don’t see how that has anything to do with :nth-last-child().


Ushiko-san! Kimi wa doushite, Ushiko-san!!
Laurens Holst, student, university of Utrecht, the Netherlands.
Website: www.grauw.nl. Backbase employee; www.backbase.com.
Received on Friday, 1 July 2005 14:59:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:19 UTC