Re: RadioGroup, differences between FireFox and Internet Explorer?

2009-02-17 Thread Swanthe Lindgren
I still have the same problem and as the project where it occurred is 
on ice I left it for what is is. I haven't even filed a JIRA, but 
please go ahead and do so since it still doesn't work in 
wicket-1.4-SNAPSHOT.


//Swanthe

metalotus wrote:

I have the same issue. Some places in my application, adding
AjaxFormChoiceComponentUpdatingBehavior to a RadioChoice simply does not
work under IE7. The ajax response is invoked, but the browser does not
actually select the new radio button.

For example, in one place I have such behavior and it works fine, in another
it does not work under IE7 only. I noticed the POST looks different. Here is
a comparison of the POST:

POST from a place where it works:

ChartTypeForm95_hf_0

utilChartRadioButtonsId 

BAR


POST from a place where it is broken:

view:wizardpanel:hostAddressEditorWindow:mainPanel:contentsPanelID:modalDialogForm:contentsPanelID:tabpanel:panel:emtabpanel:panel:panel:form:matchOptions
  

RESERVED


On, the not working post, why does it not look more similar to the working
post, such as:


formXYZ

matchOptions

RESERVED



My guess is this that when there are nested form elements, the POST is
different, and that breaks under IE7.

  




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: RadioGroup, differences between FireFox and Internet Explorer?

2009-02-16 Thread metalotus

I have the same issue. Some places in my application, adding
AjaxFormChoiceComponentUpdatingBehavior to a RadioChoice simply does not
work under IE7. The ajax response is invoked, but the browser does not
actually select the new radio button.

For example, in one place I have such behavior and it works fine, in another
it does not work under IE7 only. I noticed the POST looks different. Here is
a comparison of the POST:

POST from a place where it works:

ChartTypeForm95_hf_0

utilChartRadioButtonsId 

BAR


POST from a place where it is broken:

view:wizardpanel:hostAddressEditorWindow:mainPanel:contentsPanelID:modalDialogForm:contentsPanelID:tabpanel:panel:emtabpanel:panel:panel:form:matchOptions
  

RESERVED


On, the not working post, why does it not look more similar to the working
post, such as:


formXYZ

matchOptions

RESERVED



My guess is this that when there are nested form elements, the POST is
different, and that breaks under IE7.

-- 
View this message in context: 
http://www.nabble.com/RadioGroup%2C-differences-between-FireFox-and-Internet-Explorer--tp21033535p22044721.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org