Container query preparation in SASS - Performance & Optimization

Performance: Container query preparation

MEDIUM IMPACT

Container queries affect how the browser recalculates styles and layouts when container sizes change, impacting rendering speed and visual stability.

Applying container queries to style components based on container size

SASS

@container (min-width: 30rem) { .card { font-size: 1.5rem; padding: 2rem; } }

Combining styles under one container query reduces style recalculations and CSS complexity.

📈 Performance GainSingle style recalculation and faster CSS parsing

Applying container queries to style components based on container size

SASS

@container (min-width: 30rem) { .card { font-size: 1.5rem; } } @container (min-width: 30rem) { .card { padding: 2rem; } }

Repeating the same container query multiple times causes redundant style recalculations and increases CSS complexity.

📉 Performance CostTriggers multiple style recalculations and increases CSS parsing time

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Multiple separate container queries	No extra DOM nodes	Multiple reflows on container resize	Higher paint cost due to frequent style changes	[X] Bad
Combined container queries in one block	No extra DOM nodes	Single reflow on container resize	Lower paint cost with fewer style changes	[OK] Good

Rendering Pipeline

Container queries cause the browser to monitor container sizes and recalculate styles when those sizes change, affecting style calculation and layout stages.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to repeated container size checks and style updates

Core Web Vital Affected

CLS

Container queries affect how the browser recalculates styles and layouts when container sizes change, impacting rendering speed and visual stability.

Optimization Tips

1Group container query styles to minimize repeated style recalculations.

2Avoid frequent container size changes that trigger container queries.

3Use DevTools Performance panel to monitor style recalculations and layout shifts.

Performance Quiz - 3 Questions

What is a main performance concern when using multiple separate container queries targeting the same container size?

A They increase the number of DOM nodes.

B They block network requests.

C They cause multiple style recalculations and layout thrashing.

D They reduce paint cost.

DevTools: Performance

How to check: Record a performance profile while resizing containers that trigger container queries. Look for style recalculation and layout events.

What to look for: High frequency of style recalculation and layout events indicates inefficient container query usage.

Practice

1. What is the main purpose of using @container in Sass?

easy

A. To reset all container styles

B. To create animations for containers

C. To define variables inside containers

D. To apply styles based on the size of an element's container

Solution

1. Step 1: Understand container queries

   Container queries allow styling elements depending on their container's size, not the viewport.

2. Step 2: Role of @container in Sass

   The @container rule in Sass is used to write container queries clearly and apply styles conditionally based on container size.

3. Final Answer:

   To apply styles based on the size of an element's container -> Option D

4. Quick Check:

   Container queries = style by container size [OK]

Hint: Remember: @container styles depend on container size, not viewport [OK]

Common Mistakes:

• Confusing container queries with media queries
• Thinking @container creates animations
• Using @container to define variables

2. Which CSS property must be set on a container element to enable container queries in Sass?

easy

A. container-type

B. container-size

C. container-query

D. container-style

Solution

1. Step 1: Identify container query activation property

   To use container queries, the container must declare container-type to enable size-based queries.

2. Step 2: Verify other options

   container-size, container-query, and container-style are not valid CSS properties for this purpose.

3. Final Answer:

   container-type -> Option A

4. Quick Check:

   Enable container queries = container-type [OK]

Hint: Set container-type to activate container queries on an element [OK]

Common Mistakes:

• Using non-existent properties like container-query
• Confusing container-type with container-size
• Forgetting to set container-type on the container

3. Given the Sass code below, what background color will the .box have if its container width is 500px?

@container (min-width: 600px) {
  .box {
    background-color: blue;
  }
}
.box {
  background-color: red;
}

medium

A. Blue

B. Red

C. No background color

D. Green

Solution

1. Step 1: Understand the container query condition

   The container query applies styles only if the container's width is at least 600px.

2. Step 2: Check container width against condition

   The container width is 500px, which is less than 600px, so the container query block does not apply.

3. Step 3: Determine fallback style

   The .box outside the container query has background-color: red;, so this style applies.

4. Final Answer:

   Red -> Option B

5. Quick Check:

   Container width 500px < 600px = red background [OK]

Hint: Check container width against min-width condition to pick color [OK]

Common Mistakes:

• Assuming container query applies regardless of container size
• Confusing container width with viewport width
• Ignoring fallback styles outside @container

4. Identify the error in the following Sass container query code:

@container (max-width 400px) {
  .card {
    padding: 1rem;
  }
}

medium

A. Container queries cannot use max-width

B. Incorrect selector inside @container

C. Missing colon after max-width

D. Padding value should be in px, not rem

Solution

1. Step 1: Check container query syntax

   The condition inside @container must have a colon after the property name, e.g., max-width: 400px.

2. Step 2: Verify other options

   The selector .card is valid, padding in rem is allowed, and max-width is a valid container query condition.

3. Final Answer:

   Missing colon after max-width -> Option C

4. Quick Check:

   Container query conditions need colons [OK]

Hint: Always use colon after property in container query conditions [OK]

Common Mistakes:

• Omitting colon in container query conditions
• Thinking max-width is invalid in container queries
• Confusing units for padding

5. You want to style a .card component differently when its container is narrower than 300px or wider than 700px using Sass container queries. Which of the following is the correct way to write this?

hard

A. @container (max-width: 300px), (min-width: 700px) { .card { font-size: 1.2rem; } }

B. @container (max-width: 300px) and (min-width: 700px) { .card { font-size: 1.2rem; } }

C. @container (max-width 300px), (min-width 700px) { .card { font-size: 1.2rem; } }

D. @container (width < 300px), (width > 700px) { .card { font-size: 1.2rem; } }

Solution

1. Step 1: Understand container query syntax for multiple conditions

   Multiple conditions separated by commas mean OR logic. Use colons after properties.

2. Step 2: Analyze each option

   @container (max-width: 300px), (min-width: 700px) { .card { font-size: 1.2rem; } } correctly uses commas and colons. @container (max-width: 300px) and (min-width: 700px) { .card { font-size: 1.2rem; } } uses AND which requires both conditions simultaneously (impossible here). @container (max-width 300px), (min-width 700px) { .card { font-size: 1.2rem; } } misses colons. @container (width < 300px), (width > 700px) { .card { font-size: 1.2rem; } } uses invalid syntax with < and >.

3. Final Answer:

   @container (max-width: 300px), (min-width: 700px) { .card { font-size: 1.2rem; } } -> Option A

4. Quick Check:

   Use commas for OR, colons after properties [OK]

Hint: Use commas for OR conditions and colons after properties [OK]

Common Mistakes:

• Using 'and' instead of commas for OR conditions
• Omitting colons in conditions
• Using invalid operators like < or > in container queries