aboutsummaryrefslogtreecommitdiffstats
path: root/css
diff options
context:
space:
mode:
authorMatias Niemelä2013-10-31 14:09:49 -0700
committerMatias Niemelä2013-11-05 21:45:36 -0500
commitb89584db10b63f346cbfd03f67fb92504e5bf362 (patch)
tree05fc8dfd1ca1aa49223be3c03e0ba762acfdc5f2 /css
parent41a2d5b30f4feb90651eb577cf44852a6d2be72c (diff)
downloadangular.js-b89584db10b63f346cbfd03f67fb92504e5bf362.tar.bz2
fix($animate): avoid hanging animations if the active CSS transition class is missing
Closes #4732 Closes #4490
Diffstat (limited to 'css')
-rw-r--r--css/angular.css11
1 files changed, 11 insertions, 0 deletions
diff --git a/css/angular.css b/css/angular.css
index b88e61e4..46fee32d 100644
--- a/css/angular.css
+++ b/css/angular.css
@@ -9,3 +9,14 @@
ng\:form {
display: block;
}
+
+/* The styles below ensure that the CSS transition will ALWAYS
+ * animate and close. A nasty bug occurs with CSS transitions where
+ * when the active class isn't set, or if the active class doesn't
+ * contain any styles to transition to, then, if ngAnimate is used,
+ * it will appear as if the webpage is broken due to the forever hanging
+ * animations. The clip (!ie) and zoom (ie) CSS properties are used
+ * since they trigger a transition without making the browser
+ * animate anything and they're both highly underused CSS properties */
+.ng-animate { clip:rect(1px, auto, auto, 0); -ms-zoom:1.0001; }
+.ng-animate-active { clip:rect(0, auto, auto, 0); -ms-zoom:1; }