Event modifiers (preventDefault, stopPropagation) in Svelte - Mini Project: Build & Apply

Event modifiers (preventDefault, stopPropagation) in Svelte

📖 Scenario: You are building a simple web page with a form and a button inside it. You want to control how clicks and form submissions behave to improve user experience.

🎯 Goal: Build a Svelte component that uses event modifiers preventDefault and stopPropagation to manage form submission and button clicks properly.

📋 What You'll Learn

Create a Svelte component with a form and a button inside it

Use preventDefault modifier on the form submission event to stop the page from reloading

Use stopPropagation modifier on the button click event to prevent the click from bubbling up to the form

Show a message when the form is submitted and when the button is clicked

💡 Why This Matters

🌍 Real World

Forms and buttons are common in web apps. Controlling their events improves user experience by preventing unwanted page reloads and managing event flow.

💼 Career

Understanding event modifiers is essential for frontend developers to build interactive and user-friendly web interfaces using Svelte.

1

Set up the form and button elements

Create a Svelte component with a <form> element containing a <button> element. Add two variables formMessage and buttonMessage initialized as empty strings.

Svelte

  // Your code here



  Click me


{formMessage}
{buttonMessage}

Hint

Start by declaring two variables formMessage and buttonMessage as empty strings. Then create a form with a button inside.

2

Add form submission handler with preventDefault

Add a submit event handler to the <form> element using the on:submit|preventDefault modifier. Inside the handler, set formMessage to the string "Form submitted!".

Svelte

  let formMessage = "";
  let buttonMessage = "";



  Click me


{formMessage}
{buttonMessage}


  // Your code here

Hint

Use on:submit|preventDefault on the form and create a function handleSubmit that sets formMessage.

3

Add button click handler with stopPropagation

Add a click event handler to the <button> element using the on:click|stopPropagation modifier. Inside the handler, set buttonMessage to the string "Button clicked!".

Svelte

  let formMessage = "";
  let buttonMessage = "";

  function handleSubmit() {
    formMessage = "Form submitted!";
  }

  // Your code here



  Click me


{formMessage}
{buttonMessage}

Hint

Add on:click|stopPropagation to the button and create a handleClick function that sets buttonMessage.

4

Complete the component with proper event modifiers

Ensure the <form> uses on:submit|preventDefault={handleSubmit} and the <button> uses on:click|stopPropagation={handleClick}. The component should show messages when the form is submitted or the button is clicked without page reload or event bubbling.

Svelte

Hint

Check that the form and button have the correct event modifiers to prevent default submission and stop event bubbling.

Practice

1. What does the preventDefault event modifier do in Svelte?

easy

A. It delays the event handler execution.

B. It stops the event from bubbling up to parent elements.

C. It stops the browser's default action for the event.

D. It duplicates the event on child elements.

Solution

1. Step 1: Understand preventDefault purpose

   The preventDefault modifier stops the browser's default behavior, like following a link or submitting a form.

2. Step 2: Compare with other modifiers

   stopPropagation stops event bubbling, not default actions. The other options describe unrelated behaviors.

3. Final Answer:

   It stops the browser's default action for the event. -> Option C

4. Quick Check:

   preventDefault = stops default browser action [OK]

Hint: preventDefault stops browser default actions like clicks [OK]

Common Mistakes:

• Confusing preventDefault with stopPropagation
• Thinking it delays event handling
• Assuming it affects child elements

2. Which of the following is the correct syntax to prevent the default form submission in Svelte?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall Svelte event modifier syntax

   Svelte uses the pipe symbol | to add modifiers like preventDefault after the event name.

2. Step 2: Identify correct syntax

   correctly uses on:submit|preventDefault. uses wrong modifier, C uses dot instead of pipe, D uses incomplete modifier.

3. Final Answer:

   <form on:submit|preventDefault={handleSubmit}> -> Option D

4. Quick Check:

   Use pipe (|) for modifiers like preventDefault [OK]

Hint: Use pipe (|) after event name for modifiers [OK]

Common Mistakes:

• Using dot (.) instead of pipe (|) for modifiers
• Mixing preventDefault with stopPropagation
• Omitting the modifier entirely

3. Consider this Svelte code snippet:

<button on:click|stopPropagation={handleClick}>Click me</button>
function handleClick() {
  alert('Button clicked');
}
document.body.addEventListener('click', () => alert('Body clicked'));

What happens when the button is clicked?

medium

A. Only 'Button clicked' alert shows; 'Body clicked' is blocked.

B. Both alerts 'Button clicked' and 'Body clicked' show.

C. Only 'Body clicked' alert shows; button click is ignored.

D. No alerts show because event is stopped.

Solution

1. Step 1: Understand stopPropagation effect

   The stopPropagation modifier stops the event from bubbling up to parent elements like document.body.

2. Step 2: Analyze event listeners

   The button's click handler runs and shows 'Button clicked'. The body's click listener does not run because propagation is stopped.

3. Final Answer:

   Only 'Button clicked' alert shows; 'Body clicked' is blocked. -> Option A

4. Quick Check:

   stopPropagation blocks event bubbling [OK]

Hint: stopPropagation stops event bubbling to parents [OK]

Common Mistakes:

• Assuming both alerts show
• Confusing stopPropagation with preventDefault
• Thinking event is completely canceled

4. You wrote this Svelte code:

<a href='https://example.com' on:click|preventDefault|stopPropagation={goSomewhere}>Link</a>
function goSomewhere() {
  console.log('Navigating');
}

But clicking the link still navigates to the URL. What is the likely problem?

medium

A. The event modifiers are correct; the problem is elsewhere.

B. The function goSomewhere does not call event.preventDefault().

C. You forgot to pass the event parameter to goSomewhere.

D. The modifiers are in wrong order; preventDefault must come after stopPropagation.

Solution

1. Step 1: Check event modifiers usage

   In Svelte, preventDefault and stopPropagation modifiers automatically call the respective event methods before the handler runs.

2. Step 2: Verify code correctness

   The modifiers are correctly applied and order does not matter. The function does not need to call event.preventDefault()</> manually.

3. Step 3: Consider other causes

   If navigation still happens, the problem is likely outside this snippet, such as browser caching or other scripts.

4. Final Answer:

   The event modifiers are correct; the problem is elsewhere. -> Option A

5. Quick Check:

   Modifiers auto-call preventDefault and stopPropagation [OK]

Hint: Modifiers auto-call preventDefault; no manual call needed [OK]

Common Mistakes:

• Thinking modifier order matters
• Expecting manual event.preventDefault() call
• Assuming missing event parameter causes issue

5. You want to create a nested clickable list in Svelte where clicking a child item logs 'Child clicked' and clicking the parent logs 'Parent clicked'. You want to prevent the parent's click when a child is clicked. Which code correctly uses event modifiers to achieve this?

<ul on:click={parentClick}>
  <li on:click|???={childClick}>Child</li>
</ul>

function parentClick() {
  console.log('Parent clicked');
}
function childClick() {
  console.log('Child clicked');
}

hard

A. preventDefault

B. stopPropagation

C. stopPropagation|preventDefault

D. preventDefault|stopPropagation

Solution

1. Step 1: Understand event bubbling in nested elements

   Clicking a child triggers its click event and then bubbles up to the parent, triggering parent's click.

2. Step 2: Use stopPropagation on child click

   Adding stopPropagation on the child's click event stops the event from bubbling to the parent, preventing parent's handler from running.

3. Step 3: Confirm preventDefault is not needed

   We do not want to stop default browser actions here, only stop bubbling, so preventDefault is unnecessary.

4. Final Answer:

   stopPropagation -> Option B

5. Quick Check:

   Use stopPropagation to block parent event [OK]

Hint: Use stopPropagation to block parent event on child click [OK]

Common Mistakes:

• Using preventDefault instead of stopPropagation
• Combining both modifiers unnecessarily
• Reversing modifier order thinking it matters