Even though using very specific CSS selectors works it makes it a lot
harder to write that CSS.
Is there a way to force Wicket to write parent CSS contribution after
the children's CSS contribution?
Thanks,
Alec
On Sat, Apr 23, 2011 at 8:06 PM, Alec Swan alecs...@gmail.com wrote:
Thanks for
See if you can implement your contribution sequence rule by decorating the
IHeaderResponse e.g. [1] [2]
1 -
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.wicket/wicket-examples/1.5-rc2/org/apache/wicket/examples/resourcedecoration/ResourceDecorationApplication.java?av=f
2 -
Hello,
I have a component tree where some components contribute CSS. I have
inline CSS for the parent component that should be contributed last in
order to override CSS of child components.
Children components contribute their CSS in their constructors using
add(new StyleSheetReference(cssId,
I recall reading an article once noting that you could contribute the CSS
file noted in the parent class again in the child component and Wicket is
smart enough to not duplicate the contribution, but it still forces the CSS
file to appear later.
You also may consider changing the parent CSS rules
Thanks for the ideas, Clint. The child components do not know about
parent CSS, so I decided to use more specific CSS selectors in the
parent CSS to accomplish what I needed.
Alec
On Sat, Apr 23, 2011 at 4:35 PM, Clint Checketts checke...@gmail.com wrote:
I recall reading an article once noting
