> > The problem with textarea is, how it should be displayed, when > > CSS is off? Should it default to 5, 10, 15, 20, ... rows? How > > wide should it be? Wide enough to write a poem, or as wide as the > > entire page? > > But that's a UA issue, and UAs handle the same thing for inputs and > selects already. Whether they do a good job or a bad one is certainly up > for question, but taking the "what if CSS is off" approach can lead to > an argument for reintroducing any presentational stuff back into the > markup...i.e. it's a slippery slope.
That's exactly what I was thinking as well. Who is to decide how long a horizontal rule <hr /> should be? Or, what the default font size a header <h1> should be? I like the idea of the WHATWG 'wrap' attribute, but again, wouldn't this be purely presentational? If the line breaks needed to be inserted into the inputted text couldn't that be done on the server side easier than trusting the client's machine to do the work? Sorry about all the theoretical questions... it's a Monday! :) Jough ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
