19 Mar
2014
19 Mar
'14
7:56 a.m.
Hi,
It's normal that the uicomponents are called after the skin.
I'm not sure I understand what you mean by 'override the class in own
style.css'. IMO this is a specificity problem and usually this is solved by
having more specific selectors. What would you'd expect? To write the same
selector and take precedence because it is in a uicomponents location?
You can copy in style.css the uicomponents you know come by default in
XWiki, but the problem will still remain for ssx and ssfx calls.
Thanks,
Caty
On Tue, Mar 18, 2014 at 7:57 PM, Guillaume "Louis-Marie" Delhumeau <
gdelhumeau(a)xwiki.com> wrote:
Hi guys,
When a user create a new skin, she might have to change the CSS classes
provided by some UI components. But she cannot simply override the class in
her own style.css because uicomponents css are currently called after the
skin in the HTML page.
To fix it, in Flamingo, I currently copy the uicomponents css code into my
style.css, and then modify it. Thanks to LESS, I am able to split my big
CSS file into several LESS files, so the code still looks good. Then, I
remove every calls to $xwiki.ssfx.use('uicomponents/...') in my templates.
But it might not be a good solution to have uicomponents splitted in
different locations like this.
What is your opinion about this?
Thanks,
Louis-Marie
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs