Sent by Jukka K. Korpela on 22 August 2003 12:12
On Fri, 22 Aug 2003, Andy Budd wrote:
> Personally I can't see how people can class forms as tabular data.
Try defining "tabular data", and you will see.
> You[']r[e]
> not *displaying* data, your capturing data.
A form defines a set of form fields with associated labels, plus maybe
something else. The inherent associations make the form, or part thereof,
logically a table, with labels in one column, corresponding fields in
another.
ObCSS: The CSS argument, so to say, for the tabularity claim is that
if you have form markup without a table and you wish to use CSS to format
the form, then you would actually use display: table and relatives,
if (a) you knew about them, (b) they would work on current browsers.
If fact, even when you don't do that and use less adequate CSS tools
instead, you will find yourself looking for markup that expresses how
the material constitutes "rows" that are divided into "cells" so that you
can e.g. make "cells" in a "column" occupy the same width. That is, you
are looking for table markup, or its surrogate, and this is no coincidence
but a consequence of the nature of the data.
(Except perhaps in simplest cases, which are so simple that they can be
regarded as reduced cases, like a scalar is a reduced case of a vector.)
--
Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
