looks like we need to update form processing code to skip inner disabled forms, mind making a jira issue?
the whole concept is somewhat radical and we havent been able to think through it completely just because its new. so there are still a few caveats here and there for embedded forms. -igor On 11/1/07, Gwyn Evans <[EMAIL PROTECTED]> wrote: > Thursday, November 1, 2007, 4:26:24 PM, you wrote: > > IV> wait until you discover we support embedded forms, that will really > IV> screw with your mind... > > Talking of which, are there any "Best Practices" for dynamic instances > of that? > > The specific issue I've just run across is where I have a outer form > and, depending upon a checkbox, might have an inner form being enabled > of not. (It's an inner form, rather than just a part of the main form > as it's off as a component with it's own panel.) > > Anyway, the inner form has password/confirmPassword fields and an > EqualInputValidator, but if the form is displayed but then disabled > again (via Ajax, if significant,) when the form's finally submitted I > get a warning, saying "IFormValidator in form '...' depends on a > component that has been removed from the page or is no longer visible. > Offending component id `password`." > > Any thoughts on the best approach to this? > > -- > /Gwyn > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
