You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
many css rules have things like td.classname or h1.classname. The element name shouldn't be necessary in most cases but in others it's causing specificity problems.
try to remove specificity issues, or at least identify where in core they are coming from and comment.
The text was updated successfully, but these errors were encountered:
We'll probably have to remove element names from selectors in core too for selectors to override like we want. May have to check with others on how their theme CSS is written too.
karindalziel
changed the title
css: check specificity
css: specificity, file loading
Jan 17, 2019
In addition to other issues, I'm currently using !important to add link underlines which isn't great.
What I'd like to have happen:
get django set up somewhat like rails, where you can specify that multiple files get loaded into one css file in a defined order. This has an advantage of being able to set variables in one file and use them in another
if we do that, we'd have to override the bootstrap.min file from core so it isn't called twice (currently I'm overriding that by having it in the same location). I played around a bit with using blocks to do this, which would be fine
many css rules have things like td.classname or h1.classname. The element name shouldn't be necessary in most cases but in others it's causing specificity problems.
try to remove specificity issues, or at least identify where in core they are coming from and comment.
The text was updated successfully, but these errors were encountered: