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

Required but empty

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Fri, 25 May 2007 13:56:41 -0400
Message-ID: <46572359.6080304@orbeon.com>
To: public-forms@w3.org
CC: www-forms-editor@w3.org


I have a doubt about the meaning of "empty" in the wording "required but 
empty" (which appears in 11.2.3 and 4.3.5).

It seems that "empty" could either mean:

1. A zero-length string (clear technical interpretation)
2. A string empty as per #1 above, or a string with only white-space
    (human-friendly interpretation)

Imagine a user entering by error a space in an input field. Visually, 
with most agents (typically web browsers), you can't tell whether the 
field is empty according to #1 above, or contains white space. So to the 
user, the field is "empty".

But if the XForms implementation implements #1, then this visually empty 
field will be considered non-empty, and pass submission even if required.

This would favor an interpretation of "empty" where not only strictly 
empty strings are "empty", but also strings containing only white space.

At the very least, the spec should say whether it means #1, #2, or 


Orbeon Forms - Web Forms for the Enterprise Done the Right Way
Received on Friday, 25 May 2007 17:56:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:38:09 UTC