[ https://issues.apache.org/jira/browse/TAP5-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-1447. -------------------------------- Resolution: Invalid We assume this is no longer relevant and therefore close it. If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen. > ProgressiveDisplay could accept forcing client id property > ---------------------------------------------------------- > > Key: TAP5-1447 > URL: https://issues.apache.org/jira/browse/TAP5-1447 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core > Affects Versions: 5.2 > Reporter: Raul Montes > Priority: Minor > Labels: bulk-close-candidate > > ProgressiveDisplay component could have similar behaviour to Zone component > about forcing the id attribute. So, instead of setting clientId like: > String clientId = jsSupport.allocateClientId(resources); > It could be like Zone does: > clientId = resources.isBound("id") ? idParameter : > javascriptSupport.allocateClientId(resources); > Since ProgressiveDisplay also creates a containing div (or other element) in > the final markup, it is useful when you need to have related CSS or JS code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)