You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Leonardo Quijano Vincenzi (JIRA)" <ta...@jakarta.apache.org> on 2006/06/07 06:29:29 UTC
[jira] Created: (TAPESTRY-983) Allow Radio components id overriding
Allow Radio components id overriding
------------------------------------
Key: TAPESTRY-983
URL: http://issues.apache.org/jira/browse/TAPESTRY-983
Project: Tapestry
Type: Improvement
Components: Framework
Versions: 4.0.2
Reporter: Leonardo Quijano Vincenzi
Priority: Minor
The Radio buttons generates a client-side id to be used by javascript functions. This can't be overridden using the "id" parameter of @Radio, limiting the use of custom javascript functions on those components. When specifying a custom id, it renders as an informal parameter. We end up with 2 ids on the same component (the one generated by Tapestry and the one as an informal parameter).
This id could be made a formal parameter for more flexibility, or at least it should be reserved to prevent confusions.
--
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
Re: [jira] Created: (TAPESTRY-983) Allow Radio components id overriding
Posted by Leonardo Quijano Vincenzi <le...@dtqsoftware.com>.
Leonardo Quijano Vincenzi (JIRA) wrote:
> Allow Radio components id overriding
> ------------------------------------
>
> Key: TAPESTRY-983
> URL: http://issues.apache.org/jira/browse/TAPESTRY-983
> Project: Tapestry
> Type: Improvement
>
> Components: Framework
> Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Priority: Minor
>
>
> The Radio buttons generates a client-side id to be used by javascript functions. This can't be overridden using the "id" parameter of @Radio, limiting the use of custom javascript functions on those components. When specifying a custom id, it renders as an informal parameter. We end up with 2 ids on the same component (the one generated by Tapestry and the one as an informal parameter).
>
> This id could be made a formal parameter for more flexibility, or at least it should be reserved to prevent confusions.
>
>
>
Any chance of having this small fix for 4.0.3 ?
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Web Application Design and Programming
http://www.dtqsoftware.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-983) Allow Radio components id
overriding
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-983?page=all ]
Jesse Kuhnert reassigned TAPESTRY-983:
--------------------------------------
Assignee: Jesse Kuhnert
> Allow Radio components id overriding
> ------------------------------------
>
> Key: TAPESTRY-983
> URL: http://issues.apache.org/jira/browse/TAPESTRY-983
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Assigned To: Jesse Kuhnert
> Priority: Minor
>
> The Radio buttons generates a client-side id to be used by javascript functions. This can't be overridden using the "id" parameter of @Radio, limiting the use of custom javascript functions on those components. When specifying a custom id, it renders as an informal parameter. We end up with 2 ids on the same component (the one generated by Tapestry and the one as an informal parameter).
> This id could be made a formal parameter for more flexibility, or at least it should be reserved to prevent confusions.
--
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] Resolved: (TAPESTRY-983) Allow Radio components id
overriding
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-983?page=all ]
Jesse Kuhnert resolved TAPESTRY-983.
------------------------------------
Fix Version/s: 4.1.1
Resolution: Fixed
> Allow Radio components id overriding
> ------------------------------------
>
> Key: TAPESTRY-983
> URL: http://issues.apache.org/jira/browse/TAPESTRY-983
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Assigned To: Jesse Kuhnert
> Priority: Minor
> Fix For: 4.1.1
>
>
> The Radio buttons generates a client-side id to be used by javascript functions. This can't be overridden using the "id" parameter of @Radio, limiting the use of custom javascript functions on those components. When specifying a custom id, it renders as an informal parameter. We end up with 2 ids on the same component (the one generated by Tapestry and the one as an informal parameter).
> This id could be made a formal parameter for more flexibility, or at least it should be reserved to prevent confusions.
--
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] Commented: (TAPESTRY-983) Allow Radio components id
overriding
Posted by "Leonardo Quijano Vincenzi (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-983?page=comments#action_12415088 ]
Leonardo Quijano Vincenzi commented on TAPESTRY-983:
----------------------------------------------------
I forgot I was using Tacos version of @Radio. Anyway, this applies here, too.
> Allow Radio components id overriding
> ------------------------------------
>
> Key: TAPESTRY-983
> URL: http://issues.apache.org/jira/browse/TAPESTRY-983
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Priority: Minor
>
> The Radio buttons generates a client-side id to be used by javascript functions. This can't be overridden using the "id" parameter of @Radio, limiting the use of custom javascript functions on those components. When specifying a custom id, it renders as an informal parameter. We end up with 2 ids on the same component (the one generated by Tapestry and the one as an informal parameter).
> This id could be made a formal parameter for more flexibility, or at least it should be reserved to prevent confusions.
--
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