[whatwg] WF 2.0 -- HTMLTextAreaElement [ type ] attribute

2007-09-15 Thread Garrett Smith
Yes, I was assuming. That was my mistake. type is in fact a DOM property, not an attribute. Should have thought twice before posting. On 9/15/07, Magnus Kristiansen <[EMAIL PROTECTED]> wrote: > On Fri, 14 Sep 2007 02:52:33 +0200, Garrett Smith <[EMAIL PROTECTED]> > wrote: > > > Regarding the [ty

Re: [whatwg] WF 2.0 -- HTMLTextAreaElement [ type ] attribute

2007-09-15 Thread Magnus Kristiansen
On Fri, 14 Sep 2007 02:52:33 +0200, Garrett Smith <[EMAIL PROTECTED]> wrote: Regarding the [type] attribute: interface HTMLTextAreaElement : HTMLElement { attribute DOMString defaultValue; readonly attribute HTMLFormElement fo

Re: [whatwg] WF 2.0 -- HTMLTextAreaElement [ type ] attribute

2007-09-15 Thread Benjamin Hawkes-Lewis
Presumably return a MIME type e.g. text/plain, text/html. IIRC this idea was never fully thought out. Many textareas accepting HTML actually want a fragment and often only a subset of markup. It would be handy to have some way of specifying such profiles for clientside authoring tools to use.

Re: [whatwg] WF 2.0 -- HTMLTextAreaElement [ type ] attribute

2007-09-15 Thread Kristof Zelechovski
If I were one, I would return "text", just like it does in an input control does. Cheers Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Garrett Smith Sent: Friday, September 14, 2007 2:53 AM To: [EMAIL PROTECTED] Subject: [whatwg] WF 2.0 -- HTMLTex

Re: [whatwg] successful form controls

2007-09-15 Thread Kristof Zelechovski
1. Radio buttons are never checked so this sentence means that they are never successful. 2. A control that is read-only does not accept input from the user; however, it may have a meaningful value that is worth submitting because its value can be calculated on the client side. Although the server