By zigma on
Hi,
I override some of theme related to user login block in style.css of my custom theme directory. My custom theme is based on Garland.
What i find weird is the style.css is read in reverse order. I can see this in FireFox developer's tool.
Any idea why this could be happening.
Comments
What do you mean read in
What do you mean read in reverse order? Rules later in the file override earlier rules and that is how is supposed to work.
Thank you for your response
Thank you for your response nevets.
It is working opposite. And i observe that this is not consistent. In some case it is being processed in correct order.
Here is an example. As you would observe, style that i haave in row#1183 is supposed to override, which is not happening since it is processes before the style that is added much earlier in the style.css file.
I am guessing I am looking
I am guessing I am looking at firebugs right pane.
The question is what specifically is not working and what rule do you think is taking precedents?
THat is correct.THis is
THat is correct.
THis is happening with most blocks on right side bar.
In this case padding-top, which i set to 13px in line#1183 in my style.css is not working. It is being overridden by entries at line#460, which sets padding-top to 0px.
In some case i have observed random sequence.
Instead of #block-blog-0 try
Instead of
#block-blog-0try#sidebar-right #block-blog-0That worked :) Now I have one
That worked :)
Now I have one query though. Line# 452 and #460 has been there as part of Garland theme. They continue to be processed in reverse order. I guess adding #wrapper .container before line#460 will fix it.
But I am wondering how come no one ever had to change the base theme.
Am I supposed to change all those standard css entries.
Since one is margin, the
Since one is margin, the other padding, I am not sure what problem there might be.
Thank you very much nevets.
Thank you very much nevets. That is possible. In case i can find other instances, I will get back to you.
update
Hi - just to be clear: Your "fix" is just to write your CSS with more specificity. However, this is still an issue. When creating a sub-them, the CSS files seem to be loaded in reverse order.
This is a problem as I am using a sub-theme for taxonomy portions of my site, but it is not appearing correctly because the style.css is being loaded FIRST before the default CSS files.
Why are sub-themes loading CSS in a different order?
Any ideas?
Same problem with Marvin theme...
I've got a theme sub'd from Chameleon (copied and modified Marvin), and my theme's style.css is being loaded before Chameleon's common.css. Kind of screws up any style overrides I attempt in my theme...
Firebug is showing the chain of "overriding" and I have verified the load order in the HTML header:
Has anyone figured out how to work around this yet? Chameleon's got a huge padding at the top of my page (3em) that I need to cut down so the logo doesn't have so much whitespace around it...
Thanks!
----------
"Nothing is impossible - it just hasn't been done yet."