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



RadioGroup, differences between FireFox and Internet Explorer?

2008-12-16 Thread Swanthe Lindgren
I have this wierd behavior where a RadioGroup works perfectly well with 
FireFox but not with IE7. Both IE and FF fires the event and the server 
side event handler is executed in both cases, but with IE the model is 
not updated when I try to retrieve it in the 
AjaxFormChoiceComponentUpdatingBehaviour.onUpdate method.


Can anyone spot where I took a wrong turn?

//Swanthe

Page java code:

RadioGroupDepositType depositType = new 
RadioGroupDepositType(depositType, new 
PropertyModelDepositType(model.getObject(), depositType));


RadioDepositType wire = new RadioDepositType(wire, new 
ModelDepositType(DepositType.WIRETRANSFER));

wire.setOutputMarkupId(true).setMarkupId(wire);
depositType.add(wire);

RadioDepositType card = new RadioDepositType(card, new 
ModelDepositType(DepositType.OTHER));

card.setOutputMarkupId(true).setMarkupId(card);
depositType.add(card);

RadioDepositType cheque = new RadioDepositType(cheque, new 
ModelDepositType(DepositType.CHEQUE));

cheque.setOutputMarkupId(true).setMarkupId(cheque);
depositType.add(cheque);

depositType.add(new AjaxFormChoiceComponentUpdatingBehavior(){
 @Override
 protected void onUpdate(AjaxRequestTarget target) {
   DepositType depositType = model.getObject().getDepositType();
 }
});


Page html code:

div wicket:id=depositType
 div class=leftColumn 
   div class=contentRow style=border-bottom-style: dotted
 div class=contentRowText
   input wicket:id=wire class=radioButton type=radio/
   div style=float: left; margin-left: 16pxlabel 
for=wirewicket:message key=field.TypeWireDeposit by Wire 
Transfer/wicket:message/label/div

 /div
   /div
   div class=contentRow style=border-bottom-style: dotted
 div class=contentRowText
   input wicket:id=card class=radioButton type=radio/
   div style=float:left; margin-left: 16pxlabel 
for=cardwicket:message key=field.TypeCardDeposit by Debit or 
Credit Card/wicket:message/label/div

 /div
   /div
   div class=contentRow style=border: none
 div class=contentRowText
   input wicket:id=cheque class=radioButton type=radio/
   div style=float: left; margin-left: 16pxlabel 
for=chequewicket:message key=field.TypeChequeDeposit by 
Check/wicket:message/label/div

 /div
   /div
 /div
/div


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