It's very difficult to help if you haven't posted the code - please add it so we can see what you are doing :o) Thx

On a radio button I would probably put the action on the onChange event rather than the click. You would have to check the firing order but I wonder if the value is not changed until after the onClick event so your code executes too soon. I have not tested this but it would not be hard to do some out put to the console on each of the events. 

I know that at one point I tried some code in the onClick event of a combo box which did not work very well, changed it to the onChange event and it did what I wanted.

Well of course we should be able to make the radio button work....

But are you using the radio button for the "yes" "no" bit?

I typically don't see or use this pattern myself.  I see Radio buttons more for different "states" of a record.

In you're case I'd throw the text out:

"Is this the right address?"

And then have actual butttons or links styled as buttons for the "Yes" and "No".  Since you want to re-render something from the event itself I think buttons/links work better in this case.

(Of course that's just an opinion and I've not seen the rest of the app)..

Good Luck

Dave

I have used a single CheckBox but always have looked at the onChange event not the click to do something along the line that you are doing, and I believe that the checkBox is a bit more intuitive, however, having said that I see no reason why the single radio button would not work the way that you want it to. I will set up a little test case but I really think the issue is that you should be checking the value in the onChange event not the onClick.