You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2018/08/30 12:11:00 UTC
[jira] [Resolved] (WICKET-6582) Ajax should prevent components on a
different page from rendering on the current one.
[ https://issues.apache.org/jira/browse/WICKET-6582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Meier resolved WICKET-6582.
--------------------------------
Resolution: Not A Problem
Assignee: Sven Meier
Thanks for your investigation.
> 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
> Assignee: Sven Meier
> 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)