W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2004

[whatwg] Web Forms 2.0 Substantive - Section 5

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 23 Jun 2004 11:13:23 +0000 (UTC)
Message-ID: <Pine.LNX.4.58.0406230952550.30035@dhalsim.dreamhost.com>
On Tue, 15 Jun 2004, fantasai wrote:
>
> 5. Form submission
> ------------------
>
> # Step six: Submit the encoded form data set
> #
> #  Finally, the encoded data is sent to the processing agent designated by the
> #  action attribute of the element that initiated the submission using the
> #  protocol method specified by the method attribute of that same element.
>
> Depending on what you meant by "defaults" in section 2.7, this
> description may be wrong.

Fixed, although that was actually already handled by the section that the
next sentence in the paragraph you quoted above referred to, saying that
it had more details.


> 5.2. Handling characters outside the submission character set
> -------------------------------------------------------------
>
> # The data will be sent as "D?rst".
>
> You need to also give the source that triggered this error before
> the dialog makes sense.

Fixed.


> 5.3. application/x-www-form-urlencoded
> --------------------------------------
>
> # The values of file upload controls are the names of the files selected by
> # the user, not their contents.
>
> Does this include the path? (I think it should not, but you'd
> need to say so.)

Fixed.


> 5.4. application/x-www-form+xml: XML submission
> -----------------------------------------------
>
> # If the user selected a second (image) file "file2.png", and changes the date,
> # the user agent might construct the entity as follows:
>
> Don't do the "changes the date" bit in this example. It implies that
> this is a second submission after the first rather than a variant of it.

There was. That was entirely the point of the example.

Fixed though.


> 5.6.1. For http: actions
> ------------------------
>
> under 'get'
>
> # Handle as if enctype was application/x-www-form-urlencoded
>
> I think you need to specify some kind of escaping on that data
> before you handle it like x-www-form-urlencoded.

I don't understand what you mean.


> 5.6.3. For data: actions
> ------------------------
>
> # If the action contains the string "%%%%", then URI escape all
> # non-alphanumeric characters in the form data set...
>
> form data set -> encoded form data set
>
> Also, for the 'put' column, you need to add "Then, access the
> resulting URI."

Fixed.


> 5.6.4. For file: actions
> ------------------------
>
> # If the specified file is executable...
>
> What if it's not?

Fixed. Also fixed the description of when it is executable, which was
rather poorly described.


> 5.6.5. For mailto: actions
> ------------------------
>
> under 'get'
>
> # Handle as if enctype was application/x-www-form-urlencoded
>
> I think you need to specify some kind of escaping on that data
> before you handle it like x-www-form-urlencoded.

I don't understand what you mean.


> 5.6.6. For smsto: and sms: actions
> ----------------------------------
>
> File upload & post :
> # Handle as if enctype was application/x-www-form-urlencoded.
>
> Does that mean you're sending the binary file data as the body
> of the sms message without any kind of MIME information?

No? I don't understand why you would interpret this that way.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 23 June 2004 04:13:23 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:34 UTC