CSS background property showing under invalid.deprecated scope despite not being invalid/deprecated.
Monstarrrr opened this issue · comments
Monstar commented
Prerequisites
I don't actually use Atom so I haven't run some of the following:
- [] Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
Reported the issue on vscode, been told it has to do with this repo so i'm reposting it here.
The background
property under transition
is showing up under the invalid.deprecated.color.system.css
scope, which makes it show up as an error.
Steps to Reproduce
- Create a new
css
file - Add the following code
.test {
transition: background;
}
Alternatively :
.test {
background: white;
}
.test:hover {
background: red;
transition: background 2s;
}
- Inspect editor tokens and scopes
- Hover on
background
Expected behavior:
Should not show as deprecated/invalid because the background
property is animatable and not deprecated: MDN docs | W3C docs.
Actual behavior:
The background
property under transition
is showing up under the invalid.deprecated.color.system.css
scope, which makes it show up as an error.
Reproduces how often:
100%