You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2009/02/01 08:54:00 UTC
[jira] Assigned: (WICKET-1677)
AjaxFormChoiceComponentUpdatingBehavior affects checkboxes even if
component uses radios and vice-versa
[ https://issues.apache.org/jira/browse/WICKET-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg reassigned WICKET-1677:
-------------------------------------
Assignee: Igor Vaynberg
> AjaxFormChoiceComponentUpdatingBehavior affects checkboxes even if component uses radios and vice-versa
> -------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1677
> URL: https://issues.apache.org/jira/browse/WICKET-1677
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.3
> Reporter: Willis Blackburn
> Assignee: Igor Vaynberg
> Attachments: AjaxFormChoiceComponentUpdatingBehavior.patch
>
>
> I have a form with two radio buttons. Depending which radio the user selects, I show one form or another form. I'm using an AjaxFormChoiceComponentUpdatingBehavior attached to the RadioGroup. One of the forms has a checkbox. The checkbox triggers an ajax update--even though the AjaxFormChoiceComponentUpdatingBehavior is attached to a RadioGroup. AjaxFormChoiceComponentUpdatingBehavior should only affect the appropriate controls based on whether it is attached to a choice component that uses radios or checkboxes. If a developer really wants both, then he can use two AjaxFormChoiceComponentUpdatingBehavior instances.
> I've attached a patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.