You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Ludwig (JIRA)" <ji...@apache.org> on 2011/04/01 15:35:05 UTC

[jira] [Updated] (WICKET-3586) EnclosureContainer should honor relevantChild.determineVisibility

     [ https://issues.apache.org/jira/browse/WICKET-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sven Ludwig updated WICKET-3586:
--------------------------------

    Affects Version/s: 1.4.17

> 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
>
> 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