When embedding a multistep Pro Form via a Bricks Template Element, clicking the “Next” button scrolls the user to the absolute top of the webpage rather than the top of the form. This behavior persists even when the Bricks template wrapper is disabled and no smooth scrolling scripts are active.
Pro Forms Multistep "Scroll to top" scrolls to the top of the page when invoked via Template Element
Hi @MRKNStudio,
Thanks for the detailed report — and for already ruling out smooth-scroll scripts and the template wrapper ![]()
For context on how the option behaves: when “Scroll to top” is enabled, the form scrolls to its own position on the page on each step change — it calculates the form’s top position relative to the document and subtracts your “Jump Offset” value (default 50). It does not target the page top on purpose, so what you’re seeing is unexpected and we’d like to pin it down.
A couple of things that would help us reproduce it here:
- Jump Offset value — which value do you have set in the multistep “Jump Offset” field? A very large value can push the calculated target above the form, which the browser then clamps to the very top of the page.
- Positioning around the form — does the Template element (or any wrapper/ancestor it sits in) use
position: fixed/absoluteor a CSStransform? Those can affect how the form’s on-page position is measured. - Is it the only form instance on the page, or could the same template/form be output more than once (e.g. via another template loop)?
- If possible, a page URL that reproduces it — that’s the fastest way for us to trace it precisely.
As a quick check on your side: temporarily set the Jump Offset to a small value like 20 and try the same form placed directly on a page (not via the Template element) vs. via the Template element, so we can confirm the Template element is the deciding factor.
Once we have the above, we’ll dig in.
Best,
Daniele