Your product's interface may span several documents and scrolling containers. An editor might run inside an iframe. A lesson might contain an embedded exercise. A banner might belong above a section that users scroll past.
Usertour v0.9.8 makes onboarding work more naturally in those layouts. Tooltips, launchers, and element conditions can now find targets inside same-origin iframes, including nested frames. Banners placed at an element remain stable as users scroll, and recover their content when your application replaces a view.
Usertour Cloud checkout also gains billing address and tax ID collection, along with automatic tax calculation.
Target elements inside same-origin iframes#
Previously, a target inside an iframe could be reported as missing even when it was visible to the user. v0.9.8 expands selector lookup to search the page first, then its same-origin iframes.
Write the selector as you would inside the frame itself. For a button with the ID submit-answer, use:
#submit-answer
You do not need to prefix it with the iframe selector, and you do not need to install Usertour inside that frame.
This lets a tour point to a control inside an embedded editor, a launcher attach to an action in an exercise, or a condition wait for an input inside a framed section of your application.
The same lookup applies to element conditions for presence, clicks, disabled state, text input, and whether a text field is filled. The MCP authoring guide and content schema also describe how selectors resolve inside frames, so AI-assisted authoring can use the same targeting behavior.
Positioning follows the framed element#
Finding the target is only part of the work. The tooltip also needs to appear in the right place as the frame scrolls or changes its content.
Usertour accounts for the frame's offset when positioning the tooltip, hides it when the target scrolls out of the frame's visible area, and follows the element when the frame navigates. Nested same-origin frames are supported as well.
When a selector matches multiple elements, sequence ordering remains predictable: matches on the main page come first, followed by matches inside frames in document order.
What stays outside the scope#
Cross-origin frames remain inaccessible. A frame served from another origin, or sandboxed without allow-same-origin, cannot be searched; a selector inside it is reported as not found.
Banner placement also remains scoped to the main page. This release expands iframe targeting for tooltips, launchers, and element conditions, while banners and their containers still attach to elements on the page itself.
Banners stay stable in scrolling layouts#
A banner placed at an element should not make the page fight the user's scroll position.
Previously, scrolling the target out of view could hide the banner. Removing the banner changed the layout, which could bring the target back into view and show the banner again. That cycle caused flickering and could pull the scroll position backward, making some placements difficult to scroll past.
In v0.9.8, an element-placed banner remains in the layout while its target is rendered, even when the target is outside the viewport. It still hides when the target itself is hidden or removed.
There is one behavior change to keep in mind: a banner attached to an element below the fold is now inserted as soon as the page loads, instead of waiting for that element to scroll into view. Banners at the top or bottom of the page are unchanged.
Content survives in-app navigation#
Single-page applications often replace an entire view without reloading the browser. If that view contained a banner's target, the banner could move to the new element but return as an empty box.
The banner now renders its content again whenever its mounting element moves. That keeps the message intact as the application changes views.
More complete billing details at Cloud checkout#
Usertour Cloud checkout now collects a full billing address and, where supported, provides a business purchase form for a legal name and tax ID.
Tax is calculated automatically from the checkout information. Eligible business purchases can show the applicable reverse-charge treatment, and invoices carry the company name, address, and tax ID. Existing subscriptions continue invoicing as before.
This gives teams a clearer path from purchasing a subscription to receiving an invoice with the details their finance team needs.
Upgrading to v0.9.8#
Usertour Cloud was already running this version when it was released. For self-hosted installations:
- No database migration or new environment variable is required.
- The served SDK bundle moves from 0.8.1 to 0.8.4. Upgrading the instance is enough; pages receive the bundle on their next load. The
usertour.jsnpm package is unchanged. - Review selectors on pages with same-origin iframes. A selector that previously matched nothing may now find an element inside a frame. Sequence-based targets and element conditions can therefore behave differently.
- Review banners attached below the fold. Their space is now part of the layout from page load.
Rollback is a revert to the previous image. The SDK runtime suite now includes 108 tests, with coverage for nested and scaled frames, frame navigation, scrolling targets, and banner containers replaced during navigation.
Read the full v0.9.8 release notes for implementation details. For the preceding performance and reliability improvements, see Usertour v0.9.7. Next, v0.9.9 introduces Embeds, a new way to place onboarding directly in your application's layout.



