[jira] [Updated] (TAP5-1447) ProgressiveDisplay could accept forcing client id property

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

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

Jochen Kemnade updated TAP5-1447:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> 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.2#6252)