Well no. It would only solve my problem. How selfish of me to propose something like that ;-)
I felt so sorry this morning that I have searched for a real solution to Michaels problem, and guess what I found it. All that needs to be done is add something similar to this at the end of the child page constructor: add(HeaderContributor.forCss(MyChildPage.class, "MyChildCSS.css")); I have tested it and the result is that the link to MyChildCSS.css is the very last item in the <head> of the rendered page. And it even can be used to solve my case :-) The limitation is that it only works for Wicket 1.2. It should also be possible for the other versions but then Michael should have a look at Eelco's blog about header contributions: http://chillenious.wordpress.com/2006/05/03/wicket-header-contributions-with-behaviors/ -- View this message in context: http://www.nabble.com/header-contribution-ordering-t1768566.html#a4878920 Sent from the Wicket - User forum at Nabble.com. _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
