cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27785] - [PATCH] Form redisplays with validation errors after submit from <wd:action>
Date Sat, 20 Mar 2004 18:48:25 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27785>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27785

[PATCH] Form redisplays with validation errors after submit from <wd:action>





------- Additional Comments From tim@keow.org  2004-03-20 18:48 -------
It was added so that the value of a field could be validated before being used
to select a case for a "union" widget.  We should change it to only validate the
field widgets that are actually put to this use (selecting a case for a "union"
widget), instead of validating all the field widgets like the code currently
does. If you are not using any "union" widgets this would completely solve this bug.
For those who do use a "union" widget the field widgets that are used as
selectors would still trigger validation "early", but that should be acceptable
since the values in those specific field widgets are actually being *used*
early.  Whether we should hide the messages in that case like the proposed patch
does, I do not know.  When "union" get replaced by the redesigned "choice"
widget we will still have this issue, but it will get triggered by the "expr"
attributes' expressions referencing the values in various widgets.

Mime
View raw message