Csswg-drafts: [css-cascade] !default declarations proposal
!default declarations, opposite to !important declarations, could set a default property value, if it has not been set yet, or if another !default declaration is more specific. User agent styles should be overridden with !default (of course excluding ones with !important).
Consider this example:
<body class="default-theme new-theme">
<button>Style me!</button>
</body>
.new-theme button {
border: thin solid black;
}
button {
border: 1px dotted grey !default;
}
.default-theme button {
border: none !default;
}
The button would have a thin solid black border in result. Having the !default declaration possible would make it so much easier to do theming or reset CSS.
css-cascade-5
CyberAP
All 2 comments
I don't like !important very much, and this would be a similar hack. And I don't think it's necessary, because you should be able to achieve a similar behavior by using selectors with 0 specificity (#1170), e.g.
:is(.default-theme button) {
border: none; /* default */
}
Loirooriol
on 5 Feb 2018
👍1
Just want to point out some implications of using !default vs. :is():
!defaulttakes the specificity into account,:is()does not!defaultapplies to individual properties,:is()to the whole rule- Both keep the effects of the
!importantannotation untouched
Sebastian
SebastianZ
on 7 Apr 2018
👍2
Was this page helpful?
0 / 5 - 0 ratings
Related issues
fantasai
路
3Comments
SelenIT
路
3Comments
bramdoppen
路
3Comments
heycam
路
3Comments
Meteor0id
路
3Comments
Most helpful comment
Just want to point out some implications of using
!defaultvs.:is():!defaulttakes the specificity into account,:is()does not!defaultapplies to individual properties,:is()to the whole rule!importantannotation untouchedSebastian