Viewing 4 reply threads
You must be logged in to reply to this topic.
I’m having a hard time finding CSS selectors that aren’t ignored. I routinely use CSS selectors in the Tower Custom CSS Code section that my Chrome Inspector shows as “(index)” entries that are overridden by “style.css”.
I’ve been able to work around this by being more specific with my CSS selectors than the ones in style.css, but this makes things a good deal more difficult. It seems that the custom CSS is being applied first before style.css. Is there a way to make them apply in the reverse order?
Hello,
Sorry but i didn’t understand. Do you want the custom css code not to be applied? In this case just do not add any custom css code into your custom css box. The code in this box (if formed correctly) has to be applied before the one in style.css file, otherwise it has no point in adding it if the css file will keep making the theme styling.
I hope i explained myself well.
Best regards!
No, the opposite. I DO want my Custom CSS Code to be applied, but it is difficult. For example, if I use
.single_testimonial dl dd .param .position { color: blue; } // (index):398
…then the rule does not apply, because it is overridden by
.single_testimonial dl dd .param .position { color #aaa; } // style.css?ver=4.5.2:8207
I want my Custom CSS Code to take precedence over the same rule in style.css, but style.css is the one taking precedence.
Hello,
In this case you can use !important
to give priority to your custom code.
Example: .single_testimonial dl dd .param .position { color blue !important; }
Best regards!
You must be logged in to reply to this topic.