Warning Unrecognized CSS property name
Why a typo'd property name like colr instead of color is silently dropped by the browser instead of producing a visible error.
The validator warns when a declared property name doesn't match a recognized CSS property, and isn't a custom property (--name) or a vendor-prefixed property (-webkit-, -moz-, -ms-, -o-), both of which it treats as valid without checking further.
Example
/* Flagged: typo */
.card { colr: red; }
/* Right */
.card { color: red; }Why it matters
CSS parsing is fault-tolerant by design: an unrecognized property is simply dropped, with no console error and no visible sign anything went wrong, other than the style you expected just not applying. A single-character typo like colr for color or widht for width is easy to type and easy to miss on a read-through, and there's nothing in the rendered page pointing you at the specific line. This check is a best-effort heuristic against a large but not exhaustive list of standard CSS properties — a flag here usually means a typo, but occasionally it's a genuinely new or experimental property this validator's list hasn't caught up with yet, worth a quick manual check either way.
Frequently asked questions
Will this ever flag a real, valid property as a false positive?
It's possible for very new or highly specialized CSS properties not yet in the validator's reference list. Custom properties (--name) and vendor-prefixed properties are always accepted without this check, since those are open-ended by design.
Does the browser show any error for an unknown property?
No — CSS parsing is designed to skip declarations it doesn't understand and keep going, rather than failing the whole stylesheet. That resilience is great for forward compatibility with newer CSS features, but it means typos fail silently too.