[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053482#comment-13053482 ]
Hudson commented on TAP5-1551: ------------------------------ Integrated in tapestry-trunk-freestyle #378 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/378/]) > FormFragment change visibility/hide and remove event listeners should call > event.stop() to prevent container fragments from also being hidden > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TAP5-1551 > URL: https://issues.apache.org/jira/browse/TAP5-1551 > Project: Tapestry 5 > Issue Type: Bug > Affects Versions: 5.3.0, 5.2.5 > Reporter: Robert Zeigler > Assignee: Robert Zeigler > Fix For: 5.3.1, 5.2.6 > > > In 5.2.x, FormFragment switched from using direct calls to a "setVisible" > function on the fragment to using an event-based approach where the fragment > element listens for the Tapestry.CHANGE_VISIBILITY_EVENT or the > Tapestry.HIDE_AND_REMOVE_EVENT. The current implementation, however, does > not allow for nesting form fragments because the event listeners do not call > event.stop(), so the event continues to propagate, so hiding an "inner" form > fragment hides the outer form fragment, as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira