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

fix(input): Fix message animation not running. #9044

Closed

Conversation

topherfangio
Copy link
Contributor

@topherfangio topherfangio commented Jul 15, 2016

If an input switched from one error state directly to another error
state, the second error animation would fail.

Update input animation code to handle this situation and be
drastically cleaner and fix a bug in getMessagesElement()
method which disallowed multiple ng-messages elements.

Fixes #8635. Fixes #8864. Fixes #8973.

@topherfangio topherfangio added in progress Mainly for in progress PRs, but may be used for issues that require multiple PRs needs: work labels Jul 15, 2016
@topherfangio topherfangio self-assigned this Jul 15, 2016
@topherfangio topherfangio force-pushed the fix-inputs-messages-8864 branch 3 times, most recently from 359aee4 to 1279670 Compare July 18, 2016 21:13
@ThomasBurleson
Copy link
Contributor

@topherfangio - can rebase and verify this is working and ready ?

@topherfangio topherfangio force-pushed the fix-inputs-messages-8864 branch from 1279670 to 7434da8 Compare July 25, 2016 21:20
@topherfangio topherfangio added needs: review This PR is waiting on review from the team and removed needs: work labels Jul 25, 2016
@topherfangio
Copy link
Contributor Author

@ThomasBurleson This is ready for review; particularly seeing whether to use Protractor or Karma. Once we decide, we can delete the other ones if we want.

Also note that this switches to PhantomJS2. This was required to get the Karma tests passing.

@topherfangio topherfangio force-pushed the fix-inputs-messages-8864 branch from 7434da8 to 2849026 Compare July 26, 2016 13:26
If an input switched from one error state directly to another error
state, the second error animation would fail.

Update input animation code to handle this situation and be
drastically cleaner and fix a bug in  `getMessagesElement()`
method which disallowed multiple `ng-messages` elements.

Fixes angular#8635. Fixes angular#8864. Fixes angular#8973.
@topherfangio topherfangio force-pushed the fix-inputs-messages-8864 branch from 2849026 to 90f67c7 Compare July 26, 2016 16:47
@longrunningprocess
Copy link

just curious whether this will be a candidate for the 1.1.0 release?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
in progress Mainly for in progress PRs, but may be used for issues that require multiple PRs needs: review This PR is waiting on review from the team
Projects
None yet
3 participants