{"push_id":621968768,"size":1,"distinct_size":1,"ref":"refs/heads/ng_animate_blocking_fix","head":"93308285a43d705d4ee37bba3b870b0be2a1b3a7","before":"cdcc6b5aa96f51a5cb06f6485e79b2ae896f5087","commits":[{"sha":"93308285a43d705d4ee37bba3b870b0be2a1b3a7","author":{"email":"dbc6bbe3b711e3f58f25638428fdfc12e34c8c38@yearofmoo.com","name":"Matias Niemelä"},"message":"fix(ngAnimate): use negative delay values to drive animation blocking\n\nwhen CSS transitions are used via ngAnimate a pre-emptive \"block\" is\napplied to the element (via `transition: 0s none`) in order to gaurantee\nthat the `.ng-enter`, `.ng-leave` and/or `.ng-move` CSS classes are\napplied instantly. By setting `0s none` we gaurantee that the styles\npresent within these classes actually appear on the element. While this\nworks it causes a major issue with CSS classes where the base CSS class\nalready contains an transition, when the active class has a transition\nor if the element already has an active playing transition.\n\nThis fix makes use of negative delay values in transitions to handle\nthis blocking mechanism yet it doesn't cause the issues that setting the\ntransition to `0s none` causes.\n\nCloses #11481","distinct":true,"url":"https://api.github.com/repos/matsko/angular.js/commits/93308285a43d705d4ee37bba3b870b0be2a1b3a7"}]}