[
https://issues.apache.org/jira/browse/WICKET-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094391#comment-13094391
]
Martin Grigorov commented on WICKET-4000:
-----------------------------------------
The order from 1.4 is still possible. See
org.apache.wicket.markup.renderStrategy.AbstractHeaderRenderStrategy.get().
For Wicket.next we will consider making it easier for the application developer
to specify the contribution order. But I can see how this can be problematic
for component libraries.
With the current approach (child first) the components contribute their js/css
and the page can override them. This is also what you are trying to so, right ?
> 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: 1.6.0
>
> Attachments: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
