1.1.5 breaks ngClick when used in combination with ngAnimate and ngShow

[jasadams]

There is a bug introduced in 1.1.5 when you have a html element set up with directives like the following.

<button ng-show="showButton"
        ng-click="setText('with animate')" 
        ng-animate="{show: 'fade-show', hide: 'fade-hide'}">
          With Animate
</button>

The animation works fine, but the ngClick directive stops working once the element has been hidden by the ngShow directive.
Here is the plunkr using 1.1.5 demonstrating the issue. Here is the plunkr using 1.1.4 showing that the bug doesn't exist

[rafaelwmartins]

Indeed. Same problem here.

[mikaraento]

Ran into this too. For my case I was able to work around it by putting the ng-click on a dummy enclosing element.

[smdvdsn]

I think this effects ng-animate with other directives as well. I've tested ng-repeat, ng-if and ng-show and they all have the issue. See issue #2566

[petebacondarwin]

@matsko & @mhevery - this seems like a valid and quite serious regression.

[petebacondarwin]

This has been fixed in master: e1a050e
ngAnimate was calling element.removeData() but there was a bug in the jqLite version that caused it to unbind all the events on that element.
You can see that is works if you use jQuery rather than jqLite here: http://plnkr.co/edit/pRfeFf2vFdtjuZ8TvkQO?p=preview
And you can see that it is now working if you use a recent build on master: http://plnkr.co/edit/GKsaVhKaLWCF9o6Hyofq?p=preview