[
https://issues.apache.org/jira/browse/WICKET-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juergen Donnerstag resolved WICKET-3586.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC3
1.4.18
thanks
> EnclosureContainer should honor relevantChild.determineVisibility
> -----------------------------------------------------------------
>
> Key: WICKET-3586
> URL: https://issues.apache.org/jira/browse/WICKET-3586
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.4.16, 1.4.17
> Reporter: Sven Ludwig
> Assignee: Juergen Donnerstag
> Labels: core, visibility
> Fix For: 1.4.18, 1.5-RC3
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> The EnclosureContainer calls isVisible() on the relevant child Component to
> determine whether the content should be visible or not.
> However, in the Component API, visibility is not only defined by isVisible().
> There are also the methods isVisibilityAllowed() and isRenderAllowed(). The
> method determineVisibility() is a summary and yields the overall result
> whether a Component should be visible or not.
> The EnclosureContainer should honor relevantChild.determineVisibility().
> In our project a problem occurs because on the relevantChild, we use
> setVisibilityAllowed(false) to make it invisible, but the EnclosureContainer,
> or should I say its other contents, remain visible, which we did not expect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
