[WICKET-6839] Component visible-in-hierarchy cache not used but cleared

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 9.0.0, 8.9.0
• Fix Version/s: 9.2.0, 8.11.0
• Component/s: wicket-core
• Assignee: Thomas Heigl
• Reporter: Tobias Haupt
• Created: 06/Oct/20 09:59
• Updated: 27/Jan/21 12:47
• Resolved: 23/Oct/20 13:46

Description

When the visibility of a component is changed via setVisible(), the Component and especially the MarkupContainer clears a cache flag (RFLAG_VISIBLE_IN_HIERARCHY_SET) on all contained components.

Unlike the flag for isEnabledInHiearchy (RFLAG_ENABLED_IN_HIERARCHY_SET), the flag for visibility seems not to be updated and used in isVisibleInHiearchy.

Resolution: either use the cache or avoid the (expensive) clearance for all children.

Issue Links

• is related to: WICKET-6863 Method Component.setVisibilityAllowed should call onVisibleStateChanged()