Why actions add reusable element behavior in Svelte - Visual Breakdown

Concept Flow - Why actions add reusable element behavior

Define action function

↓

Attach action to element

↓

Element created in DOM

↓

Action runs with element

↓

Action adds behavior (event, style, etc.)

↓

Element behaves with added features

↓

Element removed -> action cleanup runs

This flow shows how a Svelte action is defined, attached to an element, runs to add behavior, and cleans up when the element is removed.

Execution Sample

Svelte

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

<div use:highlight>Text</div>

This code defines a highlight action that colors an element's background yellow and cleans up when removed.

Execution Table

Step	Action	Element State	Effect on Element	Cleanup
1	Define highlight action	No element yet	No effect	No cleanup
2	Attach highlight to <div>	<div> created	No effect yet	No cleanup
3	Run highlight(node)	<div> exists	Background color set to yellow	Prepare destroy function
4	Element displays with yellow background	<div> visible	User sees yellow background	Cleanup ready
5	Remove <div> from DOM	<div> removed	No visible element	destroy() runs, background reset

💡 Element removed from DOM, action cleanup executed to reset styles

Variable Tracker

Variable	Start	After Step 3	After Step 5
node.style.backgroundColor	'' (empty)	'yellow'	'' (reset)

Key Moments - 3 Insights

Why does the background color change only after attaching the action?

Because the action runs only when attached to an element in the DOM, as shown in step 3 of the execution_table.

What happens if the element is removed from the DOM?

The action's destroy function runs to clean up, resetting styles as in step 5 of the execution_table.

Can the action add other behaviors besides styles?

Yes, actions can add event listeners or other behaviors, not just styles, by using the node parameter.

Visual Quiz - 3 Questions

Look at the execution_table, what is the background color of the element after step 3?

A 'yellow'

B '' (empty)

C 'red'

D 'blue'

💡 Hint

Check the 'Effect on Element' column at step 3 in the execution_table.

At which step does the action's cleanup function run?

A Step 2

B Step 5

C Step 3

D Step 4

💡 Hint

Look at the 'Cleanup' column in the execution_table to find when destroy() runs.

If the action did not return a destroy function, what would happen when the element is removed?

A The element would not be removed

B The background color would reset automatically

C The background color would stay yellow

D The action would run again

💡 Hint

Refer to the 'Cleanup' column in the execution_table and variable_tracker for style reset.

Concept Snapshot

Svelte actions are functions attached to elements.
They run when the element is created.
Actions add reusable behavior like styles or events.
They can return a destroy function to clean up.
Cleanup runs when the element is removed.
This makes behavior reusable and clean.

Full Transcript

In Svelte, actions let you add reusable behavior to elements. You define an action function that receives the element node. When you attach the action to an element using use:actionName, the function runs and can modify the element, for example by changing styles or adding event listeners. The action can return a destroy function that runs when the element is removed, cleaning up any changes. This process helps keep behavior reusable and prevents leftover effects. The execution table shows the steps: defining the action, attaching it, running it to add behavior, displaying the element with the behavior, and finally cleaning up when the element is removed.