Any update on this bug?
It seems the problem appeared after
http://issues.apache.org/jira/browse/TAPESTRY-810 was fixed.
The problem is also described in
http://issues.apache.org/jira/browse/TAPESTRY-983, although I don't think it
affects version 4.0.2, as stated, but rather 4.1.x only.
If I may r
User-supplied id attributes in @Radio components are not rendered properly
in Tap4.1. Both the user-supplied id and a RadioGroup id are rendered:
This was working fine with Tap4.0.2
Ch.
2006/9/15, andyhot <[EMAIL PROTECTED]>:
They are in a group. They are supposed to have the same name.
If
J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-Original Message-
From: andyhot [mailto:[EMAIL PROTECTED]
Sent: Fri 9/15/2006 1:51 AM
To: Tapestry users
Subject: Re: RadioGroup component
They are in a group. They are supposed to have the same name.
If you supply an 'id' parameter for each, you can use
document.getElementById() later on.
Peter Dawn wrote:
> sorry guys incomplete message, am sending it again,
>
> how can i reference each radio element within a radiogroup. if my
> i
sorry guys incomplete message, am sending it again,
how can i reference each radio element within a radiogroup. if my
implementation is this,
how can i name each individual radio elements. if i use [EMAIL PROTECTED],
the name is still RadioGroup and if use [EMAIL PROTECTED] the individual
ra
