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

docs(guide/Animations): describe your change... #14900

Closed
wants to merge 2 commits into from
Closed

docs(guide/Animations): describe your change... #14900

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
970d673
docs(guide/Animations): describe your change...
Deklin Jul 12, 2016
d887444
Update animations.ngdoc
Deklin Jul 12, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/content/guide/animations.ngdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -313,8 +313,8 @@ This function can be used to enable / disable animations in two different ways:
With a single `boolean` argument, it enables / disables animations globally: `$animate.enabled(false)`
disables all animations in your app.

When the second argument is a native DOM or jQuery element, the function enables / disables
animations on this element *and all its children*: `$animate.enabled(false, myElement)`. This is the
When the first argument is a native DOM or jQuery element, the function enables / disables
animations on this element *and all its children*: `$animate.enabled(myElement, false)`. This is the
most flexible way to change the animation state. For example, even if you have used it to disable
animations on a parent element, you can still re-enable it for a child element. And compared to the
`classNameFilter`, you can change the animation status at runtime instead of during the config phase.
Expand Down