event="click" breaks p:ajax for p:selectOneRadio (3.0.RC2)

[smithh032772]

Please refer to my post in another discussion. Please read my response instead of the title of the topic. Feel free to read the rest of the discussion to see how we arrived to this conclusion.

viewtopic.php?f=3&t=15257&p=52027#p52020

This has been added to Issue Tracker as Issue 3156.

[Oleg]

click is a valid event for any component actually. I can't see any reason to exclude it from p:selectOneRadio. That would means a limitation.

[KingdomHeart]

@Oleg: maybe you can drop a comment on the issue report. That might change Cagatay opinion.

[Oleg]

What comment? I can't see my comment. Cagatay normally drops undesirable comments self. The problem is not in the comment, comment was ok.

[cagatay.civici]

That might change Catay opinion.

What is Catay?

[Oleg]

What is Catay?

Catay is probably second (or third?) developer of PrimeFaces. Can you ask him please to change his opinion?

[tandraschko]

What about Caga? Maybe he can fix it

[cagatay.civici]

There is nothing to fix, use onchange.

[Oleg]

I don't want onchange. I would like to click on the same radio button multiply times and see Ajax requests. onchange will not be fired if you click on an already selected radio button.

Imagine, radio button should behaves like command component. This is my trigger to update page area(s). If you click on command button, an Ajax request is sent, something gets updated. If you click on an already selected radio button, nothing happens. They looks different, but apart from UI appearance they should behave identical. Without ajaxified onclick, you have to click another button and then again the last one in order to trigger onchange.

P.S. It doesn't matter for me, I don't use p:selectOneRadio and similar ones (native controls looks good enough on modern OS). This is just a discussion for everybody. We would like to find the right way and make PrimeFaces better.