oh that would be a big overhead for me as the forms i'm talking about can grow to have 100s of inputs. so serializing to detect changes doesn't seem to be a good idea, neither having TimedObservers on Form.Element level.
guess my best option is to set the onchange attribute on input elements to trigger some custom event <input onchange="Element.fire(this, 'form:change')" /> then capture this event on the form object .. argh i can't believe how much time we spend on IE hacks and workarounds. cheers -- mona On Mon, Aug 31, 2009 at 12:45 PM, T.J. Crowder<[email protected]> wrote: > > Hi Mona, > > Have you considered using Form.Observer[1] instead of events? > > [1] http://prototypejs.org/api/timedObserver/form-observer > -- > T.J. Crowder > tj / crowder software / com > www.crowdersoftware.com > > On Aug 31, 10:07 am, Mona Remlawi <[email protected]> wrote: >> Hello Prototypers, >> >> I am currently in the process of implementing events delegation on HTML >> forms. >> As you might know, IE does not bubble the onchange event :( and i find >> that the onblur is a poor and a high maintenance alternative. >> Can anyone propose a neater solution? >> The forms i'm delegating events on have repeatable sections, so that's >> why i would insist on delegation. >> >> Thanks in advance >> >> cheers >> >> -- >> mona > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
