[
https://issues.apache.org/jira/browse/WICKET-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103754#comment-13103754
]
Igor Vaynberg edited comment on WICKET-4048 at 9/13/11 5:00 PM:
----------------------------------------------------------------
it doesnt really make sense to transfer required and error classes to the
labels of the radios themselves, these are only relevant for the label of the
radiogroup. i did, however, make it so that individual radio labels will get
the 'disabled' class if the radio component itself is disabled.
was (Author: ivaynberg):
it doesnt really make sense to transfer required and error classes to the
labels of the radios themselves, these are only relevant for the label of the
radiogroup. i did, however, made it so that individual radio labels will get
the 'disabled' class if the radio component itself is disabled.
> label's wicket:for does not work completely for Radios
> ------------------------------------------------------
>
> Key: WICKET-4048
> URL: https://issues.apache.org/jira/browse/WICKET-4048
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC7
> Reporter: Matthias Keller
> Assignee: Igor Vaynberg
> Fix For: 1.5.1
>
>
> The new functionality with <label wicket:for="..."> (See WICKET-1469) does
> not work completely for radio buttons, probably because the referenced Radio
> instance is no FormComponent but just a LabeledWebmarkupContainer.
> The problem is in AutoLabelResolver, line 181:
> if (component instanceof FormComponent) {...}
> There should be a special case for Radios to get its associated RadioGroup
> first and use that as component to derive the CSS class from
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
