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
Fix property-no-unknown
false positives for scroll-driven animations
#7088
Comments
For more context, in case anyone is curious, I'm using this on my portfolio: renato-bohler/renato-bohler.github.io#92 and this is the GH Actions run that's failing. |
@renato-bohler Thanks for opening this issue with a reproducible demo! The
Could you please consider feedback to the |
property-no-unknown
false positives for scroll-driven animations
FYI. The spec is here: https://drafts.csswg.org/scroll-animations/ |
Hmm interesting, I'll definitely forward this to |
Yes! Let's keep it open so other people can find the same problem. |
That's a fascinating CSS feature. The
As with the known-css-properties package, we use an upstream package for functions (and it includes
Agreed. @renato-bohler In the meantime, you can workaround the issue using the {
"extends": [
"stylelint-config-standard"
],
"rules": {
"property-no-unknown": [true, { "ignoreProperties": ["animation-timeline"] }]
}
} Demo. |
What minimal example or steps are needed to reproduce the bug?
What minimal configuration is needed to reproduce the bug?
How did you run Stylelint?
Demo
Which Stylelint-related dependencies are you using?
What did you expect to happen?
The
animation-timeline
property to not be unknown.What actually happened?
The following error gets thrown:
Do you have a proposal to fix the bug?
Add
animation-timeline
tolib/reference/properties.js
? Though I'm not familiar with the source for this library, so I don't understand whyview-timeline
andanimation-range
properties are not unknown if they don't seem to be defined there.I also don't comprehend why the
view
function is not being flagged as unknown as I don't see it being declared inlib/reference/functions.js
.So maybe we should add those as well? If that's the case, I'm happy to open a PR.
The text was updated successfully, but these errors were encountered: