Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Commit 947a44d

Browse files
committed
chore(docs): specify how ngClass deals with natural CSS transitions
1 parent eb51b02 commit 947a44d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/ng/directive/ngClass.js

+4-4
Original file line numberDiff line numberDiff line change
@@ -193,10 +193,10 @@ function classDirective(name, selector) {
193193
194194
## ngClass and pre-existing CSS3 Transitions/Animations
195195
The ngClass directive still supports CSS3 Transitions/Animations even if they do not follow the ngAnimate CSS naming structure.
196-
Therefore, if any CSS3 Transition/Animation styles (outside of ngAnimate) are set on the element, then, if a ngClass animation
197-
is triggered, the ngClass animation will be skipped so that ngAnimate can allow for the pre-existing transition or animation to
198-
take over. This restriction allows for ngClass to still work with standard CSS3 Transitions/Animations that are defined
199-
outside of ngAnimate.
196+
Upon animation ngAnimate will apply supplementary CSS classes to track the start and end of an animation, but this will not hinder
197+
any pre-existing CSS transitions already on the element. To get an idea of what happens during a class-based animation, be sure
198+
to view the step by step details of {@link ngAnimate.$animate#methods_addclass $animate.addClass} and
199+
{@link ngAnimate.$animate#methods_removeclass $animate.removeClass}.
200200
*/
201201
var ngClassDirective = classDirective('', true);
202202

0 commit comments

Comments
 (0)