Re: mosaic pre6 coming soon, and more forms stuff

• Mail folder: WWW Talk Oct 93-present
• Next message: Kevin Altis: "Re: request for new forms submission consensus"
• Previous message: Dave_Raggett: "Re: request for new forms submission consensus"
• In-reply-to: Marc Andreessen: "mosaic pre6 coming soon, and more forms stuff"
• Reply: Marc Andreessen: "Re: mosaic pre6 coming soon, and more forms stuff"

X-Delivered: at request of secret on dxcern.cern.ch
Message-id: <9310121637.AA12860@rs042.scic.intel.com>
X-Sender: kevin@rs042.scic.intel.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 12 Oct 1993 09:34:11 -0800
To: marca@ncsa.uiuc.edu (Marc Andreessen), www-talk@nxoc01.cern.ch
From: kevin@scic.intel.com (Kevin Altis)
Subject: Re: mosaic pre6 coming soon, and more forms stuff

At 10:21 PM 10/11/93 -0700, Marc Andreessen wrote:
>As I noted last night (and Bill Perry, at least, agreed), I think
>multiline texts fields should have a different name than single-line
>text fields.  Is "textarea" OK?  Also, we have three choices for
>declaring the size of a "textarea":
>
>    o SIZE="32x4" as in the original spec
>    o SIZE="32,4" to fit in a little better with other things
>    o COLUMNS=32 ROWS=4 for extreme cleanliness (which is what we
>      currently have)

What I don't understand, is why you have to specify the column and row size
at all? Are the row and column attributes simply to tell the client what
size box to create for text entry? Is the multiline text field only going
to apply to text entry of a particular line length? It seems like we should
just have a textblock entry where the user can enter an arbitrary amount of
text and the widget will handle text wrapping and scrolling.

ka