Rules Hub
Code Ruleset
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
frontend ruleP2stack specificStack: css
cssautoprefixertoolingredundancy
Don't hand-write vendor prefixes when autoprefixer is in the pipeline
With autoprefixer configured, write the unprefixed CSS property; manual -webkit-/-moz-/-ms- prefixes are redundant noise.
PR: frontpage-web · org-mining-hist-2026-06Created: Jun 18, 2026
Bad example
Old codecss
| 1 | .x { |
| 2 | -webkit-transform: scale(1); |
| 3 | -ms-transform: scale(1); |
| 4 | transform: scale(1); |
| 5 | } |
Explanation (EN)
Hand-maintained prefixes duplicate build output when the tool already supplies those exact fallbacks.
Objašnjenje (HR)
Good example
New codecss
| 1 | .x { |
| 2 | transform: scale(1); |
| 3 | } |
Explanation (EN)
Objašnjenje (HR)
Notes (EN)
Remove a manual prefix only after verifying the configured Autoprefixer/PostCSS pipeline emits the required fallback for the supported browser targets.
Exceptions / Tradeoffs (EN)
Some nonstandard properties or browser-specific fixes have no equivalent generated prefix. A transform example does not justify deleting every vendor declaration.