Default actions in Svelte - Performance & Optimization

Performance: Default actions

MEDIUM IMPACT

This concept affects how quickly user interactions respond and how smoothly the page updates after events.

Handling user clicks without blocking default browser behavior

Svelte

function handleClick(event) {
  // Let default action happen immediately
  console.log('Immediate action');
  // Run slow code asynchronously without blocking
  setTimeout(() => {
    console.log('Delayed action');
  }, 1000);
}

<button on:click={handleClick}>Click me</button>

Allows browser to perform default action immediately, keeping input responsive while running slow code later.

📈 Performance GainImproves INP by avoiding blocking default actions

Handling user clicks without blocking default browser behavior

Svelte

function handleClick(event) {
  event.preventDefault();
  // heavy computation or slow code here
  setTimeout(() => {
    console.log('Delayed action');
  }, 1000);
}

<button on:click={handleClick}>Click me</button>

Preventing default action and running slow code delays browser's natural response, causing input lag.

📉 Performance CostBlocks interaction responsiveness, increasing INP by 1000ms

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking default action with heavy JS	Minimal	0 immediate, delayed reflows possible	Low immediate, higher delayed	[X] Bad
Allowing default action, async heavy JS	Minimal	0 immediate	Low	[OK] Good

Rendering Pipeline

When a user event occurs, the browser first performs default actions like focusing or navigation. If JavaScript blocks or prevents these, the pipeline stalls, delaying rendering and interaction updates.

→Event Handling

→Layout

→Paint

⚠️ BottleneckEvent Handling stage when default actions are prevented and slow JS runs

Core Web Vital Affected

INP

This concept affects how quickly user interactions respond and how smoothly the page updates after events.

Optimization Tips

1Do not call event.preventDefault() unless you need to stop the browser's default behavior.

2Run heavy or slow code asynchronously to avoid blocking event handling.

3Let the browser perform default actions immediately to keep interactions smooth.

Performance Quiz - 3 Questions

What happens if you call event.preventDefault() and run slow code synchronously in a Svelte event handler?

A Page loads faster because JS blocks rendering.

B Input responsiveness decreases because default browser actions are delayed.

C No effect on performance.

D Browser skips default actions automatically.

DevTools: Performance

How to check: Record a performance profile while interacting with the element. Look for long tasks during event handling and delays before default actions.

What to look for: Long event handler durations and delayed paints indicate blocking default actions harming INP.

Practice

1. What is the main purpose of a default action in Svelte?

easy

A. To add behavior to an element when it is created and clean up when removed

B. To style an element with CSS automatically

C. To create a new component dynamically

D. To fetch data from an API when the page loads

Solution

1. Step 1: Understand what default actions do

   Default actions in Svelte run code when an element is created and can clean up when it is removed.

2. Step 2: Match purpose with options

   Only To add behavior to an element when it is created and clean up when removed describes adding behavior on creation and cleanup on removal, which matches default actions.

3. Final Answer:

   To add behavior to an element when it is created and clean up when removed -> Option A

4. Quick Check:

   Default actions add and clean behavior = B [OK]

Hint: Default actions run on element mount and cleanup on unmount [OK]

Common Mistakes:

• Confusing default actions with styling or data fetching
• Thinking default actions create components
• Assuming default actions only run once globally

2. Which of the following is the correct syntax to apply a default action named focus to an input element in Svelte?

easy

A. <input on:focus />

B. <input action:focus />

C. <input bind:focus />

D. <input use:focus />

Solution

1. Step 1: Recall Svelte default action syntax

   Default actions are applied using use:actionName on elements.

2. Step 2: Compare options with correct syntax

   <input use:focus /> uses use:focus, which is the correct way to apply the action.

3. Final Answer:

   <input use:focus /> -> Option D

4. Quick Check:

   Default action syntax = use:actionName [OK]

Hint: Use use: prefix to apply default actions [OK]

Common Mistakes:

• Using action: or on: instead of use:
• Confusing event handlers with actions
• Trying to bind actions like variables

3. Consider this Svelte code snippet:

function highlight(node) {
  node.style.backgroundColor = 'yellow';
  return {
    destroy() {
      node.style.backgroundColor = '';
    }
  };
}

<div use:highlight>Hello</div>

What will be the background color of the <div> when it is rendered?

medium

A. Yellow

B. No background color (default)

C. Red

D. Transparent

Solution

1. Step 1: Analyze the highlight action code

   The action sets backgroundColor to 'yellow' on the node when applied.

2. Step 2: Understand the effect on the <div>

   The <div> uses use:highlight, so its background color becomes yellow on render.

3. Final Answer:

   Yellow -> Option A

4. Quick Check:

   Action sets background to yellow = A [OK]

Hint: Default action runs on mount, sets style immediately [OK]

Common Mistakes:

• Thinking destroy runs immediately and clears color
• Confusing background color with text color
• Assuming no style changes without CSS

4. Given this default action code:

function logClick(node) {
  node.addEventListener('click', () => console.log('Clicked!'));
}

What is the main problem with this action?

medium

A. It should return a promise to work correctly

B. It uses an arrow function which is not allowed in actions

C. It does not remove the event listener when the element is removed

D. It must use use:logClick() with parentheses

Solution

1. Step 1: Check event listener management

   The action adds a click listener but does not remove it on cleanup.

2. Step 2: Understand Svelte action cleanup

   Actions should return an object with a destroy method to remove listeners and avoid memory leaks.

3. Final Answer:

   It does not remove the event listener when the element is removed -> Option C

4. Quick Check:

   Missing cleanup causes leaks = A [OK]

Hint: Always return destroy() to clean event listeners [OK]

Common Mistakes:

• Ignoring cleanup leads to memory leaks
• Thinking arrow functions are disallowed
• Assuming parentheses are required on use

5. You want to create a default action autoFocus that focuses an input element when it appears and logs "Focused" once. Which code correctly implements this behavior?

hard

A. function autoFocus(node) {
node.focus();
return {
update() {
console.log('Focused');
}
};
}

B. function autoFocus(node) {
node.focus();
console.log('Focused');
return {
destroy() {}
};
}

C. function autoFocus(node) {
setTimeout(() => node.focus(), 0);
console.log('Focused');
}

D. function autoFocus(node) {
node.addEventListener('focus', () => console.log('Focused'));
node.focus();
return {
destroy() {
node.removeEventListener('focus', () => console.log('Focused'));
}
};
}

Solution

1. Step 1: Focus element and log once on mount

   Calling node.focus() and logging immediately runs once when the element appears.

2. Step 2: Provide cleanup method

   Returning an object with an empty destroy method is valid and ensures cleanup structure.

3. Final Answer:

   Function that focuses and logs once, with destroy method -> Option B

4. Quick Check:

   Focus and log once on mount = D [OK]

Hint: Focus and log immediately, return destroy() for cleanup [OK]

Common Mistakes:

• Adding unnecessary event listeners for logging
• Missing return object with destroy method
• Logging multiple times on updates