You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Илья Нарыжный <ph...@ydn.ru> on 2011/11/03 15:43:03 UTC
Orders of CSS files
Hello,
Is there some way to specify "final" CSS file which will be used by
browsers at the end - and that's why can rewrite some CSS rules?
We have following case: we use "wicketstuff tagit autocomplite" component.
This component contribute some CSS to the header. But we need to overwrite
some css rules: the best solution for this to place some overwriting rules
at the end of list of CSS files. But the problem is in that fact, that
Wicket adds all contributed to the header things at the end of the HEAD
file.
Thanks,
Ilia
Re: Orders of CSS files
Posted by Clint Checketts <ch...@gmail.com>.
You can manually add in the autocomplete's CSS file yourself, and wicket
won't re-add it in. That way you can add in your custom CSS after it.
-Clint
On Thu, Nov 3, 2011 at 9:43 AM, Илья Нарыжный <ph...@ydn.ru> wrote:
> Hello,
>
> Is there some way to specify "final" CSS file which will be used by
> browsers at the end - and that's why can rewrite some CSS rules?
>
> We have following case: we use "wicketstuff tagit autocomplite" component.
> This component contribute some CSS to the header. But we need to overwrite
> some css rules: the best solution for this to place some overwriting rules
> at the end of list of CSS files. But the problem is in that fact, that
> Wicket adds all contributed to the header things at the end of the HEAD
> file.
>
> Thanks,
>
> Ilia
>