Naming conventions in CSS - Browser Rendering Trace

Render Flow - Naming conventions

[Write CSS selectors] -> [Apply naming rules] -> [Match HTML elements] -> [Apply styles] -> [Render visual styles]

The browser reads CSS selectors with specific naming conventions, matches them to HTML elements, then applies the styles to render the page visually.

Render Steps - 3 Steps

Code Added:No CSS applied yet

Before

[ btn-primary ]
  Click me

→

After

[ btn-primary ]
  Click me

The button text appears with default browser styles, no color or padding.

🔧 Browser Action:Parse HTML, build DOM tree

Code Sample

A blue button with white text styled using a clear, descriptive class name following naming conventions.

CSS

<div class="btn-primary">Click me</div>

CSS

.btn-primary {
  background-color: blue;
  color: white;
  padding: 1rem 2rem;
  border-radius: 0.5rem;
}

Render Quiz - 3 Questions

After applying step 2, what visual change do you see on the button?

A Button text turns white on a blue background

B Button text disappears

C Button background becomes transparent

D Button text turns black on a white background

Common Confusions - 2 Topics

Why does my CSS not apply when I use spaces in class names?

Spaces separate multiple classes in HTML. A class name cannot contain spaces. Use hyphens or underscores instead.

💡 Class names are one word or connected by hyphens/underscores, never spaces.

Why is my CSS selector too generic and affects unwanted elements?

Using simple names like .button can style many elements. Naming conventions like BEM add specificity to avoid this.

💡 Use descriptive, structured names to target only intended elements.

Property Reference

Naming Convention	Example	Visual Effect	Why Use It
BEM (Block__Element--Modifier)	.btn__icon--small	Clear structure, easy to style parts	Keeps CSS organized and scalable
Hyphen-case	.btn-primary	Readable class names	Common and easy to type
CamelCase	.btnPrimary	No visual effect	Used in JS but less common in CSS
Snake_case	.btn_primary	No visual effect	Less common, can be confusing

Concept Snapshot

Naming conventions help keep CSS organized and readable. Common styles: hyphen-case (.btn-primary), BEM (.block__element--modifier). Good names describe purpose and structure. Avoid spaces in class names. Clear naming prevents unwanted style conflicts.

Practice

1. Which of the following is the best practice for naming CSS classes?

easy

A. Use camelCase, like mainHeader.

B. Use uppercase letters and underscores, like Main_Header.

C. Use lowercase letters and hyphens to separate words, like main-header.

D. Use spaces between words, like main header.

Solution

1. Step 1: Understand common CSS naming styles

   CSS classes should be easy to read and consistent. Lowercase with hyphens is widely accepted.

2. Step 2: Compare options

   Use lowercase letters and hyphens to separate words, like main-header. uses lowercase and hyphens, which is recommended. Options B and C use uppercase or camelCase, less common in CSS. Use spaces between words, like main header. uses spaces, which is invalid in class names.

3. Final Answer:

   Use lowercase letters and hyphens to separate words, like main-header. -> Option C

4. Quick Check:

   Lowercase + hyphens = best CSS naming [OK]

Hint: Use lowercase and hyphens for CSS classes [OK]

Common Mistakes:

• Using spaces in class names
• Using uppercase letters
• Using camelCase instead of hyphens

2. Which CSS class name follows the BEM naming convention?

easy

A. button--primary

B. button_primary

C. buttonPrimary

D. button primary

Solution

1. Step 1: Recall BEM naming rules

   BEM uses block__element--modifier format. Double hyphens separate modifiers.

2. Step 2: Identify correct format

   button--primary uses double hyphens for modifier --primary, matching BEM. Options A and B use camelCase or underscores, not BEM. button primary uses space, invalid in class names.

3. Final Answer:

   button--primary -> Option A

4. Quick Check:

   BEM modifier uses double hyphens [OK]

Hint: BEM modifiers use double hyphens (--modifier) [OK]

Common Mistakes:

• Using underscores instead of hyphens
• Using camelCase for BEM
• Using spaces in class names

3. Given this CSS class name: card__title--large, what does it represent in BEM?

medium

A. Block: card, Modifier: title, Element: large

B. Modifier: card, Block: title, Element: large

C. Element: card, Block: title, Modifier: large

D. Block: card, Element: title, Modifier: large

Solution

1. Step 1: Break down the BEM parts

   In card__title--large, card is the block, title is the element (after double underscore), and large is the modifier (after double hyphen).

2. Step 2: Match parts to options

   Block: card, Element: title, Modifier: large correctly identifies block, element, and modifier. Other options mix these parts incorrectly.

3. Final Answer:

   Block: card, Element: title, Modifier: large -> Option D

4. Quick Check:

   BEM = block__element--modifier [OK]

Hint: BEM: block__element--modifier order [OK]

Common Mistakes:

• Confusing element and modifier positions
• Mixing block and element names
• Ignoring double underscores and hyphens

4. Identify the error in this CSS class name: nav__item_active

medium

A. Class name is too long

B. Underscore used instead of double hyphen for modifier

C. Spaces are used instead of underscores

D. Double underscore missing between block and element

Solution

1. Step 1: Check BEM syntax

   BEM requires modifiers to be separated by double hyphens --, not underscores.

2. Step 2: Analyze the class name

   The class nav__item_active uses a single underscore for the modifier, which is incorrect. It should be nav__item--active.

3. Final Answer:

   Underscore used instead of double hyphen for modifier -> Option B

4. Quick Check:

   Modifier separator = double hyphen [OK]

Hint: Modifiers need double hyphens, not underscores [OK]

Common Mistakes:

• Using single underscore for modifiers
• Forgetting double underscore between block and element
• Using spaces in class names

5. You want to create CSS classes for a card component with a title and a highlighted state using BEM. Which naming set is correct?

hard

A. card, card__title, card--highlighted

B. card, card_title, card_highlighted

C. card, card-title, card-highlighted

D. card, card__title--highlighted, card__highlighted

Solution

1. Step 1: Understand BEM structure for blocks, elements, and modifiers

   Block is card. Element is card__title. Modifier on block is card--highlighted.

2. Step 2: Evaluate options

   card, card__title, card--highlighted correctly uses BEM naming. card, card_title, card_highlighted uses underscores, not BEM. card, card-title, card-highlighted uses hyphens but not BEM format. card, card__title--highlighted, card__highlighted incorrectly applies modifier to element and duplicates modifier.

3. Final Answer:

   card, card__title, card--highlighted -> Option A

4. Quick Check:

   BEM block, element, modifier naming [OK]

Hint: BEM: block, block__element, block--modifier [OK]

Common Mistakes:

• Using underscores instead of BEM separators
• Applying modifiers to elements incorrectly
• Mixing hyphen and underscore styles