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

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

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Wed, 2 May 2007 14:06:03 -0700
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF403114F28@usa7061ms01.na.xerox.net>
To: "John Boyer" <boyerj@ca.ibm.com>, <public-forms@w3.org>
I apologize for the distraction during the meeting and for sending both
issues in the same message.
- If you submit with method="get", nodes whose string content is empty
get elided, so there's no way to do a GET of 
Instead, you get
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
- 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.


From: public-forms-request@w3.org [mailto:public-forms-request@w3.org]
On Behalf Of John Boyer
Sent: Wednesday, May 02, 2007 1:13 PM
To: public-forms@w3.org
Subject: List discussion issue: Pruning empty nodes on url-encoded

Turns out the link in the agenda was correct:

It is the submit-on-enter example from Leigh, which includes information
from Aaron Reed. 

The email points out two problems, the submit-on-enter problem AND the
problem that empty nodes are pruned on URL encoded submissions, instead
of submitting them as empty values. 

Let's get some discussion going on the list here about what the correct
behavior should be. 

John M. Boyer, Ph.D.
STSM: Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com  

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer

Received on Wednesday, 2 May 2007 21:06:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:13:51 UTC