Skip to main content


Specify a list of disallowed property and value pairs within declarations.

a { text-transform: uppercase; }
/** ↑ ↑
* These properties and these values */

The message secondary option can accept the arguments of this rule.


object: { "unprefixed-property-name": ["array", "of", "values", "/regex/", /regex/]|"value"|"/regex/"|/regex/ }

If a property name is surrounded with "/" (e.g. "/^animation/"), it is interpreted as a regular expression. This allows, for example, easy targeting of shorthands: /^animation/ will match animation, animation-duration, animation-timing-function, etc.

The same goes for values. Keep in mind that a regular expression value is matched against the entire value of the declaration, not specific parts of it. For example, a value like "10px solid rgba( 255 , 0 , 0 , 0.5 )" will not match "/^solid/" (notice beginning of the line boundary) but will match "/\\s+solid\\s+/" or "/\\bsolid\\b/".

Be careful with regex matching not to accidentally consider quoted string values and url() arguments. For example, "/red/" will match value such as "1px dotted red" as well as "\"foo\"" and "white url(/".


"transform": ["/scale3d/", "/rotate3d/", "/translate3d/"],
"position": "fixed",
"color": ["/^green/"],
"/^animation/": ["/ease/"]

The following patterns are considered problems:

a { position: fixed; }
a { transform: scale3d(1, 2, 3); }
a { -webkit-transform: scale3d(1, 2, 3); }
a { color: green; }
a { animation: foo 2s ease-in-out; }
a { animation-timing-function: ease-in-out; }
a { -webkit-animation-timing-function: ease-in-out; }

The following patterns are not considered problems:

a { position: relative; }
a { transform: scale(2); }
a { -webkit-transform: scale(2); }
a { color: lightgreen; }
a { animation: foo 2s linear; }
a { animation-timing-function: linear; }
a { -webkit-animation-timing-function: linear; }