-
Notifications
You must be signed in to change notification settings - Fork 3.4k
angular-material breaks our app by just being included as a dependency #3941
Comments
@smashercosmo It's an issue with your directives. There is a name confict. Rename (namespace) your directives that are affected and it works. |
@robertbaker no, it's not. I updated plunker with renamed (namespaced) directives. still not working. |
@smashercosmo I believe it's an issue with Angular 1.4 and angular-material specifically. I changed versions of angular to 1.3.10 in your plunker and it seems to work. I recall this library also having an issue with 1.4 animation and if I recall, they rolled back to require an older version of angular? Maybe someone else can chime in here. |
@smashercosmo - The issues that ngMaterial has with ngAnimate should all be solved once the PR #3949 has been merged into master.
|
@ThomasBurleson just want you to know, I've just tested with latest master, that includes #3949, but issue is still not resolved :( |
@smashercosmo - this appears to be an edge-case issue with $animate and ngMaterial. See Plunkr Demo and the
|
Fixed with recent Angular.JS master build/snapshot: http://plnkr.co/edit/hQ2Q6y5Qi72fePI1VrUl?p=preview |
Here is a simple plunker that illustrates an issue. We have a transcluded form with ng-repeat inside and custom validation directive on inputs. Form has an ng-show directive, but as you will see it is always hidden.
Only combination of these four causes the form to not show up.
The text was updated successfully, but these errors were encountered: