[ https://issues.apache.org/jira/browse/WICKET-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993559#comment-12993559 ]
Hudson commented on WICKET-3436: -------------------------------- Integrated in Apache Wicket 1.4.x #429 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/429/]) WICKET-3436 OnChangeAjaxBehavior can render javascript before wicket-ajax.js is loaded Update the test expectation > OnChangeAjaxBehavior can render javascript before wicket-ajax.js is loaded > -------------------------------------------------------------------------- > > Key: WICKET-3436 > URL: https://issues.apache.org/jira/browse/WICKET-3436 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 1.4.15 > Reporter: Alexander Morozov > Assignee: Martin Grigorov > Priority: Minor > Labels: javascript > Fix For: 1.4.16, 1.5-RC2 > > Attachments: fix-WICKET-3436.patch > > > In the current OnChangeAjaxBehavior implementation, the behavior renders > javascript (Wicket.ChangeHandler) > within the onComponentRendered() method directly to the response. Its okay in > case, when wicket-ajax.js is rendered in the head of the page, but if we move > javascript to the footer of the page, the inlined javascript will be broken. > I think, the javascript have to be evaluated after the DOM is built. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira