The Specificity Problem
You'll learn how inline styles create an immovable specificity wall that breaks CSS's cascade and makes overrides nearly impossible.
The Specificity Ceiling
In CSS, specificity determines which styles win when multiple rules target the same element. Normally, you can override a class style with a more specific selector or with !important. But inline styles sit at the top of the specificity hierarchy—they beat almost everything except !important declarations.
When you use the style prop in React, you're applying inline styles:
<button style={{ backgroundColor: 'blue' }}>Click</button>
This blue background cannot be overridden by any class or ID selector in your stylesheets. Not even this:
#super-specific-id.multiple.classes button {
background-color: red; /* Won't work! */
}
The inline style wins. Period.
Why This Breaks CSS Patterns
CSS's cascade is designed to let you layer styles—defaults at the base, component styles in the middle, contextual overrides on top. Inline styles short-circuit this entire system. You lose the ability to:
- Apply theme variations through parent classes
- Override component styles based on state or context
- Use media queries to adapt styles (inline styles don't support them)
- Let utility classes or external stylesheets have any say
The only way to override an inline style is with another inline style or with !important in CSS (which creates its own specificity nightmare). This makes components rigid and hard to customize, especially in design systems where consumers need flexibility.
Key Takeaway: Inline styles have maximum specificity, making them nearly impossible to override and breaking the CSS cascade's layering system—use them only when dynamic values truly require runtime computation.