W3C home > Mailing lists > Public > public-forms@w3.org > October 2007

Re: List discussion issue: Pruning empty nodes on url-encoded submission

From: Blake Jones <blake.jones@ViewPlus.com>
Date: Wed, 03 Oct 2007 12:31:06 -0700
Message-ID: <4703EDFA.7020201@ViewPlus.com>
To: "Klotz, Leigh" <Leigh.Klotz@xerox.com>
CC: public-forms@w3.org
Hi Leigh (et al),
attached is a proposed update to the spec that addresses this.  The 
issue was only mentioned with respect to url-encoded submissions, but I 
wonder if this might also affect multipart/form-data submissions 
(http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-all.html#serialize-form-data) 
(and others?) as well.  I'm anything but an expert on form submission.

Regards,

Blake

Klotz, Leigh wrote:
>  
> - If you submit with method="get", nodes whose string content is empty 
> get elided, so there's no way to do a GET of
>  http://example.com/query?a=1;b=;c=3
> Instead, you get
>  http://example.com/query?a=1;c=3
>  
> I believe the correct behavior is that the empty item should be 
> serialized as "name=" but no value.
> I believe that only missing or non-relevant b is what should cause the 
> elision.
>  
> - In HTML4, empty string content values are still submitted.
>  
> Attached are examples of a single-parameter query/echo form example in 
> XHTML+XForms and XHTML1.
>  
> Leigh.

-- 
Blake Jones
Software Engineer
ViewPlus Technologies
blake.jones@viewplus.com




Received on Wednesday, 3 October 2007 19:31:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:45 UTC