Another user asked the same question so I added it to my demo app: https://github.com/martin-g/blogs/commit/d5a248a3a3d5369c9cdc66604eba384428e9d0a0
On Tue, Mar 19, 2013 at 9:31 PM, Martin Grigorov <[email protected]>wrote: > Actually I think it is possible to have them on the top. > All "entries" from <wicket:head> are handled by PageHeaderItem at runtime. > So you can use custom FilteringHeaderResponse that lifts PageHeaderItem to > PriorityHeaderItem. > > > On Tue, Mar 19, 2013 at 7:42 PM, Guillaume Smet > <[email protected]>wrote: > >> Hi, >> >> On Tue, Mar 19, 2013 at 2:07 PM, Martin Grigorov <[email protected]> >> wrote: >> > You can use StringHeaderItem.forString("<meta ...>") and wrap it in >> > PriotityHeaderItem/FilterHeaderItem if needed. >> >> We had the same question. Starting with Wicket 6, <title> and so on >> are lost in the resources lines. It was quite nice to have them on top >> of the <head> and the resources at the bottom of the <head>, >> especially when a customer starts to look at the HTML produced. >> >> I'm not sure having all these tags in the Java code is a good solution >> for this issue. >> >> It's mostly cosmetic so it's probably not worth spending too much time >> on this but if there is an easy solution for this issue, it might be >> worth it. >> >> -- >> Guillaume >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com <http://jweekend.com/> > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
