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 2011/09/13 18:59:09 UTC
[jira] [Resolved] (WICKET-4048) label's wicket:for does not work
completely for Radios
[ https://issues.apache.org/jira/browse/WICKET-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-4048.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5.1
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