You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/06 09:28:57 UTC
[jira] [Resolved] (WICKET-4440)
JavaScriptFilteredIntoFooterHeaderResponse breaks Javascript Order
[ https://issues.apache.org/jira/browse/WICKET-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4440.
-------------------------------------
Resolution: Not A Problem
This is fixed in 1.5.4
> JavaScriptFilteredIntoFooterHeaderResponse breaks Javascript Order
> ------------------------------------------------------------------
>
> Key: WICKET-4440
> URL: https://issues.apache.org/jira/browse/WICKET-4440
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.3
> Reporter: Michael Frankerl
>
> When using {{JavaScriptFilteredIntoFooterHeaderResponse}} the order of aggregated javascript/resources is broken.
> This causes the script error {{Uncaught ReferenceError: Wicket is not defined}} in the resulting page.
> While scripts added with {{renderJavaScriptReference}} reside in the footer bucket, scripts added with {{renderJavaScript}} are in the {{<head>}}.
> See {{AbstractDefaultAjaxBehavior.renderHead}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira