Hi,
I've been searching around a bit and found the solution. I figured maybe
someone else will face the same issue. It's pretty darn simple anyway.
I used to do what I wanned like this:
someRadio.add(new AjaxEventBehavior("onchange"){...}
This worked great in FF, but in IE7 it didn't... all i did is change
"onchange" with "*onclick*" and now it works in both.
I think that FF handles onchange for the *newly selected item* while IE7
does it for the *element which gets deselected*. I'm not 100% sure, anyways,
maybe somebody can say for certain.
Thanks Igor,
Cristi Manole
On Fri, Apr 4, 2008 at 10:01 AM, Igor Vaynberg <[EMAIL PROTECTED]>
wrote:
> make sure you dont have any span tags attached to wicket components
> that have div tags inside.
>
> also past the output of wicket ajax console
>
> -igor
>
>
> On Thu, Apr 3, 2008 at 11:52 PM, Cristi Manole <[EMAIL PROTECTED]>
> wrote:
> > Hello,
> >
> > I have on a page 3 radio buttons in a group and for each radio a drop
> down:
> >
> > x DropDown1 V
> > o DropDown2 V
> > o DropDown3 V
> >
> > When the user selects a radio, the corresponding dropdown will be
> enabled
> > and the other two disabled.
> >
> > In Firefox, this works as I need it to, but in IE, the dropdowns are
> not
> > enabled/disabled as needed (either not at all - in IE6 or oddly in
> IE7). The
> > funny thing is the functionality is there - i mean, although
> graphically
> > they are wrong, I can change the values only for the dropdown which is
> > enabled. And when I try to do that, all the dropdowns will be updated
> > correctly.
> >
> > Any ideas what's wrong with IE and how i could update the dropdowns
> > correctly? I use just setEnabled(true/false) and
> target.addComponent(...).
> >
> > Thanks,
> > Cristi Manole
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
