[
https://issues.apache.org/jira/browse/WICKET-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Meier resolved WICKET-5082.
--------------------------------
Resolution: Fixed
Fix Version/s: 6.7.0
Assignee: Sven Meier
The JavaScript ordering should now be consistent.
> Ajax update renders parent/child JS in different order than initial Page
> render
> -------------------------------------------------------------------------------
>
> Key: WICKET-5082
> URL: https://issues.apache.org/jira/browse/WICKET-5082
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 6.6.0
> Reporter: Nick Pratt
> Assignee: Sven Meier
> Fix For: 6.7.0
>
> Attachments: Change_order_of_Ajax_child_visitation.patch,
> quickstart.tar.gz, wicket-5082.patch
>
>
> See attached quickstart. On initial page load, the child Javascripts are
> rendered and executed first, followed by the parent's JS - in this case a
> Datatables.net JS. Everything works fine.
> However, if you click on a link in the DefaultDataTable, we trigger a DDT
> refresh via Ajax, and then you can see that the parent's JS is executed
> first, before the child JS - this causes a problem since the parent JS
> modifies the visible rows in the table and Wicket can no longer find some of
> the child rows.
> I expected the order of JS contributions to be the same for initial page
> render and any Ajax updates.
--
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
