[
https://issues.apache.org/jira/browse/WICKET-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004565#comment-14004565
]
Rudi Wijaya commented on WICKET-4874:
-------------------------------------
I also got hit by this bug (actually WICKET-5214: ignored unrendered
components) and spent some time being confused about this behavior.
I agree with [~aditsu]'s suggestion that any use of {{<wicket:enclosure>}}
should log a {{WARN}} and mention this ticket (WICKET-4874 / WICKET-5214) and
also suggesting {{EnclosureContainer}} instead.
And hopefully {{<wicket:enclosure>}} is removed from Wicket 7.0 because it's
harmful to "support" a feature with problematic/unpredictable behavior.
> "Cannot find element with id" error seen in Ajax Debug for child of
> wicket:enclosure
> ------------------------------------------------------------------------------------
>
> Key: WICKET-4874
> URL: https://issues.apache.org/jira/browse/WICKET-4874
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.3.0
> Environment: Windows 7 x64 Java 1.6.0_32
> Reporter: Jesse Bonzo
> Assignee: Igor Vaynberg
> Priority: Minor
> Labels: ajax, enclosure, javascript
> Fix For: 7.0.0-M1
>
> Attachments: WicketQuickStart.zip
>
>
> When an AjaxLink is hidden due to being a child of a wicket:enclosure an
> error is seen in the Ajax Debug window. It seems like the event handler is
> expecting the AjaxLink to exist in the DOM even though it has been hidden.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
