You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/03/04 21:05:56 UTC
[jira] Created: (TAP5-553) Tapestry should include a new binding
prefix, "clientId:", that extracts the clientId of a component
Tapestry should include a new binding prefix, "clientId:", that extracts the clientId of a component
----------------------------------------------------------------------------------------------------
Key: TAP5-553
URL: https://issues.apache.org/jira/browse/TAP5-553
Project: Tapestry 5
Issue Type: New Feature
Components: tapestry-core
Affects Versions: 5.1.0.1
Reporter: Howard M. Lewis Ship
It is quite frequently desirable to get a component (that implements ClientElement) and extract the component's clientId property. Currently you have to inject the component into the page to expose it as a property to extract the clientId.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-553) Tapestry should include a new binding
prefix, "clientId:", that extracts the clientId of a component
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-553:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> Tapestry should include a new binding prefix, "clientId:", that extracts the clientId of a component
> ----------------------------------------------------------------------------------------------------
>
> Key: TAP5-553
> URL: https://issues.apache.org/jira/browse/TAP5-553
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> It is quite frequently desirable to get a component (that implements ClientElement) and extract the component's clientId property. Currently you have to inject the component into the page to expose it as a property to extract the clientId.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-553) Tapestry should include a new binding
prefix, "clientId:", that extracts the clientId of a component
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-553.
-------------------------------------
Resolution: Won't Fix
Played around with this for a bit; the problem is that the prime use case (accessing the id of a zone) doesn't work if the zone renders after the component, and that's pretty common. Zones just work better with manually assigned ids.
> Tapestry should include a new binding prefix, "clientId:", that extracts the clientId of a component
> ----------------------------------------------------------------------------------------------------
>
> Key: TAP5-553
> URL: https://issues.apache.org/jira/browse/TAP5-553
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> It is quite frequently desirable to get a component (that implements ClientElement) and extract the component's clientId property. Currently you have to inject the component into the page to expose it as a property to extract the clientId.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-553) Tapestry should include a new binding
prefix, "clientId:", that extracts the clientId of a component
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-553:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> Tapestry should include a new binding prefix, "clientId:", that extracts the clientId of a component
> ----------------------------------------------------------------------------------------------------
>
> Key: TAP5-553
> URL: https://issues.apache.org/jira/browse/TAP5-553
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> It is quite frequently desirable to get a component (that implements ClientElement) and extract the component's clientId property. Currently you have to inject the component into the page to expose it as a property to extract the clientId.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-553) Tapestry should include a new binding
prefix, "clientId:", that extracts the clientId of a component
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-553.
-------------------------------------
Resolution: Won't Fix
Played around with this for a bit; the problem is that the prime use case (accessing the id of a zone) doesn't work if the zone renders after the component, and that's pretty common. Zones just work better with manually assigned ids.
> Tapestry should include a new binding prefix, "clientId:", that extracts the clientId of a component
> ----------------------------------------------------------------------------------------------------
>
> Key: TAP5-553
> URL: https://issues.apache.org/jira/browse/TAP5-553
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> It is quite frequently desirable to get a component (that implements ClientElement) and extract the component's clientId property. Currently you have to inject the component into the page to expose it as a property to extract the clientId.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.