[
https://issues.apache.org/jira/browse/WICKET-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759521#comment-16759521
]
Martin Grigorov commented on WICKET-6622:
-----------------------------------------
bq. isVisibilityAllowed is usually used for authorization
I think isRenderAllowed() is the one used for authorization:
https://github.com/apache/wicket/blob/07c36ce6852737b7a468a240053126c1605a4460/wicket-core/src/main/java/org/apache/wicket/Component.java#L4279-L4282
bq. what if that flag is changed after the enclosure's onConfigure()?
I still haven't had time to debug the tests but I am also not fully certain in
my idea here.
bq. What If we unified resolvers with queued components
I am a noobie here. The queued components code added a lot of complexity and
bugs, and I try to avoid them.
> 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)
