Common CSS anti-patterns - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the 'Overqualified Selector' anti-pattern in CSS?

It happens when you use too many qualifiers in a selector, like div.header instead of just .header. This makes CSS slower and harder to maintain.

beginner

Why is using !important considered a CSS anti-pattern?

Because it forces styles to override others, making debugging and future changes difficult. It breaks the natural cascading and specificity rules of CSS.

intermediate

What problems arise from using deeply nested selectors in CSS?

Deep nesting creates complex selectors that are hard to read and maintain. It also increases CSS specificity, making overrides tricky and can slow down browser rendering.

beginner

Explain the 'Global Styles' anti-pattern in CSS.

Applying styles globally (like styling all p or div tags) can cause unintended side effects across the site, making it hard to control and predict styling.

beginner

Why is using fixed units like px for font sizes considered an anti-pattern?

Fixed units ignore user preferences and device differences, harming accessibility and responsiveness. Using relative units like em or rem is better.

Which of the following is an example of an overqualified selector?

A .button

B button.primary

C #header

D div.button.primary

Option D uses too many qualifiers (tag + classes), making it overqualified.

What is a major downside of using !important in CSS?

A It improves performance

B It makes styles easier to override

C It breaks natural cascading and makes debugging harder

D It reduces file size

!important forces style overrides, breaking CSS rules and complicating debugging.

Why should you avoid deep nesting of selectors?

A It makes CSS files smaller

B It increases specificity and reduces maintainability

C It improves browser rendering speed

D It helps with responsive design

Deep nesting increases specificity and makes CSS harder to maintain.

What problem can global styles cause?

A They cause unintended styling side effects

B They improve accessibility

C They reduce CSS file size

D They make styles easier to override

Global styles apply everywhere, which can cause unexpected changes in many places.

Which unit is better for font sizes to support accessibility and responsiveness?

A em or rem

B px

C pt

D cm

em and rem are relative units that adapt to user settings and screen sizes.

Describe three common CSS anti-patterns and why they should be avoided.

Think about how these affect maintainability, performance, and debugging.

Explain why using fixed units like px for fonts can harm accessibility and responsiveness.

Consider how users might change font size settings or use different screen sizes.

Practice

1. Which of the following is considered a common CSS anti-pattern that can make your styles hard to maintain?

easy

A. Using semantic HTML elements like <header> and <footer>

B. Using !important excessively to override styles

C. Writing CSS with clear and simple selectors

D. Using CSS variables for colors and fonts

Solution

1. Step 1: Understand the impact of !important

   Using !important forces styles to override others, which can cause confusion and difficulty in debugging.

2. Step 2: Compare with good practices

   Using semantic HTML and clear selectors improves maintainability, while !important overuse is a known anti-pattern.

3. Final Answer:

   Using !important excessively to override styles -> Option B

4. Quick Check:

   Excessive !important = Anti-pattern [OK]

Hint: Avoid !important unless absolutely necessary [OK]

Common Mistakes:

• Thinking !important is always good for quick fixes
• Confusing semantic HTML with CSS anti-patterns
• Believing CSS variables cause maintenance issues

2. Which CSS syntax is correct to avoid the anti-pattern of deep nesting?

easy

A. nav ul li a { color: blue; }

B. nav { ul { li { a { color: blue; } } } }

C. nav > ul > li > a { color: blue; }

D. nav ul li a { color: blue !important; }

Solution

1. Step 1: Identify valid CSS syntax

   nav { ul { li { a { color: blue; } } } } uses nested blocks like SCSS, which is invalid in plain CSS. Options A, C, and D are valid CSS syntax.

2. Step 2: Choose syntax avoiding deep nesting

   nav ul li a { color: blue; } uses simple descendant selectors without deep nesting or unnecessary specificity, avoiding anti-patterns.

3. Final Answer:

   nav ul li a { color: blue; } -> Option A

4. Quick Check:

   Simple selectors avoid deep nesting [OK]

Hint: Use flat selectors, avoid nested blocks in CSS [OK]

Common Mistakes:

• Confusing SCSS nesting with CSS syntax
• Using !important unnecessarily
• Overusing child selectors causing deep nesting

3. What will be the visual result of this CSS on a button?

button {
  width: 300px;
  padding: 1rem;
  background-color: lightblue;
}

Consider the anti-pattern of fixed widths.

medium

A. Button width stays fixed at 300px on all screen sizes

B. Button width adjusts automatically to content size

C. Button width becomes 100% of the container

D. Button width shrinks below 300px on small screens

Solution

1. Step 1: Understand fixed width effect

   The CSS sets a fixed width of 300px, so the button will always be 300px wide regardless of screen size.

2. Step 2: Consider responsive behavior

   Because width is fixed, the button won't adjust or shrink on smaller screens, which is an anti-pattern for responsive design.

3. Final Answer:

   Button width stays fixed at 300px on all screen sizes -> Option A

4. Quick Check:

   Fixed width = no responsiveness [OK]

Hint: Fixed width means no size change on different screens [OK]

Common Mistakes:

• Assuming padding affects width instead of content spacing
• Thinking width auto adjusts with fixed px value
• Confusing fixed width with max-width

4. Identify the error in this CSS snippet that demonstrates an anti-pattern:

.container {
  color: red !important;
}

.container {
  color: blue;
}

medium

A. The colors will blend and show purple

B. The syntax is invalid because of multiple color properties

C. The !important should be placed on the second color

D. The second color declaration is ignored due to !important

Solution

1. Step 1: Understand !important effect on CSS rules

   The color: red !important; overrides any later declarations without !important.

2. Step 2: Analyze the order of declarations

   The second color: blue; is ignored because the first has !important, causing an anti-pattern of forced overrides.

3. Final Answer:

   The second color declaration is ignored due to !important -> Option D

4. Quick Check:

   !important overrides later rules [OK]

Hint: Later rules ignored if earlier has !important [OK]

Common Mistakes:

• Thinking colors blend automatically
• Believing multiple same properties cause syntax errors
• Assuming !important can be moved freely without effect

5. You want to avoid the anti-pattern of repeated styles in CSS. Which approach below best solves this problem for multiple buttons with similar styles?

hard

A. Use inline styles on each button element to customize colors

B. Write separate CSS rules for each button with repeated properties

C. Use a shared class with common styles and add specific classes for differences

D. Use !important on all button styles to ensure they apply

Solution

1. Step 1: Identify the problem of repeated styles

   Writing repeated styles for each button causes maintenance issues and code bloat.

2. Step 2: Choose the best practice to reuse styles

   Using a shared class for common styles and specific classes for differences avoids repetition and keeps CSS clean.

3. Final Answer:

   Use a shared class with common styles and add specific classes for differences -> Option C

4. Quick Check:

   Shared classes reduce repetition [OK]

Hint: Use shared classes for common styles, specific for differences [OK]

Common Mistakes:

• Using inline styles causing repetition and harder maintenance
• Overusing !important instead of organizing styles
• Writing separate full rules for each similar element