Insert icheck CSS right after bootstrap file. #2752
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What issues does this PR aim to fix?
Note: this PR is aimed to fix issues identified during the tests of the new LCARS Picard theme.
In CSS, the order of files matters.
The current code inserts
icheck
CSS in the end of<HEAD>
tag (after all theme files).icheck
CSS file uses a few!important
rules.If a theme needs to change something related to
icheck
elements, a higher selector specificity is needed (in addition to!important
rules).Another issue is the use of
body:not(.lcars)
. This selector doesn't work for the new theme, but it should.How does this PR fix the issues?
Changing where we insert this CSS file.
Replacing the
body:not(.lcars)
selector withbody:not([class*="lcars"])
.These changes will reduce the need of complex selectors or hacks to achieve a higher specificity.
Link documentation PRs if any are needed to support this PR:
none
By submitting this pull request, I confirm the following:
git rebase
)