On Jan 16, 7:08 pm, Adam Warski <a...@warski.org> wrote: > Hello, > > >> Hmm yes I wondered if the order in which the functions are bound is > >> significant, but my experiments showed that it's not simply a "first > >> bound, first called" principle. So I don't quite get it yet why it doesn't > >> work. > > > We rely on JQuery (or other underlying library) to send the actual > > ajax request. We feed in the correct sequence but if your button is in > > the middle of the form (as fields were added after the button's > > location in the form) the sequence of the function id-s is not sent > > right via ajax even if onclick for the ajax button we first serialize > > the for and then add the function ID of the ajax button. Personally I > > don't see why this is an impediment > > ah, clear now. Thanks a lot for the explanation. This is a small impediment > if the button logically belongs inside the form (if I want the user to see > the button inside the form), but then, as I wrote, I can use css to correctly > position it, although I would consider it a "small hack" :)
Right ... and it's not even a hack ... css is the right way of building layout not really the html. Putting buttons "in the form" ar giving this perception in the page doesn't mean that the button has to be physically in the form element (at least that's the way I see it.). Anyways have fun with Lift :) and thanks for contributing with interesting use-cases. > > -- > Adam
-- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
