[
https://issues.apache.org/jira/browse/WICKET-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emond Papegaaij updated WICKET-4000:
------------------------------------
Attachment: 0001-WICKET-4000-render-all-headers-through-IHeaderRespon.patch
With this patch, all header rendering is done by IHeaderResponse from within
the HeaderRenderStrategy. Some tests are failing now, because the order
changed, but I think the order defined in these testcases is wrong.
> Header contributions order is not stable
> ----------------------------------------
>
> Key: WICKET-4000
> URL: https://issues.apache.org/jira/browse/WICKET-4000
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC6
> Reporter: Sylvain Vieujot
> Fix For: 6.0.0
>
> Attachments:
> 0001-WICKET-4000-render-all-headers-through-IHeaderRespon.patch,
> quickstart-scriptsOrder.zip
>
>
> In the last RCs, I started to experience problems with the contributions
> order.
> For example, I add jQuery, and until 1.5RC5, it worked well, but now the call
> to the jQuery script has been moved to the bottom of the page head, and this
> disables all my other scripts that are expecting jQuery's $ to be defined.
> I attach a quickstart to demonstrate the problem.
> Maybe the order in the quickstart is not the expected one, but what it shows
> is that the order does not make real sense (at least to me) :
> In the quickstart, the wicket:head tag contributions are in the order 3 - 8 -
> 9 - 5, and the renderHead methods contributions are in the order 4 - 1 - 2 -
> 6 - 7.
--
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
