Hi Thiago, thanks, but no, I'm not using value change events only, but action link events also.
You are right, that some lines of js code will be sufficient to trigger the submission of the surrounding form, but the logic of my event handlers have to be performed BEFORE the form submission, so the desired order of events is: 1.) call action link or valueChanged event handler 2.) perform custom code in these handlers 3.) submit form values and server side state 4.) refresh zone arround the form I will do like you proposed, but I dare that won't lead to the right event order ... Greetings Erich On Fri, 21 Nov 2014 11:41:07 -0200, "Thiago H de Paula Figueiredo" <thiag...@gmail.com> wrote: > On Fri, 21 Nov 2014 11:23:13 -0200, Erich Gormann <e.gorm...@gormann.de> > wrote: > >> Dear all, > > Hi! > >> So my idea was simple to trigger a from submission manually for instance >> from within my onValueChanged event handler, which is called >> automatically from the select field on a value change. The form >> submission seems the only way to update the server side representations >> of the client input elements in a zone refresh. > > If you're just using Select's valueChanged event just to submit the form > automatically without writing JavaScript, I think you're going in the > wrong direction. A couple of lines of JavaScript allow you to listen for > <select> value changes and to submit the surrounding form. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
