-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Closed
Description
Bug, feature request, or proposal:
Bug.
What is the expected behavior?
The select control should prioritize its own valid flag over the form's invalid flag
What is the current behavior?
ng-select shows invalid state if the form is marked as ng-invalid even when the select itself has the ng-valid class
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker: http://plnkr.co/edit/wLkZWMBZs0gngUmkMJHn?p=preview
I fudged the classes to simplify the plunkr
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
I noticed this on 11-3 but I believe the plunkr uses the master version which still has this behaviour
Is there anything else we should know?
Metadata
Metadata
Assignees
Labels
No labels