Multistep form does not work in Firefox on Windows 10

[alexanderbuergin]

Describe the bug

We are experiencing an issue with a multistep form where the multistep functionality does not work in Firefox on Windows 10. Specifically, the form fails to proceed to the next step. This behavior occurs both in native browser testing and in simulated environments.

Technical Details:
• We are using the default JavaScript and CSS provided in the form template.
• For testing purposes, we disabled our custom CSS to rule it out as a cause. The issue persists even with default styling.
• Our investigation suggests that the issue likely occurs when special characters are entered into the form fields.

Steps to reproduce

1.	Open the multistep form in Firefox on Windows 10.
2.	Enter special characters into the form fields.
3.	Attempt to proceed to the next step of the form.

Bildschirmaufnahme.2024-12-17.um.22.00.55.mp4

Form settings

• Multi-page form: Yes or No
• Submission Method: Ajax or Page Reload
• Client-side Validation: Yes or No
• Custom Form Templates: Yes or No

Craft CMS version

5.5.7

Plugin version

3.0.15

Multi-site?

YES

Additional context

Download Form SetUp: https://www.dropbox.com/t/3iHSHiLLDFV2DtAZ

[engram-design]

So I can confirm that I'm able to submit your form on any browser, and any OS. I did specifically test Firefox on Windows 10, and that's working okay for me.

We have had reports of users struggling with multi-page forms due to session retention issues (although we're not been able to isolate or reproduce the issue).

I'm wondering if you might like to try adding the following above your formRender() call.

{% form = craft.formie.forms.handle('contactForm').one() %}

{% do form.setStorageBehaviour('memory') %}

{{ craft.formie.renderForm(form) }}

And let me know if that makes a difference?

[alexanderbuergin]

Hello Josh

Perfect, that worked.

If it would help, I’d be happy to provide access to our server to potentially isolate the issue. Thank you!

[engram-design]

That's good to know, so it's certainly something to do with sessions. Do you have any non-standard session setup for your site (using Redis, etc)?

You'd be welcome to send details to [email protected] and I can see if I can uncover anything.

[mjniland1]

We're encountering a similar issue both in production and local environments, particularly on Safari 18.1.1 on Mac OS 15.1.1. The issue seems browser-specific, as some users running Chrome were able to complete the form without issue.

Using the default form styling and JavaScript, users cannot progress to page two of the form when the submission method is set to "Page Reload". On submission, the first page reloads, the fields are cleared, and a draft is saved to the Craft control panel. However, the user is unable to proceed.

We also tested using {% do form.setStorageBehaviour('memory') %}, but the behavior remains the same.

Interestingly, switching the submission method to "Ajax" allows users to proceed and save. However, when a user saves their progress, they are redirected back to page one, which is not the expected behavior.

[engram-design]

@mjniland1 Having this happen locally is an interesting one, and stranger still that this seems at face value browser-specific.

I don't suppose your project would be in a state that's available to share? If so, sending it through to [email protected] would be amazing.

And of course, ensuring that you're clearing your caches (Craft and browser), don't have any session handlers (different from the Craft norm). And that there's no static caching enabled.

[mjniland1]

The files have been sent, thank you for the quick response!

[engram-design]

Fortunately, I was able to reproduce that with @mjniland1 and it's certainly something to do with sessions on my end. For some reason, Craft's session helpers don't seem to be kicking into gear when Formie first starts interacting with them, which is leading to things getting messed up with the current page (among other session-based things).

I've resolved it on my end, but very keen to know if it's working for everyone else.

To get this early, run composer require verbb/formie:"dev-craft-5 as 3.0.16".

[mjniland1]

The issue appears to be resolved on my end, thank you @engram-design.