[
https://issues.apache.org/jira/browse/WICKET-6582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596287#comment-16596287
]
Jezza commented on WICKET-6582:
-------------------------------
I have temporarily worked around it:
`insert.setParent((MarkupContainer) handler.getPage());`
We basically just set the parent to be the page, so when the target goes to
compare all is well.
But that feels a bit...
Yeah...
> Ajax should prevent components on a different page from rendering on the
> current one.
> -------------------------------------------------------------------------------------
>
> Key: WICKET-6582
> URL: https://issues.apache.org/jira/browse/WICKET-6582
> Project: Wicket
> Issue Type: Improvement
> Reporter: Jezza
> Priority: Major
>
> Heyo, we've just updated to Wicket 8, and run head first into WICKET-6140.
> The problem is that we use this behaviour to generate components without a
> page, and then render them into place using ajax.
> I think a better solution would be to only verify the page iff the component
> is on a page.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
