Replies: 4 comments 24 replies
-
This is the distinction between navigating and submitting and is valid, correctly behaviour. In fact, when the user clicks a tab to another page in a multi-page form, the values of that page are not submitted. I'd argue that changing this behaviour of clicking a tab to navigate to another page to submit (and validate) is confusing to a user. That's just not a standard form submission action that the user would expect. It's why a final validation on the last page of the form is so important. In case users miss an error on a previous page (which under normal circumstances shouldn't be possible), it's clear that they need to go back to fix errors. In addition, we also highlight which tab has the error, so it's pretty straightforward for users to realise that there's an error on a previous page. So this won't really be possible unless we only add client-side validation when clicking on a page tab. That's maybe something we can look at adding. But I'm not interested in adding a server-side validation check when you click on a tab to navigate to another page. First and foremost, we're not sending the data of the form to the server anyway. Hope that makes sense? Let me know if I've misunderstood anything. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your reply @engram-design I must be missing something then. What do you mean by "we highlight which tab has an error"? I can't see any class being added to the tabs, and clicking the tabs after submitting (with errors) doesn't display the inline errors either once viewing the page where validation errors occurred. So even if the tab was marked as containing errors, the user would still be confused about what field caused it exactly. I don't use a custom template, I only disabled the "Output Theme" option. I tried both the page reload and ajax submission methods and they both produce the same result. |
Beta Was this translation helpful? Give feedback.
-
Both JS options Plugin version is 2.0.21 |
Beta Was this translation helpful? Give feedback.
-
I tried to export the form so you can reproduce it, but I noticed the fields are not exported? Here's the JSON I get when exporting
|
Beta Was this translation helpful? Give feedback.
-
Hi,
Currently, validation only happens when using the next/previous/submit buttons of each form page. Navigating to another page doesn't trigger any validation of the current page fields.
This can be confusing for users to get a "please fill the required fields" on page 3, after they submit, if they forgot they jumped from page 1 to 3, without validating 1 or even seeing 2.
I reckon there should be an option to enable validation on navigation, to make sure the error message is always in context.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions