You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Andrea Del Bene (JIRA)" <ji...@apache.org> on 2012/11/28 11:56:58 UTC
[jira] [Commented] (WICKET-4874) "Cannot find element with id"
error seen in Ajax Debug for child of wicket:enclosure
[ https://issues.apache.org/jira/browse/WICKET-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505362#comment-13505362 ]
Andrea Del Bene commented on WICKET-4874:
-----------------------------------------
I think the problem is due to the adoption in Wicket 6 of browser event registration in place of inline events. Now the AJAX behaviour tries to register the ajax handler for the given component but it fails as the component is not rendered (is inside wicket:enclosure ) and at the same time is visible in hierachy. I didn't find a solution yet.
> "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
> Priority: Minor
> Labels: ajax, enclosure, javascript
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira