How do inline styles and important interact with specificity?
PICTURE THIS: STACK VS QUEUE
Simple meaning
Inline styles beat classes and ids unless a rule uses important.
WHY — CSS instead of guessing?
Why interviewers care about CSS:
question about CSS.
trade-offs, and what you would actually do on a Frontend project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Inline styles beat classes
and ids unless a rule uses important.
- 2Important on a class
can beat an inline style without important, which is why important is a last resort.
- 3I solve fights by
lowering specificity or restructuring CSS, not stacking important.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Inline styles beat classes and ids unless a rule uses important. Important on a class can beat an inline style without important, which is why important is a last resort.