-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Stepper [completed]="true" cannot skip steps #15310
Labels
P4
A relatively minor issue that is not relevant to core functions
Comments
crisbeto
added
has pr
P4
A relatively minor issue that is not relevant to core functions
labels
Mar 6, 2019
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 6, 2019
Currently we allow for the `completed` value of a step to be overwritten, however setting it to `true` still won't allow the user to skip the step, because the `interacted` flag won't be flipped if they haven't been on a particular step before. Fixes angular#15310.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 6, 2019
Currently we allow for the `completed` value of a step to be overwritten, however setting it to `true` still won't allow the user to skip the step, because the `interacted` flag won't be flipped if they haven't been on a particular step before. Fixes angular#15310.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 13, 2019
Currently we allow for the `completed` value of a step to be overwritten, however setting it to `true` still won't allow the user to skip the step, because the `interacted` flag won't be flipped if they haven't been on a particular step before. Fixes angular#15310.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 13, 2019
Currently we allow for the `completed` value of a step to be overwritten, however setting it to `true` still won't allow the user to skip the step, because the `interacted` flag won't be flipped if they haven't been on a particular step before. Fixes angular#15310.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Mar 18, 2019
Currently we allow for the `completed` value of a step to be overwritten, however setting it to `true` still won't allow the user to skip the step, because the `interacted` flag won't be flipped if they haven't been on a particular step before. Fixes angular#15310.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jun 15, 2019
Currently we allow for the `completed` value of a step to be overwritten, however setting it to `true` still won't allow the user to skip the step, because the `interacted` flag won't be flipped if they haven't been on a particular step before. Fixes angular#15310.
jelbourn
pushed a commit
that referenced
this issue
Sep 6, 2019
Currently we allow for the `completed` value of a step to be overwritten, however setting it to `true` still won't allow the user to skip the step, because the `interacted` flag won't be flipped if they haven't been on a particular step before. Fixes #15310.
mmalerba
pushed a commit
that referenced
this issue
Oct 8, 2019
…15403) Currently we allow for the `completed` value of a step to be overwritten, however setting it to `true` still won't allow the user to skip the step, because the `interacted` flag won't be flipped if they haven't been on a particular step before. Fixes #15310. (cherry picked from commit bebb9ff)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the expected behavior?
Linear stepper - Able to Move from Step 1 to Step 3 when [completed]="true" is set
What is the current behavior?
Linear stepper -
Need to touch step 2 to be able to move from Step 1 to Step 3 when [completed]="true" is set
What are the steps to reproduce?
https://stackblitz.com/edit/angular-bmwaq7
[completed]="true" is set on all steps.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 7.2.6
Material 7.3.1
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: