NWD Status Checker (User/Tab/Net) v1.10.0

Sets how many seconds without interaction before the user counts as idle. It accepts any number or a dynamic value from your app, so the threshold can follow the plan, the role or the screen. Zero marks the user idle as soon as the element loads.

Sets the text published in User status label while the user is interacting. It exists for binding straight to a text element; a conditional should use User is idle, which is a yes/no and does not depend on the wording.

Sets the text published in User status label once the user goes idle.

Chooses which interactions reset the idle timer. The three options build on each other, from the narrowest to the widest. Keyboard only counts typing and nothing else, which suits a screen the visitor reads while typing elsewhere. Taps clicks and keys adds deliberate actions, including touch, and ignores a pointer that merely moves. Taps clicks keys and movement adds pointer movement, scrolling and touch dragging, which is the default because a visitor reading a long page is present without clicking anything. Pick the middle one when presence has to mean a deliberate act, as in a session timeout, since a nudged desk moves the pointer on its own.

• keyboard only
• taps clicks and keys
• taps clicks keys and movement

Keeps the person active while they interact with your app in another tab or window. Each tab runs its own timer, so with this off someone working in a second tab is reported idle in the first. It carries activity between tabs of the same origin, which means the same scheme, host and port: another site can neither hear it nor speak to it, and it never reaches another browser or another device. Two cases are worth knowing: the test version and the live version of your app share an origin, so working in one keeps the other active; and your Bubble address and your own domain are different origins, so a tab on each will not see the other.

Fires the User idle warning event this many seconds before the user goes idle, which is what a "your session expires in 30s" dialog needs. Zero turns the warning off.

Publishes User seconds idle on this cadence, for a live counter on screen. It comes off, and off is the right default: every published state makes Bubble re-evaluate everything bound to it, so a value republished every second re-renders conditionals every second. For a countdown without that cost, use User goes idle at and let the page do the arithmetic.

Publishes Tab is visible and Tab is focused, and fires the four tab events, when the visitor switches away from your tab or window and back. Visibility and focus are different signals: switching to another tab in the same window, or minimising, turns visibility off, while moving to another window or another monitor leaves the tab visible and only removes focus. Neither is the same as idle, which measures interaction rather than attention.

Fires Pointer left through the top when the pointer leaves the page by its top edge, where the tabs, the address bar and the close button are. It is a guess and not a detection: no browser tells a page that someone is about to switch tabs, because the shortcuts belong to the browser and the tab strip is outside the page. It also fires when the visitor reaches for a bookmark or the address bar, it cannot happen at all on touch devices, and it means nothing when the window is not at the top of the screen. Useful for a cart or a draft, never for a session or anything about security. Off by default for all of those reasons.

Publishes Network is online and fires the network events when the device gains or loses its network connection. Note what this measures: the device being attached to a network, not the internet working and not your app being reachable. False is reliable; true only means there is a network: a hotel captive portal, a router whose uplink is down or your own server being offline all look online from here.

Yes once the user has gone the configured time without interacting. This is what a conditional should read: it does not depend on the label wording, which the app may translate.

The instant of the last interaction counted as activity. It updates on every return to activity, not on every mouse move.

The instant the user will be marked idle if nothing else happens, published once per activity. Subtract the current date from it for a countdown without the plugin republishing a value every second.

The wording from the two label fields, following the current state. It exists for binding to a text element.

Seconds since the last activity, published only while the tick above is on. With the tick off it stays empty, and the countdown comes from User goes idle at.

Yes while the Pause activity detection action is in effect. Idle time stops being counted and interactions stop resetting it, so the user neither goes idle nor comes back until detection resumes. Reset returns it to no.

Yes while your tab is the one in front. It comes from the browser's own visibility signal and fires reliably, including when the visitor switches apps on a phone.

Yes while this window has keyboard focus. It is not the same as Tab is visible: focusing another window, or another monitor, leaves your tab visible while this turns no. For "is the person here", read this one; for "is the tab in front", read the other.

The instant the tab last went to the background.

Whether the device has a network connection. No is reliable; yes only means a network exists, and says nothing about a captive portal, a router whose uplink is down or your own server being up.

The instant the device last lost its network connection.

Fires once when the user crosses the idle threshold. It does not repeat while they stay idle.

Fires once when an idle user interacts again. It does not fire on every interaction, only on the return.

Fires the configured number of seconds before the user goes idle, and only when that field is above zero. It fires once per idle approach and resets on any activity.

Fires when the visitor switches to another tab, another window or another application, and also when the tab is being closed, because the browser marks the page hidden before it goes away. This is the reliable moment to save a draft or stop a timer: there is no separate closing event, since nothing a page can listen for survives a killed process or a swipe-away on a phone.

Fires when your tab comes back to the front.

Fires when the window stops receiving keyboard input, which happens when the visitor moves to another window or another application while your page stays on screen.

Fires when the window receives keyboard input again.

Fires when the pointer leaves the page by its top edge, with the detection turned on. Read it as an intention, not a fact: the visitor may be going for a bookmark, the address bar or another tab, and someone switching with the keyboard produces nothing at all. It fires once per exit and rearms when the pointer comes back over the page.

Fires when the device loses its network connection.

Fires when the device regains a network connection. It does not mean your app is reachable again: the device may be on a network that cannot reach it.