Incorrect filter behaviour about customermanagerstandard

[DanWahlin]

Thanks for taking the time to comment - I appreciate it.

That's correct behavior on the filtering for "Jones". It is only designed to filter the existing records that are displayed. Otherwise, as the user types the server would have to be hit with each keystroke which would be expensive. That's because server-side paging is used and only 10 records at a time are loaded into the client. That behavior could certainly be changed if you wanted to only filter after a few characters or on lost focus but the current behavior is what is intended.

There was a bug with filtering though that was caused by the animations that were applied. Since they'd lag, invalid results would show up if a user typed too fast. That's been resolved now by removing the animation class after it runs the first time.