[WICKET-3586] EnclosureContainer should honor relevantChild.determineVisibility

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.16, 1.4.17
• Fix Version/s: 1.4.18, 1.5-RC3
• Component/s: wicket
• Labels: core visibility
• Assignee: Juegen Donnerstag
• Reporter: Sven Ludwig
• Created: 01/Apr/11 13:31
• Updated: 09/Apr/11 13:36
• Resolved: 09/Apr/11 13:36

Description

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.