W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2006

[whatwg] introduction, plus some form input ideas

From: Brad Fults <bfults@gmail.com>
Date: Fri, 3 Feb 2006 17:58:53 -0800
Message-ID: <1959130b0602031758yb85de5i1a86deb84177970b@mail.gmail.com>
On 1/30/06, Ric Hardacre <ric at hardacre.org> wrote:
> hello, i'm an asp developer in the uk and have a couple of
> suggestions... no doubt selfishly to make my life easier one day :-)
> these could probably do with their own threads if they're deemed worthy
> of discussion but let's just throw them out there:
>
> 1. form tag:
>     send="all" , (default, send all fields to server in get/post)
>     send="changed" , only send hidden fields and fields that have been
> changed by the user

Agreed, this is useful. Details of the implications of this, however,
I am not so sure of.

> the idea being that if i'm running a datagrid then there's no point
> sending a ton of data back and forth if the user only edits a couple of
> cells. but the hidden form data will still be needed in any case so i
> can still connect the data sent to the user who sent it!
>
> 2. select tag:
>     selectedindex="[num]"

Agreed. This would be very useful.

> implicitly set the selected index, instead of having to parse all the
> option tags and insert a "selected" string, much easier to bind to
> server side data, an invalid value (such as -1 or greater than the
> number of option tags) would mean none are selected. this would
> obviously not apply to multiple-selects
>
> 3. input tags:
>     validate="[regex]"

See: http://whatwg.org/specs/web-forms/current-work/#the-pattern

--
Brad Fults
NeatBox
Received on Friday, 3 February 2006 17:58:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:26 UTC