You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
I ran into this issue today, and my investigation is as follows:
This issue is triggered when the body element is not contained by the ng-app. When the $animate service is checking if any of the elements inside the modal can be animated the checks inside the angular-animate animationsDisabled() function fail as those element are not inside the $rootElement of the ng-app.
In this plunkr I have moved the ng-app on to the body element and the animations inside the modal now work.
Given the nature of this problem, I don't think there is anything that should be done by Angular or UI Bootstrap. I would even go as far as to say there is likely no reason not to have the ng-app on <body> or <html>, or just manually bootstrapping on document. The modal is currently set up to append to the body element by default, which is necessary for CSS reasons - there is a feature request to allow the user to configure appending to a particular element, which we will implement at some point for accessibility reasons, but otherwise this would be a breaking change with larger ramifications.
angular's animation hooks don't exist on elements within a bootstrap modal...
any idea on a workaround?
I made a plunker:
UPDATE:
@wesleycho I stripped down the plunker a little bit:
http://plnkr.co/edit/9AXi1I7P7YN7wqMS8RDS?p=preview
The text was updated successfully, but these errors were encountered: