[
https://issues.apache.org/jira/browse/WICKET-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748665#comment-16748665
]
Michael Gerhards commented on WICKET-6622:
------------------------------------------
This is true but maybe you can use the rising number of linked tickets to
banish wicket:enclosure or make it deprecated for Wicket 9? At least the
official documentation should clearly warn especially new users about the
shortcomings of wicket enclosures. Inline enclosures is also another problem.
> Enclosure Ajax Bug
> ------------------
>
> Key: WICKET-6622
> URL: https://issues.apache.org/jira/browse/WICKET-6622
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 8.2.0
> Reporter: Michael Gerhards
> Priority: Minor
> Attachments: Error Message.PNG, Wicket_Enclosure_Ajax_Bug.zip
>
>
> WICKET AJAX DEBUG produces the error message
> ERROR: Cannot bind a listener for event "inputchange change" on element
> "text1" because the element is not in the DOM
> when component is not visible caused by enclosure:
> HTML
> <wicket:enclosure child="other">
> <input type="text" wicket:id="text"/>
> <div wicket:id="other" />
> </wicket:enclosure>
> JAVA
> other.setVisibilityAllowed(false);
>
> HTML Page source head script contains
> Wicket.Ajax.ajax(\{"u":"./?0-1.0-text","m":"POST","c":"text1","e":"inputchange
> change"});;
> but not text1 since it is invisible.
> See attached source project and screenshot.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
