Hi,

Noted, glad to hear that it worked for you.

Regarding the form submit event. We will pass it on for now.
You can use a custom code to submit the form. This gives more freedom to handle the flow programmatically.

Regards.

Hi Sean,

I'm sorry I havent understood if you will add the event or not.
As to what you say, force devs to use the form submit actually limits the way we can handle the stepper (we already discussed this time ago).
The reason is simple: if the "functionality" you provide with the theme is the stepper itself, why should you force users to create single form steppers? I have some steppers which need multiple forms to work. Being forced to use a single form for the whole stepper is, in some cases, just impossible.
Having the possibility to delegate the submit to the stepper (which is the real "container", instead of the form) really gives much more freedom.

This should also make you reason about why the design team just put the whole modal inside the form, to fix the content height issue. Imho (I have tried to figure out your reason, but can hardly come to reasonable ones) is a terrible design.

Instead of helping us being productive, all these little things (stepper, no more outlined checkboxes (remember?) , .. ) prevent us from doing more.

Please ,let me know if you will add the event, and if you will consider to improve the design of the stepper.
Thanks

Hi,

Thanks for your feedback.

This is a stepper component and by right it should handle the sections for steps.

Excluding the submit event from the core stepper logic was suggested by multiple users so we decided to go by this way.

The form submission is a feature that everyone utilizes differently.
The current approach gives more control in validating their forms as you need and decide when to submit the form.

Adding the submit event for the entire stepper limits the flexibility.

Can you please confirm if you now can technically submit the form after validation? If it works well then I think that should be fine since other users prefer the current solution.

Regarding the modal example with scrollable content, I thought it worked well for you as per your previous reply.

Now you are asking something else. We may consider an example with multiple forms in steps. However this is a rate case for most of the users, but we can consider it and demonstrate how our stepper component can be customized for such cases.

Regards.