[jira] [Commented] (TAP5-2020) Tree label block should be rendered inside an heartbeat
[ https://issues.apache.org/jira/browse/TAP5-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111504#comment-14111504 ] ASF subversion and git services commented on TAP5-2020: --- Commit 89836426940a91bb140627743407326fbebee143 in tapestry-5's branch refs/heads/master from [~hlship] [ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=8983642 ] TAP5-2020: Tree label block should be rendered inside an heartbeat Tree label block should be rendered inside an heartbeat --- Key: TAP5-2020 URL: https://issues.apache.org/jira/browse/TAP5-2020 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3.4 Reporter: Nicolas Bouillon Labels: patch Fix For: 5.4 Attachments: Tree.java.diff Unlike the loop component, the tree component doesn't render the label block inside an heartbeat. So, if a form with a zone target is defined as the label parameter of the tree, the clientId of the last generated form element is used as the linkId for each form element contained in the tree. Sample project available at https://github.com/bouil/tapestry-tree-test Live testable at http://tapestry-tree-test.cloudfoundry.com/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TAP5-2020) Tree label block should be rendered inside an heartbeat
[ https://issues.apache.org/jira/browse/TAP5-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111584#comment-14111584 ] Hudson commented on TAP5-2020: -- SUCCESS: Integrated in tapestry-trunk-freestyle #1308 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1308/]) TAP5-2020: Tree label block should be rendered inside an heartbeat (hlship: rev 89836426940a91bb140627743407326fbebee143) * tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Tree.java Tree label block should be rendered inside an heartbeat --- Key: TAP5-2020 URL: https://issues.apache.org/jira/browse/TAP5-2020 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3.4 Reporter: Nicolas Bouillon Assignee: Howard M. Lewis Ship Labels: patch Fix For: 5.4 Attachments: Tree.java.diff Unlike the loop component, the tree component doesn't render the label block inside an heartbeat. So, if a form with a zone target is defined as the label parameter of the tree, the clientId of the last generated form element is used as the linkId for each form element contained in the tree. Sample project available at https://github.com/bouil/tapestry-tree-test Live testable at http://tapestry-tree-test.cloudfoundry.com/ -- This message was sent by Atlassian JIRA (v6.2#6252)
