[
https://issues.apache.org/jira/browse/TAP5-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954579#comment-14954579
]
Chris Poulsen commented on TAP5-2509:
-------------------------------------
After looking into this I think that using a plain <label> with the necessary
styling is the correct solution.
It seems like it is the fact that t:radiogroup behaves like a field, that trips
up things. The "pre beta-37" behavior renders the label without "for" AFAICS.
This does not make it correct to use a t:label for a radio group, but it makes
it look like it works.
I wonder if making the RadioGroup.getClientId method fail harder than just
always returning null, could help users identify the situation? (An
exception+as much info as possible)
> 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)
