Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

fix(modal): add $animateCss support #4121

Closed
wants to merge 1 commit into from

Conversation

wesleycho
Copy link
Contributor

  • Add support for $animateCss

The carousel change is to safely detect whether $animateCss is truly present (if the user is not using ngAnimate, then this would throw an exception before this patch.

The modal change is to correctly use $animateCss - this can be observed in action here.

I am currently still investigating #4119, and hopefully will be able to patch that up on top of this or as a part of this PR. These changes are not enough to fix the broken behavior, as can be seen here.

- Add support for `$animateCss`
@wesleycho wesleycho force-pushed the fix/modal-animateCss branch from 0d5e619 to 46f120d Compare August 6, 2015 03:34
@wesleycho
Copy link
Contributor Author

I updated the Plunker, with usage from the snapshot version of Angular, due to a major ngAnimate fix that is currently not released. This is still currently broken in 1.4.3, but only with the indicators and controls being missing. That part will be fixed with the release of 1.4.4.

@icfantv
Copy link
Contributor

icfantv commented Aug 6, 2015

LGTM

@mattlewis92
Copy link
Contributor

FYI you can use $injector.has('$animateCss') instead of using the try catch to detect if $animateCss is available

@wesleycho
Copy link
Contributor Author

I should have checked the docs...I never knew that existed - thanks for that tidbit, I will refactor that now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants