Thiago H. de Paula Figueiredo wrote: >> <t:loop t:source="objetcs" t:value="current" t:formState="iteration"> >> <t:submit t:id="toggleState" t:context="[another, current]"/> >> </t:loop> > I'm not sure, but maybe we can't use the Submit component this way. Take a > look at the generated HTML (specially the submit buttons and hidden > fields) and post it here please.
For a loop over two objects, the submit buttons look like this: <input value="Change" name="submit_0" type="submit"></input> [...] <input value="Change" name="submit_0_0" type="submit"></input> Within the loop there are no hidden fields. In the whole page there are only two of them, one for the ActivationContext and one formData. > I've been using ActionLinks or EventLinks inside Loops and Grids > successfully. What I need is a button which does some change to an object. I do not want the user to lose data he entered for other objects, so I decided to use a form submit. Will this be possible with ActionLinks and EventLinks? Do they work without JavaScript? Thanks for your help! Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
