Component styles and encapsulation in Angular - Mini Project: Build & Apply

Component styles and encapsulation

📖 Scenario: You are building a simple Angular component that displays a user profile card. You want to style this card with a background color and padding. To keep styles organized and avoid affecting other parts of the app, you will use Angular's component style encapsulation.

🎯 Goal: Create an Angular standalone component called UserProfileComponent with a template showing a user name inside a <div>. Add styles to give the <div> a light blue background and some padding. Use Angular's default style encapsulation to keep these styles local to the component.

📋 What You'll Learn

Create a standalone Angular component named UserProfileComponent

Add a template with a <div> containing the text User: Alice

Add component styles to set the div background color to light blue and padding to 1rem

Use Angular's default style encapsulation (Emulated) to keep styles local

💡 Why This Matters

🌍 Real World

Component style encapsulation is essential in Angular apps to keep styles modular and prevent unwanted side effects across the app.

💼 Career

Understanding Angular component styles and encapsulation is a key skill for frontend developers working with Angular to build maintainable and accessible UI components.

1

Create the UserProfileComponent with template

Create a standalone Angular component named UserProfileComponent with a template that contains a <div> showing the text User: Alice. Use the @Component decorator with standalone: true and include the selector as app-user-profile.

Angular

@Component({
  selector: 'app-user-profile',
  standalone: true,
  template: `User: Alice`
})
export class UserProfileComponent {
  // Your code here
}

Hint

Use the @Component decorator with standalone: true and define the template inline.

2

Add component styles for background and padding

Add a styles array to the @Component decorator with CSS that sets the div background color to lightblue and padding to 1rem.

Angular

@Component({
  selector: 'app-user-profile',
  standalone: true,
  template: `User: Alice`,
  // Add styles array below
})
export class UserProfileComponent {
}

Hint

Use the styles property with an array containing a CSS string targeting the div.

3

Set style encapsulation to Emulated explicitly

Add the encapsulation property to the @Component decorator and set it to ViewEncapsulation.Emulated to explicitly use Angular's default style encapsulation.

Angular

import { Component, ViewEncapsulation } from '@angular/core';

@Component({
  selector: 'app-user-profile',
  standalone: true,
  template: `User: Alice`,
  styles: [
    `div { background-color: lightblue; padding: 1rem; }`
  ],
  // Add encapsulation property below
})
export class UserProfileComponent {
}

Hint

Import ViewEncapsulation from @angular/core and set encapsulation to ViewEncapsulation.Emulated.

4

Add accessibility role and aria-label to the div

Add role="region" and aria-label="User Profile Card" attributes to the <div> in the component template to improve accessibility.

Angular

import { Component, ViewEncapsulation } from '@angular/core';

@Component({
  selector: 'app-user-profile',
  standalone: true,
  template: `User: Alice`,
  styles: [
    `div { background-color: lightblue; padding: 1rem; }`
  ],
  encapsulation: ViewEncapsulation.Emulated
})
export class UserProfileComponent {
  // Add accessibility attributes to the div in the template
}

Hint

Add role="region" and aria-label="User Profile Card" inside the div tag in the template string.

Practice

1. What does ViewEncapsulation.Emulated do in Angular component styles?

easy

A. It removes all styles from the component.

B. It disables all style encapsulation, applying styles globally.

C. It scopes styles to the component using generated attributes, preventing style leaks.

D. It uses the browser's native Shadow DOM for style encapsulation.

Solution

1. Step 1: Understand Emulated encapsulation

   Emulated encapsulation scopes styles by adding unique attributes to elements, so styles apply only inside the component.

2. Step 2: Compare with other modes

   Unlike None (global styles) or ShadowDom (native Shadow DOM), Emulated simulates encapsulation without browser Shadow DOM.

3. Final Answer:

   It scopes styles to the component using generated attributes, preventing style leaks. -> Option C

4. Quick Check:

   Emulated = Scoped styles with attributes [OK]

Hint: Emulated adds unique attributes to isolate styles [OK]

Common Mistakes:

• Confusing Emulated with None or ShadowDom
• Thinking Emulated disables styles
• Assuming Emulated uses native Shadow DOM

2. Which of the following is the correct way to set no style encapsulation in an Angular component?

easy

A. @Component({ encapsulation: ViewEncapsulation.Emulated })

B. @Component({ encapsulation: ViewEncapsulation.None })

C. @Component({ encapsulation: ViewEncapsulation.Native })

D. @Component({ encapsulation: ViewEncapsulation.ShadowDom })

Solution

1. Step 1: Identify the correct encapsulation for no style isolation

   ViewEncapsulation.None disables style encapsulation, making styles global.

2. Step 2: Check other options

   Emulated scopes styles, Native is deprecated, ShadowDom uses native Shadow DOM, so only None disables encapsulation.

3. Final Answer:

   @Component({ encapsulation: ViewEncapsulation.None }) -> Option B

4. Quick Check:

   No encapsulation = ViewEncapsulation.None [OK]

Hint: None means no encapsulation, styles apply globally [OK]

Common Mistakes:

• Using Emulated or ShadowDom instead of None
• Confusing Native with None (Native is deprecated)
• Missing the encapsulation property entirely

3. Given this Angular component code:

@Component({
  selector: 'app-box',
  template: `
Hello
`,
  styles: [`.box { color: red; }`],
  encapsulation: ViewEncapsulation.None
})
export class BoxComponent {}

What will be the color of all elements with class box in the entire app?

medium

A. All box elements in the app will be red.

B. Only the box inside app-box will be red.

C. No box elements will be red because styles are scoped.

D. Only box elements inside Shadow DOM will be red.

Solution

1. Step 1: Understand ViewEncapsulation.None effect

   None disables style encapsulation, so styles apply globally to all matching elements.

2. Step 2: Apply to the .box class

   The style `.box { color: red; }` will affect every element with class 'box' in the entire app, not just inside this component.

3. Final Answer:

   All box elements in the app will be red. -> Option A

4. Quick Check:

   None encapsulation = global styles [OK]

Hint: None means styles leak globally, coloring all matching elements [OK]

Common Mistakes:

• Assuming styles stay inside component with None
• Confusing ShadowDom encapsulation effects
• Thinking Emulated behaves like None

4. You wrote this Angular component:

@Component({
  selector: 'app-test',
  template: `
Test
`,
  styles: [`p { font-weight: bold; }`],
  encapsulation: ViewEncapsulation.ShadowDom
})
export class TestComponent {}

But the p text is not bold in the browser. What is the likely cause?

medium

A. The styles are scoped inside Shadow DOM, but you are inspecting outside it.

B. The browser does not support Shadow DOM, so styles are ignored.

C. You forgot to import ViewEncapsulation from @angular/core.

D. The component selector is incorrect and not used in HTML.

Solution

1. Step 1: Understand ShadowDom encapsulation

   ShadowDom encapsulates styles inside the browser's native Shadow DOM, isolating them from the main document.

2. Step 2: Inspecting styles outside Shadow DOM

   If you inspect the page outside the Shadow DOM, you won't see the styles applied because they are inside the component's shadow root.

3. Final Answer:

   The styles are scoped inside Shadow DOM, but you are inspecting outside it. -> Option A

4. Quick Check:

   ShadowDom styles live inside shadow root, not visible outside [OK]

Hint: ShadowDom styles are inside shadow root, inspect there [OK]

Common Mistakes:

• Assuming ShadowDom styles apply globally
• Not checking if component is used in HTML
• Thinking browser lacks Shadow DOM support

5. You want to create a reusable Angular component with styles that do not affect the rest of the app and also want to use native browser features for style encapsulation. Which encapsulation should you choose and why?

hard

A. Do not set encapsulation; Angular will automatically isolate styles.

B. Use ViewEncapsulation.Emulated because it simulates encapsulation without Shadow DOM.

C. Use ViewEncapsulation.None to apply styles globally for easy reuse.

D. Use ViewEncapsulation.ShadowDom to leverage native Shadow DOM for true style isolation.

Solution

1. Step 1: Identify the goal for style isolation and native features

   You want true style isolation and to use the browser's native Shadow DOM capabilities.

2. Step 2: Match encapsulation mode to goal

   ViewEncapsulation.ShadowDom uses native Shadow DOM, providing real isolation and native browser support.

3. Step 3: Evaluate other options

   None applies styles globally (not isolated), Emulated simulates but does not use native Shadow DOM, and default does not guarantee native isolation.

4. Final Answer:

   Use ViewEncapsulation.ShadowDom to leverage native Shadow DOM for true style isolation. -> Option D

5. Quick Check:

   Native isolation = ShadowDom encapsulation [OK]

Hint: ShadowDom uses native browser isolation for styles [OK]

Common Mistakes:

• Choosing None and expecting isolation
• Confusing Emulated with native Shadow DOM
• Assuming Angular isolates styles without setting encapsulation