Thank you, I had no idea about the important attribute. I just thought that it would make more sense if the page's css was rendered after all components contributions.
Regards, Poko On Wed, Mar 2, 2011 at 2:44 PM, Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Can't you just use !important at page CSS definition to override what > the component defines as default? > > Ernesto > > On Wed, Mar 2, 2011 at 1:24 PM, Poko Booth <poko.bo...@gmail.com> wrote: > > Hi all, > > > > I have created some custom components which implement the > IHeaderContributor > > interface in order to obtain their custom css when rendered. > > I want to give user the opportunity to override these classes without > making > > them create specific new trees in their page's basic css. > > > > To be more specific, I have created a custom textfield which renders an > > "Error" class in its tag when not valid. > > I have also created a css file which is being rendered in order to define > > the "Error" class displaying the textfield with red borders [the > component > > implements the IHeaderContributor]. > > I want to give user the opportunity to define a new "Error" class in his > > page's css in order to override this. > > The problem is that the page's css is being rendered before the > components > > css reference thus doesn't override it. > > > > Do you have any hint on how to proceed? > > > > Best regards, > > Poko > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
