validation text boxes with required: true are rude

[alex]

today, validation text boxes show the error state if no default value is provided, even if the user hasn't focused them. The required attribute should show a visual indication that it is a required field (different border color? something) but not the error state. Examples with many of these inputs are glaringly user-unfriedly (like this page: http://dojotoolkit.org/~alex/anon_view/dijit/demos/form.html).

[bill]

ValidationTextBox? itself doesn't differentiate between those two states (empty vs. invalid), but it would be nice to.

[bill]

See ​http://thread.gmane.org/gmane.comp.web.dojo.devel/7588/focus=7593

Consensus so far seems to be to just have different CSS classes for required-but-blank fields vs. invalid-value-fields (with no change in behavior after a field has been accessed or after the form has been submitted). Alex said he had a slight preference for marking the field as invalid after you've touched it. Still want to get input from phiggins.

[bill]

One more response from Peter: ​http://article.gmane.org/gmane.comp.web.dojo.devel/7643, bringing the tally to:

• James: #2 (no change on blur)
• Becky: #4 (on blur mark invalid)
• Eugene: #2
• Sam: #2
• Alex: #4 (either #2 or #4 is ok, slight preference for #4)
• Peter: #4
• Doug: #4

[Douglas Hays]

(In [10729]) Fixes #4427. Required but empty textboxes will have the normal css classes until blurred for the first time.

[Adam Peller]

so now if I don't tab through each input in a form, is it possible I could submit to the server without enforcing require: true? Is that ok?

[Douglas Hays]

Only the decoration is changed. isValid() still returns false.