Hi Jesse, I have forgotten about this discussion... Please create a ticket and we will try to implement it. Thanks!
Martin Grigorov Wicket Training and Consulting On Fri, Mar 7, 2014 at 11:35 AM, Jesse Long <[email protected]> wrote: > Hi Martin, > > Any news about the feature discussed below? At the time I thought it was a > good idea, and today I have a perfect use case for it. Is it still planned? > > Thanks, > Jesse > > > On 19/04/2013 16:43, Sven Meier wrote: > >> My idea was to support <wicket:header-items/> only in <head>. >>> >> >> Ok, understood. >> >> Sven >> >> On 04/19/2013 03:21 PM, Martin Grigorov wrote: >> >>> Usually the markup of a page should have only <head>. If there is none >>> then >>> Wicket creates one automatically. >>> <wicket:head> should be used only in children pages (markup inheritance) >>> and in panels. >>> >>> My idea was to support <wicket:header-items/> only in <head>. >>> >>> >>> >>> On Fri, Apr 19, 2013 at 4:13 PM, Sven Meier <[email protected]> wrote: >>> >>> Sounds good in theory. >>>> >>>> What's with a <wicket:header-items/> inside a <wicket:head>, e.g. the >>>> tag >>>> is on different positions in two panels' markup? >>>> >>>> Regards >>>> Sven >>>> >>>> >>>> On 04/19/2013 02:51 PM, Martin Grigorov wrote: >>>> >>>> Hi, >>>>> >>>>> There were questions in the mailing lists about how to control the >>>>> order >>>>> of >>>>> header contributions. >>>>> In Wicket 6 there are PriorityHeaderItems >>>>> and org.apache.wicket.settings.**IResourceSettings#** >>>>> getHeaderItemComparator() >>>>> but still this requires some great gymnastics to achieve a goal like >>>>> making >>>>> sure that <meta> for charset is always at the very top of <head> >>>>> content. >>>>> >>>>> What do you think about the following suggestion: >>>>> >>>>> MyPage.html: >>>>> >>>>> <head> >>>>> [some optional markup] >>>>> <wicket:header-items/> >>>>> [some more optional markup] >>>>> </head> >>>>> >>>>> That is, <wicket:header-items/> acts as a placeholder, something like >>>>> org.apache.wicket.markup.head.**filter.**HeaderResponseContainer, that >>>>> is used >>>>> to put all header contributions from Java or <wicket:head> in panels. >>>>> >>>>> This gives the developer the flexibility to put something that is at >>>>> the >>>>> top of the page's markup. >>>>> While rendering Wicket will put all header items in the placeholder. >>>>> And >>>>> the developer can also add something that should always be at the >>>>> bottom >>>>> of >>>>> <head> >>>>> >>>>> For backward compatibility, and sane default, if there is no >>>>> <wicket:header-items/> then everything is like it is today. >>>>> >>>>> >>>>> Example: >>>>> >>>>> <head> >>>>> <meta chartset="UTF-8"/> >>>>> <wicket:header-items/> >>>>> <script src="my-monkey-patch-of-**wicket-ajax.js"></script> >>>>> </head> >>>>> >>>>> >>>>> >>>>> >>> >> >> >
