Thinking the matter over a little bit more, there's a fairly straightforward workaround. By removing any listener from the form and binding them all to submit button action values, I can get the desired behavior. Of course, this does mean more template changing which is not as transparent as I'd like, but not terrible either.
The "autoSubmit" parameter seems broken though, so I'll be poking around JIRA for that. -- Kevin On 12/20/07 6:55 PM, in article [EMAIL PROTECTED], "Kevin Menard" <[EMAIL PROTECTED]> wrote: > On 12/20/07 5:51 PM, in article > [EMAIL PROTECTED], "Jesse Kuhnert" > <[EMAIL PROTECTED]> wrote: > > >> In theory it will take all the arguments to the client side function >> (including the javascript event, which should have a >> target/relatedTarget/etc attribute attached to it) and serialize them >> in some form that you can then try to interact with in the form of a >> JSONArray. I've not used it though so don't know what will happen >> under which circumstances / etc.. > > Ahh. Cool. I guess ideally I'd be able to a serialized copy of the DOM > node, sorta like I can do with jQuery. Then I could dump the server-side > value altogether and just use a plain ol' checkbox. > > I guess I'll put EventListener back on the shelf until then. > > Thanks for the info, > Kevin > > > > --------------------------------------------------------------------- > 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]
