[
https://issues.apache.org/jira/browse/WICKET-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219689#comment-17219689
]
ASF subversion and git services commented on WICKET-6839:
---------------------------------------------------------
Commit 50a551423700be3c3604e0a2ce3604186f10e144 in wicket's branch
refs/heads/master from Thomas Heigl
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=50a5514 ]
Merge pull request #459 from theigl/WICKET-6839-visible-hierarchy-cache
WICKET-6839 Use request flag for caching `isVisibleInHierarchy`
> Component visible-in-hierarchy cache not used but cleared
> ---------------------------------------------------------
>
> Key: WICKET-6839
> URL: https://issues.apache.org/jira/browse/WICKET-6839
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 9.0.0, 8.9.0
> Reporter: Tobias Haupt
> Assignee: Thomas Heigl
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
