Thanks Eelco, it was caused by a bug in Wicket 1.2.4. It works for me in
Wicket 1.2.6
--Andrés
Eelco Hillenius wrote:
> I think you have to use AjaxCallDecorators.
>
> Eelco
>
> On 4/26/07, Andrés Ferrari <[EMAIL PROTECTED]> wrote:
> > Hi everyone!
> &g
useactive==1)return false;
>hideAutoComplete();
> + objonblur();
> }
>
> obj.onkeydown=function(event){
>
> On 4/27/07, Andrés Ferrari <[EMAIL PROTECTED]> wrote:
> > (Sorry the following mail is duplicated... I sent the original to
(Sorry the following mail is duplicated... I sent the original to the wrong
thread)
---
Hi everyone!
I'm having trouble with an AutoCompleteTextField. I want to add an ajax
behavior to it (specifically, for "onblur") like can I do with other wicket
components, but somehow it doesn't work.
I
Hi everyone!
I'm having trouble with an AutoCompleteTextField. I want to add an ajax
behavior to it (specifically, for "onblur") like can I do with other wicket
components, but somehow it doesn't work.
I can add an AjaxFormComponentUpdatingBehavior to a TextField and it works.
I cannot add it
Hi everyone!
I read on the devel list that you're voting about merging the fix to issue
wicket-371 into 1.2.6. It would really help me if you did. It would fix a
problem in the app I'm developing, which currently requires a workaround.
The context: I'm using statefull non-singleton beans, injec
Frank Bille wrote:
> On 1/11/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > Imo, it would be intuitive to keep the order in which they were added.
> > Unless there is some urgent reason why the ajax engine should want to
> > give components priority over others
>
> +1
Igor's suggestion worked
Hi everyone!
I have the following problem: I'm using Ajax to enable a Date field +
DatePicker combo, depending on a third field, and it is important to me that
during the updating behavior the components get processed in the right order.
Example:
someField.add(new AjaxFormComponentUpdatingBeha
