You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Robert Zeigler (JIRA)" <ji...@apache.org> on 2011/06/18 08:03:47 UTC
[jira] [Created] (TAP5-1551) FormFragment change visibility/hide
and remove event listeners should call event.stop() to prevent container
fragments from also being hidden
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.2.5, 5.3.0
Reporter: Robert Zeigler
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
[jira] [Commented] (TAP5-1551) FormFragment change visibility/hide
and remove event listeners should call event.stop() to prevent container
fragments from also being hidden
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Closed] (TAP5-1551) FormFragment change visibility/hide and
remove event listeners should call event.stop() to prevent container
fragments from also being hidden
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler closed TAP5-1551.
--------------------------------
> 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
[jira] [Assigned] (TAP5-1551) FormFragment change visibility/hide
and remove event listeners should call event.stop() to prevent container
fragments from also being hidden
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler reassigned TAP5-1551:
------------------------------------
Assignee: Robert Zeigler
> 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
>
> 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
[jira] [Assigned] (TAP5-1551) FormFragment change visibility/hide
and remove event listeners should call event.stop() to prevent container
fragments from also being hidden
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler reassigned TAP5-1551:
------------------------------------
Assignee: Robert Zeigler
> 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
>
> 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
[jira] [Resolved] (TAP5-1551) FormFragment change visibility/hide
and remove event listeners should call event.stop() to prevent container
fragments from also being hidden
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler resolved TAP5-1551.
----------------------------------
Resolution: Fixed
Fix Version/s: 5.2.6
5.3.1
> 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
[jira] [Closed] (TAP5-1551) FormFragment change visibility/hide and
remove event listeners should call event.stop() to prevent container
fragments from also being hidden
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler closed TAP5-1551.
--------------------------------
> 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
[jira] [Commented] (TAP5-1551) FormFragment change visibility/hide
and remove event listeners should call event.stop() to prevent container
fragments from also being hidden
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (TAP5-1551) FormFragment change visibility/hide
and remove event listeners should call event.stop() to prevent container
fragments from also being hidden
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler resolved TAP5-1551.
----------------------------------
Resolution: Fixed
Fix Version/s: 5.2.6
5.3.1
> 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