-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Linear stepper stuck on the step after re-initialization #15449
Comments
Can confirm, same issue |
Happens the same. Blocks even if:
|
Having the same issue |
Same issue here |
Any news here? Issue still exists and blocking almost any possible flow with url navigations, component UX looks inconsistent because of this |
I have the same issue with the latest version too. |
i have same issue here, i expend around 3 hours try to fix it but didn't work.... |
same issue here, is getting depressing to use Angular Material T_T |
|
Hi!, Is anybody working on it? Otherwise, I could try to fix it if you don't mind. |
…revious step issue Set the step as interacted if its linear step and is not the first step. angular#15449
…revious step issue Set the step as interacted if its linear step and is not the first step. angular#15449
What is the expected behavior?
After linear stepper reinitialization (f.e. web-app reload) all previously filled out forms of steps restore their valid state from storage and stepper restore selectedIndex. All these forms should be considered as visited and completed so user can navigate back without restriction.
What is the current behavior?
User completed step 1 and 2 and stay on step 3.
States of forms on step 1 and 2 are saved in storage.
After reload, forms on step 1 and 2 restore its states, so the steps are valid and
selectedIndex
set to step 3.User can't navigate back to step 2, despite the fact that this step is valid. User can only navigate to step 1.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-a5jw17
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Windows 8.1; Google Chrome 72.0.3626.121;
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: