mat-expansion-panel's content shows immediately, outrunning the panel's animation #10134
Assignees
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
kodwi
changed the title
crisbeto
added
P3
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 25, 2018
Fixes expansion panels becoming `overflow: visible` as soon as their expansion animation starts, causing them to show the entire content before they're done animating. It seems like we were setting the `mat-expanded` class both through the view and manually when the animation is done. Fixes angular#10134.
tinayuangao
pushed a commit
that referenced
this issue
Mar 1, 2018
…art (#10138) Fixes expansion panels becoming `overflow: visible` as soon as their expansion animation starts, causing them to show the entire content before they're done animating. It seems like we were setting the `mat-expanded` class both through the view and manually when the animation is done. Fixes #10134.
tinayuangao
pushed a commit
that referenced
this issue
Mar 5, 2018
…art (#10138) Fixes expansion panels becoming `overflow: visible` as soon as their expansion animation starts, causing them to show the entire content before they're done animating. It seems like we were setting the `mat-expanded` class both through the view and manually when the animation is done. Fixes #10134.
|
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.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
The content inside
mat-expansion-panelhas to show synchronously with the panel's animation, without outrunning.What is the current behavior?
The content shows immediately and completly, at the moment when the panel begins to open, bypassing its animation. By the way, if there are several panels, then all of them have the bug, except last one.
What are the steps to reproduce?
https://angular-p1bsmv.stackblitz.io/
https://stackblitz.com/edit/angular-p1bsmv
What is the use-case or motivation for changing an existing behavior?
Incorrect behaviour. There was no such behaviour in the previous versions.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular Material 5.2.2
TypeScript 2.4.2
The bug was reproduced in the last versions of Chrome, FF, Edge, Opera.
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: