This is a large usability more than a bug itself. We may want to have a default retainAfterPartialSubmit attribute on the ice:message and messages components, where they retain previous messages until a full submit.

A special message component variant is an interesting idea. Are we losing all validation error messages or just the "required" error messages?

Another option may be to create a custom validator that returns an error until it is cleared – the validator would not test for an empty value until the component was "required", but once "required" would continue to test for an empty value.

Assigning to Philip to comment on which messages specifically are being lost (with input from Tyler from his observations).

This involves any validation message, whether arising from a conversion error, validation error, or missing required error. The proposed new behaviour would be quite simple. A new attribute, such as 'retainOnPartialSubmit' would cause the lifespan of a message to span partialSubmits and only be cleared on a full submit or a partialSubmit originating from the corresponding component of the message itself. This is the desired behaviour requested from both clients.

Revision 15209

revision 15220

revision 15238

revision: 15289

The implemented enhancement is to retain the display of error messages for any components that:

• Were in an invalid state prior to the partialSubmit
• Are not the component that is the subject of the partialSubmit

This supports the use-cases where user's are entering data in a partial-submit form, enter an invalid value in field 1, see the error msg., then move to field2 and enter a value there. Prior to this change the original error msg. from their invalid entry into field1 would disappear when field2 was partialSubmitted. Now error msgs for all invalid state components will continue to be displayed until they are in a valid state.