I think it is a nice *not* to have. If head sections were included automatically, there is no way to distinguish between stuff that is there for design purposes and runtime purposes.
Martijn On Tue, Aug 19, 2008 at 12:28 PM, Wayne Pope <[EMAIL PROTECTED]> wrote: > :-) that might be it! > > Its a none issue really, just would be 'nice to have' > > On Tue, Aug 19, 2008 at 12:19 PM, Martijn Dashorst < > [EMAIL PROTECTED]> wrote: > >> There is the slight possibility that the wiki is inaccurate. >> >> Martijn >> >> On Tue, Aug 19, 2008 at 11:52 AM, Wayne Pope >> <[EMAIL PROTECTED]> wrote: >> > Hi, >> > >> > I just wanted to check I'm not alone on this, before going to the dev >> group. >> > I've created a simple base page and markup and using market inheritance I >> > have a child page with the content. >> > >> > This worsd fine, except that Wicket does not interprets <head> as >> > <wicket:head> automatically in the child page - as stated on the Wiki. I >> > need to use <wicket:head> to get it work. >> > >> > Anyone have this working without using <wicket:head>? >> > >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.3.4 is released >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
