W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2007

[whatwg] [wf2] form submission algorithm questions

From: Benjamin West <bewest@gmail.com>
Date: Mon, 16 Apr 2007 12:28:12 -0700
Message-ID: <8ad71be30704161228u1db7f739m1c5e1903cfcbbb3c@mail.gmail.com>
On 4/16/07, Kristof Zelechovski <giecrilj at stegny.2a.pl> wrote:
> What do you mean by "rinse"?  Only the end user is in position to make the
> necessary corrections if the input is invalid.  Any interaction with the
> user should not be executed inside a loop because it is a frustrating
> experience where you do not know where you are, what you are operating on
> and how to get out of this mess (reminds me of Emacs recursive edit mode) so
> that "repeat" afterwards really does not make sense.  After the user feels
> ho is ready, ho can resubmit, triggering another event thereby.
> Chris
>

I apologize, "rinse and repeat" is a familiar idiom in the U.S. after
shampoo bottles started including these instructions.  If there is
something wrong with the input (as decided by the application),
feedback is provided to the user, and she is given an opportunity to
fix.  This process is iterative (eg rinse and repeat) so that the user
can iterate towards success without suffering consequences (such as
long waiting times) in between corrections.  My proposal intends to
put the user in control by offering a more immersive and responsive
control, reducing spurious or confusing error messages (of the ilk
"you need to enter a string instead of a number").  There is no
automatic procedural loop, just an iterative process for validating
and submitting sane input.

Thanks for pointing out the ambiguity.

-Ben

> -----Original Message-----
> From: whatwg-bounces at lists.whatwg.org
> [mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Benjamin West
> Sent: Monday, April 16, 2007 12:11 AM
> To: WHAT Working Group Mailing List
> Subject: [whatwg] [wf2] form submission algorithm questions
>
> [cut]
> I suggest something like:
>
> 1.) Step One:     a new event "onvalidate" is dispatched
> 2.) Step Two:     Identify form controls.
> 3.) Step Three:   build form data set.
> 4.) Step Four:    encode data set.
> 5.) Step Five:    submit data set to validation URI.
> 6.) Step Six:     dispatch recieved
> 7.) Step Seven:   process validation results
>   if response indicates validity->
>    Submit using steps 2 - 8 of original algorithm.
>   if response indicates invalid input->
>    rinse and repeat
>
> [cut]
>
>
Received on Monday, 16 April 2007 12:28:12 UTC

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