[
https://issues.apache.org/jira/browse/WICKET-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723509#comment-17723509
]
Martin Tzvetanov Grigorov commented on WICKET-7057:
---------------------------------------------------
The epic ticket is WICKET-4874
It has a link to the discussion (from 2013!) about deprecating
<wicket:enclosure>
No one has worked on improving <wicket:enclosure> (and auto-components in
general) since 2013, so don't expect that anything will be improved in this
area.
> header not rendered for components whithin enclosure in ajax response
> ---------------------------------------------------------------------
>
> Key: WICKET-7057
> URL: https://issues.apache.org/jira/browse/WICKET-7057
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 9.13.0
> Reporter: Palancher aurélien
> Priority: Major
> Attachments: callstack1.png, callstack2.png, myproject.zip
>
>
> Ajax response doesn't contain the binding of events
> (Wicket.Ajax.ajax({"u":...) of components while they are positionned within
> an enclosure.
> With the following code :
> ```
> <div wicket:enclosure="mylink">
> <a wicket:id="mylink"></a>
> <label wicket:id="mylabel"></label>
> <a wicket:id="myotherlink"></a>
> </div>
> ```
> When you click on *mylink* to refresh *mylabel*, wicket refreshes the
> enclosure tag, and call renderhead of behaviors of enclosure and *mylink*
> only, so *myotherlink* event is not bound
> It can be reproduced in the quickstart.
> I've also joined some pictures of the callstack to find easily where is the
> problem
> I don't know if other versions are affected
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
