You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "David Rain (Jira)" <ji...@apache.org> on 2026/02/02 11:52:00 UTC
[jira] [Created] (WICKET-7175) wicket:enclosure attribute - "Component with id ... was not found" when inner component hidden
David Rain created WICKET-7175:
----------------------------------
Summary: wicket:enclosure attribute - "Component with id ... was not found" when inner component hidden
Key: WICKET-7175
URL: https://issues.apache.org/jira/browse/WICKET-7175
Project: Wicket
Issue Type: Bug
Components: wicket-core
Affects Versions: 8.17.0
Environment: Wicket 8.17.0 either Linux or Windows - doesn't matter
Reporter: David Rain
If visibility of a component inside a tag with wicket:enclosure attribute is changed from false to true (determined by isVisible) then an javascript error is reported in the Wicket Ajax Debug window (and also in the console).
It seems that the updated component is included 2x in the AJAX re-paint response. Once alone and second surrounded by the enclosure element.
I don't know if this has been a known bug on wicket:enclosure attribute? Or if enclosures had been completely abandoned? We're still running Wicket 8 because of JDK8 compatibily.
I can of course provide a quick start if someone is to bother with this bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)