Navigation state
Use browser information for redirects, links, history-aware UI, and page-level decisions.
Browser component (navigation + viewport)
Use the Browser component for navigation, online/offline state, viewport, scroll, and history events.
Introduction
This tour positions the Browser component as App Connect’s bridge to client-side browser state. You will review which events and properties it exposes, how those values become usable in bindings, and when it is the right source for navigation, viewport, online status, and history-driven behavior.
Tour goals
The goal is to understand the Browser component as a shared context provider for the page, not just a list of random browser APIs. By the end, you should know which kinds of UI behavior belong here and how to inspect those events and values in Wappler.
Viewport and status
Read viewport size, scroll position, and online state where responsive or resilient UI needs them.
Event source
Treat browser events as declarative triggers that feed App Connect actions and bindings.
Identify which page behaviors should use Browser component state
Review the events and values the component contributes to App Connect
Connect those values to responsive or navigation-aware UI patterns
Where it shows up
Configure Browser events and state in Properties, and use it as a UI-level source for navigation and viewport data.
Wrap-up
Review what you did and choose a next tour.
Next steps
Pick a related tour to continue.