Global vs scoped style strategies in Svelte - Practice Questions

Challenge - 5 Problems

❓ component_behavior

intermediate

How does scoped styling affect component styles in Svelte?

Consider a Svelte component with styles defined inside a <style> tag without the global attribute. What happens to these styles?

Svelte

<script>
  let color = 'red';
</script>

<style>
  p { color: red; }
</style>

<p>This text is styled.</p>

A The styles apply globally to all <code>&lt;p&gt;</code> elements in the app.

B The styles apply only to elements inside this component, not affecting other components.

C The styles are ignored and do not apply anywhere.

D The styles apply only to elements outside this component.

💡 Hint

Think about how Svelte isolates styles by default to avoid conflicts.

By default, Svelte scopes styles to the component they are defined in. This means styles inside a <style> tag without global only affect that component's elements.

📝 Syntax

intermediate

Which syntax applies global styles in a Svelte component?

In Svelte, how do you write CSS inside a component so that it applies globally to the whole app?

A <style> :global(p) { color: blue; } </style>

B <style scoped> p { color: blue; } </style>

C <style> p { color: blue; } </style>

D <style global> p { color: blue; } </style>

💡 Hint

Remember Svelte uses a special :global() selector inside styles for global CSS.

In Svelte, to apply global styles inside a component's style block, you wrap selectors with :global().

🔧 Debug

advanced

Why does this global style not apply outside the component?

Given this Svelte component code, why does the h1 outside the component not turn green?

Svelte

<style>
  h1 { color: green; }
</style>

<h1>This is inside component</h1>

A Because styles without <code>:global()</code> are scoped and do not affect elements outside the component.

B Because the <code>h1</code> tag is invalid inside <code>&lt;style&gt;</code>.

C Because Svelte requires styles to be in a separate CSS file to apply globally.

D Because the component is missing a <code>global</code> attribute on the <code>&lt;style&gt;</code> tag.

💡 Hint

Think about how Svelte isolates styles by default.

Svelte scopes styles by default. Without :global(), styles only apply inside the component. So h1 outside remains unaffected.

❓ state_output

advanced

What color will the paragraph text be after clicking the button?

In this Svelte component, what color will the paragraph text show after clicking the button once?

Svelte

<script>
  let isGlobal = false;
  function toggle() {
    isGlobal = !isGlobal;
  }
</script>

<style>
  p { color: red; }
  :global(.global-style) { color: blue; }
</style>

<p class={isGlobal ? 'global-style' : ''}>Hello!</p>
<button on:click={toggle}>Toggle Style</button>

A Black, because no style applies after toggle.

B Red, because scoped styles override global styles.

C No color change, the text remains red.

D Blue, because the class 'global-style' applies a global blue color.

💡 Hint

Check how the class changes and how global styles apply.

When the button is clicked, isGlobal becomes true, adding the global-style class. The global CSS sets color: blue for that class, so the paragraph text turns blue.

🧠 Conceptual

expert

Why prefer scoped styles over global styles in Svelte for large apps?

Which reason best explains why scoped styles are generally preferred over global styles in large Svelte applications?

A Scoped styles require less CSS code overall, reducing file size significantly.

B Global styles load faster because they are cached once and reused everywhere.

C Scoped styles prevent style conflicts by isolating CSS to components, making maintenance easier.

D Global styles automatically update component state, improving reactivity.

💡 Hint

Think about how CSS conflicts happen in big projects.

Scoped styles isolate CSS to components, avoiding conflicts and making it easier to maintain and reason about styles in large apps. Global styles can cause unintended overrides and bugs.