On 10/21/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > Hold on, the raw input _must_ be preserved after rendering. Where else > would we keep invalid input?
Why do we need to keep invalid input after rendering? Any such input is already consumed for feedback messages, and the renders should either render their model values if they did not get new input, or render *new* input that may have been submitted. > The code also doesn't make sense - there > is no reason why it shouldn't work, except when the page was submitted > before the render and the submit was not validated. But that is exactly my problem! So any form submit that doesn't validate subsequently holds back updating of any of the form components via Ajax like my example does, because the inputs aren't cleared (whether they are valid or not). > Am I missing something? Am I? What are the disadvantages of my fix exactly? I think the per-request scope is just right, and anything that should be persisted over multiple requests should be done via model updates. Eelco
