Component styles and encapsulation in Angular - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a component with inline styles.

Angular

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

@Component({
  selector: 'app-box',
  template: `<div class=\"box\">Hello</div>`,
  styles: [[1]]
})
export class BoxComponent {}

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

A'div.box { color: red; }'

B`div.box { color: red; }`

Cdiv.box { color: red; }

D[div.box { color: red; }]

Attempts:

3 left

💡 Hint

Common Mistakes

Using single quotes instead of backticks for multi-line CSS.

Not wrapping CSS in a string.

Passing CSS code without quotes.

The styles property expects an array of strings with CSS code. Using backticks allows multi-line CSS.

2fill in blank

medium

Complete the code to set the component's encapsulation to None.

Angular

import { Component, [1] } from '@angular/core';

@Component({
  selector: 'app-no-encap',
  template: `<p>No encapsulation</p>`,
  encapsulation: [1].None
})
export class NoEncapComponent {}

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

AViewEncapsulation

BEncapsulation

CComponentEncapsulation

DStyleEncapsulation

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect enum names like Encapsulation or StyleEncapsulation.

Forgetting to import the enum.

The ViewEncapsulation enum controls style encapsulation modes in Angular components.

3fill in blank

hard

Fix the error in the component decorator to properly apply styles with encapsulation.

Angular

@Component({
  selector: 'app-style-fix',
  template: `<h1>Title</h1>`,
  styles: [1],
  encapsulation: ViewEncapsulation.Emulated
})
export class StyleFixComponent {}

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

A[`h1 { font-weight: bold; }`]

B`h1 { font-weight: bold; }`

Ch1 { font-weight: bold; }

D'h1 { font-weight: bold; }'

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a string without an array.

Using single quotes instead of backticks for CSS.

The styles property must be an array of strings, so the CSS should be inside an array with backticks for multi-line support.

4fill in blank

hard

Fill both blanks to create a component with external styles and Shadow DOM encapsulation.

Angular

import { Component, [1] } from '@angular/core';

@Component({
  selector: 'app-shadow',
  templateUrl: './shadow.component.html',
  styleUrls: ['./shadow.component.css'],
  encapsulation: [2]
})
export class ShadowComponent {}

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

AViewEncapsulation

BNone

CShadowDom

DEmulated

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'None' or 'Emulated' instead of 'ShadowDom'.

Not importing ViewEncapsulation.

To use Shadow DOM encapsulation, import ViewEncapsulation and set encapsulation to ViewEncapsulation.ShadowDom.

5fill in blank

hard

Fill all three blanks to define a component with inline styles, Emulated encapsulation, and a template.

Angular

import { Component, [1] } from '@angular/core';

@Component({
  selector: 'app-inline',
  template: [2],
  styles: [[3]],
  encapsulation: [1].Emulated
})
export class InlineComponent {}

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

AViewEncapsulation

B`<p>Inline template</p>`

C`p { color: blue; }`

D'<p>Inline template</p>'

Attempts:

3 left

💡 Hint

Common Mistakes

Using single quotes for template or styles causing syntax issues.

Not wrapping styles in an array.

Forgetting to import ViewEncapsulation.

Use ViewEncapsulation for encapsulation, backticks for the template string, and backticks inside an array for styles.

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