You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Thijs Vonk (JIRA)" <ji...@apache.org> on 2012/10/02 20:19:07 UTC
[jira] [Comment Edited] (WICKET-4769) Clicking on Label of Radio
doesn't update component with Ajax update
[ https://issues.apache.org/jira/browse/WICKET-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467917#comment-13467917 ]
Thijs Vonk edited comment on WICKET-4769 at 10/3/12 5:17 AM:
-------------------------------------------------------------
The repainting of the dom doesn't trigger the second event.
When you click on the label 2 click events are fired. If you click on the radio button there is only one event.
See the attached html file demonstrating the issue.
This causes the ajax request to happen twice, with all kinds of weird side effects.
some extra info: http://bugs.jquery.com/ticket/10673
was (Author: thyzz):
The repainting of the dom doesn't trigger the second event.
When you click on the label 2 click events are fired. If you click on the radio button there is only one event.
See the attached html file demonstrating the issue.
This causes the ajax request to happen twice, with all kinds of weird side effects.
> Clicking on Label of Radio doesn't update component with Ajax update
> --------------------------------------------------------------------
>
> Key: WICKET-4769
> URL: https://issues.apache.org/jira/browse/WICKET-4769
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.0.0
> Reporter: Thijs Vonk
> Assignee: Martin Grigorov
> Fix For: 6.2.0
>
> Attachments: radio-choice-bug-6.0.0.tar, radio-label.html, test14.zip, test.zip
>
>
> We just upgraded a application from wicket 1.4 to wicket 6.
> We discovered that when clicking on the label of a radio button that has a AjaxFormChoiceComponentUpdatingBehavior attached the radio is not selected.
> I'll attach 2 testcases (one for wicket 1.4 and one for wicket 6)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira