Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(select): should have same error behavior as input #5826

Closed
mmalerba opened this issue Jul 17, 2017 · 4 comments
Closed

(select): should have same error behavior as input #5826

mmalerba opened this issue Jul 17, 2017 · 4 comments
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@mmalerba
Copy link
Contributor

select's error state is not affected by form submit, select also doesn't support error messages (see: http://plnkr.co/edit/4nJFdsq4Z4ckpLfHVkAt?p=preview)

@mmalerba mmalerba added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Jul 17, 2017
@crisbeto
Copy link
Member

I've sorted out the error state in #4754.

@mmalerba
Copy link
Contributor Author

awesome!

@mmalerba
Copy link
Contributor Author

mmalerba commented Jul 17, 2017

closing as dup of #4611

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

3 participants