-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
awSelectedStep condition #353
Comments
Not really, it was not an issue as of now :) When thinking about adding a condition to
Currently it is only possible to set If you need to define the selected step at startup using some kind of logic, you can currently do so by setting the |
It is also important to note that the default step input is not validated at the moment. This means that you can basically define an arbitrary step as the default step and it will be applied. If a "bad" index is used for the default step index, which violates the constraints of your navigation mode, your wizard may behave different from your expectations (for example it may prevent the user from navigating at all or only allow backwards navigation) |
Awesome, defaultStepIndex helped me! |
I noticed that my button (to go to the next step) doesn't do anything anymore. This is how the button looks like:
This is how my code looks like:
When I click the button, I stay in the same step, so nothing happens. Is the default behavior useless now? or do I understand you incorrectly? |
Thank you. It works to me. |
Hello,
Is there a particular reason why we cannot apply a condition to awSelectedStep?
The text was updated successfully, but these errors were encountered: