From 54637a335f885110efaa702a3bab29c77644b36c Mon Sep 17 00:00:00 2001
From: Matias Niemelä
Date: Sat, 14 Dec 2013 00:30:48 -0500
Subject: fix($animate): use a scheduled timeout in favor of a fallback
 property to close transitions

With ngAnimate, CSS transitions, that are not properlty triggered, are forceably closed off
by appling a fallback property. The fallback property approach works, however, its styling
itself may effect CSS inheritance or cause the element to render improperly. Therefore, its
best to stick to using a scheduled timeout to run sometime after the highest animation time
has passed.

Closes #5255
Closes #5241
Closes #5405
---
 css/angular.css | 11 -----------
 1 file changed, 11 deletions(-)

(limited to 'css')

diff --git a/css/angular.css b/css/angular.css
index 3e20a999..b88e61e4 100644
--- a/css/angular.css
+++ b/css/angular.css
@@ -9,14 +9,3 @@
 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 border-spacing (!ie) and zoom (ie) CSS properties are
- * used below since they trigger a transition without making the browser
- * animate anything and they're both highly underused CSS properties */
-.ng-animate-start { border-spacing:1px 1px; -ms-zoom:1.0001; }
-.ng-animate-active { border-spacing:0px 0px; -ms-zoom:1; }
-- 
cgit v1.2.3