On Friday, August 22, 2003, at 12:18 PM, Jukka K. Korpela wrote:
> 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.
>> 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
> logically a table, with labels in one column, corresponding fields in
I kinda disagree.
It's definitely in a table because that's how your laying it out.
However I'd argue that a bunch of empty input boxes and a submit button
are not data, it's just a means of capturing data.
Once the data has been input It's cool to display that inputted data
back to the user in the form of a table. But until that data exists,
you're not using the form to display it!
I'm sure one could come up with loads of arguments saying a row of news
article headlines, a row of news articles summaries and a row of links
to that news article could be considered to be tabular data as well.
I think most people understand what tabular data is and isn't, and if
you've got to debate if something is tabular data or not, it probably
There is nothing wrong with creating hybrid layouts using tables and
CSS for 99% of cases. However if you happen to be designing a site that
has to use CSS layout and correct XHTML (say for a showcase or
competition) I'd say using tables to layout a form was a bit of a cheat.
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/