You're welcome. It wasn't a known issue before you found it. I just debugged and logged it.
The benefits of using the label component are: - DRY: a component declares its label once, and the Label refers to it - validation decoration of the resulting label Cheers, Nick. Chris Lewis-5 wrote: > > Nick, thanks for pointing that out and I'm glad to see its a known issue > (hopefully that means a fix is coming). Thanks for your solution, but > I'd rather just use the raw label tag. I'm not entirely sure what the > benefit of using the the label component is to be honest, but it was one > of those thing where I felt like I had to understand what was happening > (I'm new to tap). > Thanks again! > > chris > > Nick Westgate wrote: >> The problem is actually in the Radio component. >> Copy its source to make your own component and apply these changes: >> https://issues.apache.org/jira/browse/TAPESTRY-1709 >> >> Cheers, >> Nick. >> >> >> Chris Lewis wrote: >>> tamseo, >>> >>> Let me amend my last message. I can use <t:label> in the form as long >>> as its not a child of the <t:radiogroup> component! >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/T5%3A-radio%2C-label-tf4276314.html#a12183202 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
