Common CSS anti-patterns - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to avoid using fixed pixel font sizes for better accessibility.

CSS

body { font-size: [1]; }

Drag options to blanks, or click blank then click option'

A10px

B1rem

C12px

D16px

Attempts:

3 left

💡 Hint

Common Mistakes

Using fixed pixel sizes like 16px reduces accessibility.

Choosing too small fixed sizes like 10px makes text hard to read.

Using 1rem instead of fixed pixels allows font sizes to scale based on user preferences, improving accessibility.

2fill in blank

medium

Complete the code to avoid using the !important rule which can cause maintenance issues.

CSS

.button { color: red[1] }

Drag options to blanks, or click blank then click option'

A:important;

B!important;

C!important

D;

Attempts:

3 left

💡 Hint

Common Mistakes

Adding !important unnecessarily makes debugging harder.

Forgetting the semicolon causes syntax errors.

Omitting !important helps keep CSS easier to maintain and override properly.

3fill in blank

hard

Fix the error in the selector to avoid using overly generic selectors that slow down rendering.

CSS

[1] p { color: blue; }

Drag options to blanks, or click blank then click option'

A.container

B#main

C*

Ddiv

Attempts:

3 left

💡 Hint

Common Mistakes

Using * selector slows down CSS rendering.

Using tag selectors alone can be too broad.

Using a class selector like .container is more specific and efficient than the universal selector *.

4fill in blank

hard

Fill both blanks to replace fixed width and height with flexible layout units.

CSS

.box { width: [1]; height: [2]; }

Drag options to blanks, or click blank then click option'

A100%

B50vw

C200px

D300px

Attempts:

3 left

💡 Hint

Common Mistakes

Using fixed pixel sizes causes layout issues on different screens.

Mixing fixed and relative units inconsistently.

Using 100% width and 50vw height makes the box responsive to screen size.

5fill in blank

hard

Fill all three blanks to replace float-based layout with modern Flexbox properties.

CSS

.container { display: [1]; justify-content: [2]; align-items: [3]; }

Drag options to blanks, or click blank then click option'

Ablock

Bcenter

Cflex

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using block display does not enable Flexbox.

Incorrect justify-content or align-items values cause layout issues.

Using display: flex with justify-content: center and align-items: start creates a flexible and modern layout without floats.

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