hi juergen,
Solution: you simply must attach HeaderContributor.forCss to any other
of your components (e.g. html in your code)
hmm, that i can do for own components, it'll break components like the wicket
tree, too!
also, this doesn't make sense, as when there is _no_ wicket-id in the
I added my comment to the other thread obviously discussing the very
same topic.
Juergen
On 6/24/07, Matej Knopp [EMAIL PROTECTED] wrote:
I also think this would be a good solution.
-Matej
On 6/24/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
On 6/23/07, Matej Knopp [EMAIL PROTECTED] wrote:
hi juergen,
I added my comment to the other thread obviously discussing the very
same topic.
yes, have seen that. what i still don't understand is, why did it work when
there was no wicket:id in the html? only the wicket:id broke
header-contribution.
regards, --- jan.
yes, this a valid comment. The html component is causing the
problem. The header contribution code has obviously been designed in a
way that it expects to be the very first contribution to the pages
output markup. With the html component it no longer is, since the
html tag must be rendered first
Jan,
the problem is that though you can attach attribute modifier (that is
what HeaderContributor is as well) to a Page (or WebPage), it'll not
work. WebPage doesn't have a tag. Since there is no tag, the attribute
modifier are not invoked, hence the nothing gets added to the header
section.
Err, I believe that you can do add(HeaderContributor.forCss(...)) in
page constructor.
-Matej
On 6/23/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:
Jan,
the problem is that though you can attach attribute modifier (that is
what HeaderContributor is as well) to a Page (or WebPage), it'll
not anymore.
Matej Knopp-2 wrote:
Err, I believe that you can do add(HeaderContributor.forCss(...)) in
page constructor.
-Matej
On 6/23/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:
Jan,
the problem is that though you can attach attribute modifier (that is
what
Why? Component.renderHead renders the attached behaviors and it's not
overriden for Page, so i does what components do.
HtmlHeaderContainer#renderHeaderSection calls page.renderHead().
So why this shouldn't work?
-Matej
On 6/24/07, Jonathan Locke [EMAIL PROTECTED] wrote:
not anymore.
Modifying the tag (onComponentTag) and rendering header contribution
(renderHead) are two different thing. While onComponentTag on a
behavior attached to page won't work (for reasons as you stated),
there is no reason why renderHead shouldn't work as well.
-Matej
On 6/23/07, Juergen Donnerstag
On 6/23/07, Matej Knopp [EMAIL PROTECTED] wrote:
Modifying the tag (onComponentTag) and rendering header contribution
(renderHead) are two different thing. While onComponentTag on a
behavior attached to page won't work (for reasons as you stated),
there is no reason why renderHead shouldn't
I also think this would be a good solution.
-Matej
On 6/24/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
On 6/23/07, Matej Knopp [EMAIL PROTECTED] wrote:
Modifying the tag (onComponentTag) and rendering header contribution
(renderHead) are two different thing. While onComponentTag on a
copy to the list, as sourceforge doesn't allow zip-attachments atm.
Original Message
Subject: Re: [Wicket-user] html wicket:id=html CSS
Date: Fri, 22 Jun 2007 08:53:23 +0200
From: Jan Kriesten [EMAIL PROTECTED]
Hi Juergen,
I'll try my best to find some spare time to do
12 matches
Mail list logo
