Session Manager (per-tab state)

Session Manager

Session Manager stores per-tab state for the lifetime of the tab/session. It’s great for wizards and temporary workflow data.

When session storage is the right choice

This tour teaches the decision rule for session storage, not just the API. Use it when workflow state should survive refreshes in the current tab but disappear when that tab’s session ends, which makes it a strong fit for wizards, short-lived progress, and temporary UI context that should not bleed into other tabs.

Wizards

Keep step data until completion.

Per-tab safety

Each tab has its own session storage.

Temporary state

Clears when the tab closes.

Survives reloads

Clears when tab closes

Great for multi-step forms

Objects are supported

Session Manager can store complex objects; they are serialized/deserialized automatically.

tip: Even with objects, keep stored values small and focused.

set(key, value) supports objects

Read with session.key

Clear with remove/removeAll

Core workflow

Bind UI to session values, and update them on events.

Write session state

Use session.set(key, value) in submit/click handlers to store the user’s progress or inputs.

set(key, value)

Stores a value for this tab session.

remove(key)

Removes one key.

removeAll()

Clears session state for the page.

Save intermediate form data

Store selected step/index

Clear on completion

Read session state in bindings

Use session.key in expressions to prefill fields, show status text, or conditionally render UI.

Screenshot: Read session state in bindingsClick to open the larger image

Pattern: multi-step form

Store each step’s data in session storage so refreshes don’t lose progress. Clear on final submit.

Step 1 writes session

Step 2 reads session

Final step clears session

Wrap-up

Next, pick the right persistence level for your app.

Next steps

Pick a related tour to continue.