md-toolbar has a delay when used with ng-hide or ng-if

[jelbourn]

See http://jsbin.com/kixicas/1/edit

Removing the transition CSS property on md-toolbar fixes this, but it is not clear why a transition specifically targeting box-shadow would impact this.

[ThomasBurleson]

I think @robertmesserle recently added this shadow transition... not sure why it impacts performance.

[calebegg]

I was actually just debugging a similar problem in our app, and I think the best solution is either to only use transitions that you want ngAnimate to care about (and then only use them in the special classes ng-animate makes) or to use a prefix for ngAnimate:

https://docs.angularjs.org/api/ngAnimate#preventing-collisions-with-third-party-libraries

Though I don't know if it's possible to do that without enforcing it for all angular-material users as well.

[robertmesserle]

I well add a fix for this later. I've had to fix this on other components.
On Fri, May 1, 2015 at 3:29 PM Caleb Eggensperger notifications@github.com
wrote:

I was actually just debugging a similar problem in our app, and I think
the best solution is either to only use transitions that you want ngAnimate
to care about (and then only use them in the special classes ng-animate
makes) or to use a prefix for ngAnimate:

https://docs.angularjs.org/api/ngAnimate#preventing-collisions-with-third-party-libraries

Though I don't know if it's possible to do that without enforcing it for
all angular-material users as well.

—
Reply to this email directly or view it on GitHub
#2663 (comment).

[robertmesserle]

The easy fix is to add transition: none for md-toolbar.ng-animate
On Fri, May 1, 2015 at 4:58 PM Robert Messerle robert.messerle@gmail.com
wrote:

I well add a fix for this later. I've had to fix this on other components.
On Fri, May 1, 2015 at 3:29 PM Caleb Eggensperger <
notifications@github.com> wrote:

I was actually just debugging a similar problem in our app, and I think
the best solution is either to only use transitions that you want ngAnimate
to care about (and then only use them in the special classes ng-animate
makes) or to use a prefix for ngAnimate:

https://docs.angularjs.org/api/ngAnimate#preventing-collisions-with-third-party-libraries

Though I don't know if it's possible to do that without enforcing it for
all angular-material users as well.

—
Reply to this email directly or view it on GitHub
#2663 (comment).