Hi Justin I'm not 100% sure about that, but after a quick look at prototype source code, I would recommend you the following solution: 1. change the DIV (child of FORM) into FIELDSET (better semantics) 2. use Form.serialize(YOUR_FIELDSET)
And the general solution for prototype could be extending the fieldsets with the methods like serialize() :) Greetings :) On 17 Kwi, 08:42, mr_justin <gro...@jperkins.otherinbox.com> wrote: > Joran, that is too funny man. Please re-read my question and then your > response. ;) > > Let me explain a bit more, so the idea is clear. > > I have a form with a bunch of form controls in it (say it ain't so!). > Within that form is a DIV that has even more form controls in it. For > the sake of simplicity, let's say all the form controls outside of the > DIV are for one record, and all the form controls inside the DIV are > for a different record. > > I think it would be darn handy to be able to do this: $('my- > form').serialize({within:'my-div'}); > > With the whole nested forms stuff in Rails 2.3, I thought this topic > might have come up already. It would be cool to make the serialization > logic more flexible (pluggable, as you say Andrew). As it is now, it's > an all or nothing, my way or the highway kind of approach. Which > honestly is fine 99% of the time. And when it's not, there's things > like Simon's snippet can meet those wacky esoteric needs. > > -justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---