Replacing OnDomReadyHeaderItem with OnLoadHeaderItem (class
DatatablesBehavior) seems to solve your problem. It's likely that your
script (the one from DatatablesBehavior) depends on some other code and
it must wait for it to be loaded before being executed.
Im having a problem with Javascript
Thanks - that seems to confirm the problem - delaying the Datatables JS to
after the Wicket link listeners have executed will fix it, since the errors
are coming from the Wicket Link Listeners not being able to find markup IDs
that the Datatables JS paginates out of view. (load fires after ready
I take some of that back:
In the initial page rendering, the Javascript is ordered as I expect (child
JS then parent JS).
However, in the Ajax update, the Wicket listeners are added *after* the
datatables init call, which results in an out of order sequence.
Why is the Ajax update change the
I logged: https://issues.apache.org/jira/browse/WICKET-5082 and added some
comments with my interpretation of what's going on.
N
On Wed, Mar 6, 2013 at 12:31 PM, Nick Pratt nbpr...@gmail.com wrote:
I take some of that back:
In the initial page rendering, the Javascript is ordered as I expect
