Is there some reason why T5.2.5's form fragment event handlers for Tapestry.CHANGE_VISIBILITY_EVENT and Tapestry.HIDE_AND_REMOVE_EVENT don't call event.stop? Without that, the event continues to propagate and so you can't have nested form fragments, because making the inner fragment invisible will make the outer fragment invisible as well.
I was planning on filing a jira for the issue, but wanted to check first to make sure there wasn't something I was missing? Robert --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
