Currently, the TagHelper Wizard does not expose a tag attribute which would dictate whether the component will behave as a regular "form or "div" - https://docs.telerik.com/aspnet-core/api/kendo.mvc.ui.fluent/wizardbuilder#tagsystemstring

Currently, the Wizard displays any server-side errors that are added to the ModelState in the respective form fields within the Wizard steps (which is great).

The problem is that those errors are not "cleared" when the field is edited/changed. This prevent the form from being posted or the user to move to the next step if the form validation is enabled within the Wizard.

The only way to work with server-side error in the wizard form at the moment is to either disable form validation altogether or to attach an "onchange" event to each of the fields and clear any server-side errors manually once the field is changed.

Both solutions are far from ideal. It would be great if this was part of the default behaviour of the wizard form (like it already is for client-side errors).

In a Wizard with form integration, once you click on the "Done" button, the form is posted to the server, if the server returns the page with any errors in the ModelState, the wizard is displayed again from the first step and any errors are added to their respective fields.

The problem is that if the errors are not in the first step, the user simply sees the Wizard returning to the first step with no obvious indication of why. Only when he navigates to the next steps he will understand that an error was found. If the Wizard has many steps and the error in only in the last ones, the user can get confused.

It would be nice if the wizard could display an icon/badge on top of the step icon indicating that an error was found in that step.

Unlike the regular Form the Wizard's Form Integration doesn't allow .HtmlAttributes to be added to it. This is need to pass custom Actions, Ids and Classes to the Form.

Is it possible to implement an option to change the position of the Wizard ActionBar (Buttons and Pager elements)?

For example:

Currently, when a Telerik UI Form is nested inside a Telerik UI Wizard, the user should click twice on the Submit button after they have changed a field. 

Steps to replicate: 

1. Nest a form inside a Wizard.

2. Change a field in the form.

3. Click on the submit button.

4. The form is not submitted as the blur validation consumes the click. The user has to click the button submit again.

Short video demonstration:

http://somup.com/cr1oICqpnl