[
https://issues.apache.org/jira/browse/WICKET-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220401#comment-17220401
]
ASF subversion and git services commented on WICKET-6839:
---------------------------------------------------------
Commit b127a01582cc4097e40941ca6d57989f614466d1 in wicket's branch
refs/heads/wicket-8.x from Thomas Heigl
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=b127a01 ]
WICKET-6839 Use request flag for caching `isVisibleInHierarchy`
(cherry picked from commit 931c873e84ebefc1cbb96b5b62e94fce3de6fc0b)
> 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
> Fix For: 9.2.0
>
>
> 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)
