2 Feb 2009 9:01 AM #1
[FIXED][1.2.2] RadioGroup broke in IE.
RadioGroup doesn't work properly in IE (both 6 and 7) when using 2 or more radio groups in the same panel.
Apparently, IE isn't able to differenciate the different groups and wrap all the radios in a
The bug is exposed with the following code:
Radio radio = new Radio(); radio.setName("radio1"); radio.setBoxLabel("Red"); radio.setValue(true); Radio radio2 = new Radio(); radio2.setName("radio2"); radio2.setBoxLabel("Blue"); //First radio group RadioGroup radioGroup = new RadioGroup("test"); radioGroup.setFieldLabel("Favorite Color"); radioGroup.add(radio); radioGroup.add(radio2); this.add(radioGroup); Radio radio3 = new Radio(); radio3.setName("radio3"); radio3.setBoxLabel("High"); radio3.setValue(true); Radio radio4 = new Radio(); radio4.setName("radio4"); radio4.setBoxLabel("Low"); //second radio group. RadioGroup radioGroup2 = new RadioGroup("power"); radioGroup2.setFieldLabel("Power"); radioGroup2.add(radio3); radioGroup2.add(radio4); this.add(radioGroup2);
2 Feb 2009 9:03 AM #2
2 Feb 2009 9:07 AM #3
You just have one radio group in that example. With two radios. That's ok.
Now try to create below a new radio group, with 2 new radios, for example. You will see that all them are mixed.
2 Feb 2009 9:22 AM #4So please post some complete testcase.
2 Feb 2009 9:48 AM #5
3 Feb 2009 1:52 PM #6
There is an issue with submitting the form with even single radio group in 1.2.2. It used to work fine in 1.2.1. The value on the server is always coming as "on" in 1.2.2 irrespective of the radio that is clicked in the group. In 1.2.1 the value going to servlet used be the label name of the radio that was clicked.
4 Feb 2009 5:28 AM #7
What's the status on a fix for this bug? I am having the same problem in Internet Explorer.
4 Feb 2009 8:52 AM #8
Fixed in SVN.
11 Aug 2009 4:11 AM #9
Still having the same problem with 2.0.1
I am using 2.0.1 and facing the same issue, is the fix available in this version. Please let me know?
Thanks and Regards,
11 Aug 2009 4:30 AM #10
These forums are for GXT 1.2.x and this bug is fixed here.
If you have this problem in version 2.0.x, please, report it in the GXT 2.0.x forums