This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(ngAnimate): make sure that the class value passed into addClass/r…
…emoveClass is the base class string value
- Loading branch information
Showing
2 changed files
with
137 additions
and
104 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2430347
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI I am still experiencing poor
ngRepeat
performance. There is flashing and it appears like there are one-too-many $digest cycles being performed (this is just a guess)? Basically sometimes I will see elements momentarily flash into view that should no longer be in thengRepeat
list -- this occurs when I change the array of items in the list to a new array. And for a list with 50 items they take a second to appear into view initially. This quirky behavior only occurs when I havengAnimate
as a dependency.2430347
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's a plunkr that shows the problem clearer than my last one: http://plnkr.co/edit/udltDOfGBWBGrBP1spEK?p=preview
The above plunkr shows how re-assigning the array used for
ngRepeat
withngAnimate
as a dependency causes weird flashing of thengRepeat
items, which doesn't occur when you remove thengAnimate
dependency.2430347
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@matsko @mhevery @IgorMinar Hey guys, just want to make sure you're aware of the above issue that I posted. It looks like you're gearing up for a release soon, and I don't want to see it ship with an unusable
ngAnimate
module that will keep me and anybody else who usesngAnimate
withngRepeat
on 1.1.5