[
https://issues.apache.org/jira/browse/TAP5-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989520#comment-14989520
]
Jochen Kemnade commented on TAP5-2509:
--------------------------------------
Well, TAP5-2500 did not force the change. I just assumed that the usual use
case for the Label component is to be able to render a label for a field and to
expect the label to have the correct {{for}} attribute. If the client ID is
null, we cannot render a proper {{for}} attribute and instead of producing a
potentially undesired result (label *without* for attribute), we should tell
the user that there is a problem. Maybe we should rather log a warning than
throw an exception.
> Regression with radiogroup label in 5.4-beta-37
> -----------------------------------------------
>
> Key: TAP5-2509
> URL: https://issues.apache.org/jira/browse/TAP5-2509
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.4
> Reporter: Chris Poulsen
> Attachments: t54-radiogrouplabel.zip
>
>
> Having a label for a radio group fails in 5.4 beta 37, while it works up
> until beta-36.
> The error is:
> Render queue error in AfterRender[Index:form]: The field has returned a null
> client-side ID
> See the attached project for an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
