csslint
csslint copied to clipboard
Expected RBRACE unknown property grid-template-columns
Hi using CSSLint (2.0.22) with brackets. Having a simple css file with:
#content {
display: grid;
grid-template-columns: repeat(4, 1fr);
}
getting this error:
1
Disallow IDs in selectors - Don't use IDs in selectors. (ids) #content {
3
Require use of known properties - Unknown property 'grid-template-columns'. (known-properties) grid-template-columns: repeat(4, 1fr);
3
Parsing Errors - Expected RBRACE at line 3, col 35. (errors) grid-template-columns: repeat(4, 1fr);
Whats wrong with that?
Also an issue here with many grid properties:
grid-template-areasgrid-template-columnsgrid-template-rowsgrid-area
Are these deprecated or something? Plugin version 2.0.22 from Brackets.
EDIT: This is not an issue with CSSLint's main project. Something hasn't been merged to cfjedimaster/brackets-csslint. An issue should be raised there, and it should be an easy fix. This issue should now be closed.
I also have an issue being flagged with grid-template-columns I am using the line below:
grid-template-columns: repeat(auto-fit, minmax(250px, 1fr));
and receive this message:
"Expected RBRACE at line 255, col 59."
I am using CSSLint installed via NPM at version 1.0.5. Also use the Atom linter plugin too
npm list -g --depth=1
C:\Users\###\AppData\Roaming\npm
+-- [email protected]
| +-- [email protected]
| `-- [email protected]
also got these results via csslint.net

@timeassistant: Separate issue I think, repeat is not an exported property in csslint.js
@JaredTheWolf ah ok, it is valid CSS though, is it something that can be corrected?
So is there a solution or a workaround for this? I am having the same issue
ul.products{grid-template-columns:repeat(12,1fr)}
I'm still having the issue as well with grid-template rows, grid-template-columns, and grid-gap. Keep getting the 'unknown property' error message.

@AntonioHouTX As previously mentioned, this is not an issue with CSSLint itself but rather the Brackets port of it. You may wish to raise the issue on that board instead.