-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
bug(animations): false
(0) state is being confused as "void"
in transitions in 4.0.0-rc.4
#15223
Comments
After digging around more, i notice that its confusing Notice the transitions are going from Created a plnkr so its easier to notice: |
*
auto-style stopped working in 4.0.0-rc.3false
state is being confused as "void"
in transitions in 4.0.0-rc.3
false
state is being confused as "void"
in transitions in 4.0.0-rc.3false
(0) state is being confused as "void"
in transitions in 4.0.0-rc.3
Renamed the issue since the |
This will be fixed tomorrow. |
Pulled |
false
(0) state is being confused as "void"
in transitions in 4.0.0-rc.3false
(0) state is being confused as "void"
in transitions in 4.0.0-rc.4
This is now waiting to go in: #15245 |
Awesome @matsko. looking forward for 4.0.0 😄 |
Just you wait until 4.1.0-beta and you'll get some crazy new stuff ;) |
Oh snap! extra excited 💥 haha |
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. |
I'm submitting a ... (check one with "x")
Current behavior
The
*
auto-style wildcard stopped working when upgrading the @angular@4.0.0-rc.3 and the element keeps theopacity
at0
anddisplay
atnone
even after animating. (also the returning transition is not working)e.g.
Expected behavior
It was working in
2.X.X
without any issues. Should setopacity
to0
anddisplay
tonone
whentrigger
isfalse
and should setopacity
anddisplay
to whatever it was whentrigger
istrue
while animating betweenopacity
.Minimal reproduction of the problem with instructions
Plnkr with issue: https://plnkr.co/edit/IGvg3RIcdVtfhOV9M0sI?p=preview
What is the motivation / use case for changing the behavior?
Working animations are broken now.
Angular version: 4.0.0-rc.3
Browser: all
The text was updated successfully, but these errors were encountered: