[jira] [Updated] (TAP5-1975) Tapestry should recognize explicit ids in the template, automatically prevent id collisions

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-1975:
---------------------------------

    Issue Type: Improvement  (was: Bug)

> Tapestry should recognize explicit ids in the template, automatically prevent id collisions
> -------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1975
>                 URL: https://issues.apache.org/jira/browse/TAP5-1975
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> If a template contains markup with a literal id, say <span id="link">, and a component exists with the same component id (think:  <t:mycomponent t:id="link"/>), then the component may render itself using the same id.
> Tapestry should recognize the set of ids defined explicitly be components in the template. During a full-page render, those ids should be pre-allocated to prevent collisions; thus the component would render itself with id="link_0".



--
This message was sent by Atlassian JIRA
(v6.2#6252)