-
Notifications
You must be signed in to change notification settings - Fork 483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS4 custom properties #682
Comments
:root {
--fit: {
position: absolute;
top: 0; bottom: 0;
left: 0; right: 0;
}
}
.container {
@apply --fit;
} |
Umm, Is this CSS4 syntax or Sass / Less? It does not seem to be working with Chrome 54 or Node 8.0. nightly |
@DarylBerryhill It's not supported natively yet but there are polyfills |
http://cssnext.io |
Very much supported now. https://caniuse.com/#feat=css-variables |
Any plans to address this? CSS variables/custom properties are starting to blow up now that they're natively supported in modern browsers? |
Any news on this front? |
I'm curious why this is still an issue and if it will be addressed. It makes for a very messy log since I use CSS custom properties (CSS variables) under Here is an example: :root {
--ux-background: #FFFFFF;
--ux-on-background: #191D26;
} Where each line that starts with Then, when trying to use the custom property later, another warning is shown: body {
background-color: var(--ux-background);
color: var(--ux-on-background);
} For each line using a custom property, it shows the warning: The feature is supported in 94.62% of browsers at the time of writing this (per CanIUse which was posted earlier), and there are several articles recommending and outlining different use cases for them.
Should I start looking for a different linter? AtomLinter/linter-csslint#303 doesn't look promising. To link other issues, this is also mentioned in #538, #720, and #733. |
Will CSSlint be supporting CSS4 in the future?
getting an error when linting custom CSS properties.
Error message:
CSS snippet
It doesn't like the two "--" in front of the name
The text was updated successfully, but these errors were encountered: