Stop using #crm-container (by finding another way to top the cascade over component css files)
Struggling to get your css to work? prefix it with #crm-container and ba-boom it goes to the front of the queue, mostly, without having to write !important
. This isn't brilliant practice, but for now there's no way for a theme to gain greater specificity in the cascade over external css files - ie all of those in https://github.com/civicrm/civicrm-core/tree/master/css other than civicrm.css.
Without finding another method to top the cascade, ending the use of `#crm-container in stylesheets, as proposed on Github will create new problems.
Example. With #crm-container .crm-dashlet-header
in the theme:
But with .crm-container .crm-dashlet-header
in the theme
The background colour and padding is now coming from dashboard.css, ln 30:
.crm-container .crm-dashlet-header {
background-color: #5d677b;
display: block;
padding: 5px 0;
}