From: Mike S. <ms...@md...> - 2008-02-28 15:38:46
|
You should not specify observeFieldID for this to work. It will not render children components if you specify observeFieldID. for instance, your span example: <wo:form> <wo:AjaxObserveField elementName = "span" id = "YourSpanID"> <wo:textfield value = "$firstName"/> <wo:textfield value = "$lastName"/> </wo:AjaxObserveField> </wo:form> ms On Feb 28, 2008, at 10:27 AM, Johann Werner wrote: > > Am 27.02.2008 um 15:24 schrieb Mike Schrag: > >> The new AjaxObserveField allows you to wrap a set of components and >> it >> will automatically observe all of them, so you don't have to add an > > What exactly do you mean by wrapping some components? Looking at the > source code (of today) and a quick test shows that enclosing > elements by the AjaxObserveField removes them from the generated > page as AOF does not call appendResponse on child elements. > > Trying to enclose some elements with a span tag and using its id to > observe doesn't work either. Though that feature would be quite > usefull as I am trying to make a radio button list work together > with ajax. > > jw > > >> >> observe field for every single one ... That might be helpful in this >> case. That will save every time you type rather than onblur, though, >> I think. You could also make an AjaxSubmitButton with a functionName >> and no updateContainerID and onblur = "yourFunctionName()" on each >> textfield. That would be pretty painless, also. >> >> ms > < > snip > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |