You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org> on 2005/12/18 13:46:35 UTC
[jira] Created: (TAPESTRY-810) Radio components don't have unique client id's
Radio components don't have unique client id's
----------------------------------------------
Key: TAPESTRY-810
URL: http://issues.apache.org/jira/browse/TAPESTRY-810
Project: Tapestry
Type: Improvement
Components: Framework
Environment: any
Reporter: Jesse Kuhnert
Assigned to: Jesse Kuhnert
Fix For: 4.0.1
Because Radio components don't generate id="" html attributes, it becomes almost impossible to do standard client side interactions with them. An easy fix would generate unique id's based on the option value + groupname for the unique id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Resolved: (TAPESTRY-810) Radio components don't have unique
client id's
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-810?page=all ]
Jesse Kuhnert resolved TAPESTRY-810.
------------------------------------
Resolution: Fixed
> Radio components don't have unique client id's
> ----------------------------------------------
>
> Key: TAPESTRY-810
> URL: http://issues.apache.org/jira/browse/TAPESTRY-810
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Environment: any
> Reporter: Jesse Kuhnert
> Assigned To: Jesse Kuhnert
> Fix For: 4.1
>
>
> Because Radio components don't generate id="" html attributes, it becomes almost impossible to do standard client side interactions with them. An easy fix would generate unique id's based on the option value + groupname for the unique id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-810) Radio components don't have unique
client id's
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-810?page=all ]
Jesse Kuhnert updated TAPESTRY-810:
-----------------------------------
Fix Version: 4.1
(was: 4.0.1)
> Radio components don't have unique client id's
> ----------------------------------------------
>
> Key: TAPESTRY-810
> URL: http://issues.apache.org/jira/browse/TAPESTRY-810
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Environment: any
> Reporter: Jesse Kuhnert
> Assignee: Jesse Kuhnert
> Fix For: 4.1
>
> Because Radio components don't generate id="" html attributes, it becomes almost impossible to do standard client side interactions with them. An easy fix would generate unique id's based on the option value + groupname for the unique id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org