Oh, woops, yep, tr:subform is a much convenient than manually mucking with the immediate attribute. Thanks Andrew!
Andy On Wed, Dec 17, 2008 at 11:08 AM, Andrew Robinson <[email protected]> wrote: > Look at tr:subForm > > On Wed, Dec 17, 2008 at 2:57 AM, <[email protected]> wrote: >> Hi, >> >> >> >> On one of my pages I've got 2 tr:selectOneChoice boxes – box A and box B. >> The content of box B depends on the selection of box B. I'm using >> autoSubmit="true" for box A and partialTriggers="boxA" for box B. This works >> perfect unless I'm setting the required="true" attribute for box B. That >> causes a validation of the box B selection when a change in box A occurs. >> Seperating both boxes with tr:subforms doesn't work with the >> partialTriggers, so this is no solution. >> >> Am I right in thinking that I can't use the required="true" attribute for >> box B or did I overlook other ways to implement this? When it's not possible >> to set the required="true" for box B this is no problem for me because I >> can validate all fields later, but I want to know it because I don't like >> smelling code. >> >> >> >> Thanks you and best regards >> >> >> >> Felix >
