-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Closed
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentfeatureThis issue represents a new feature or feature request rather than a bug or bug fixThis issue represents a new feature or feature request rather than a bug or bug fix
Description
Bug, feature request, or proposal:
feature request
What is the expected behavior?
There should be something similar to the md-input-container which does not depend on a input control inside, so that the benefits for styling error states, using md-error and md-hint can easily be used for custom form controls.
What is the current behavior?
md-input-container has a very limited support for form-controls.
What are the steps to reproduce?
Read the docs :-)
What is the use-case or motivation for changing an existing behavior?
When using md-input-container it's really easy to have those nice animated md-error hints and invalid highlight. It's not that easy to get angular to adding the ng-invalid, ng-dirty and so on classes to a parent element like the md-input-container. So creating a similar look and feel for custom controls can be hard.
It would be very cool to use md-input-container for anything.
<md-input-container>
<my-cool-control mdInput></my-cool-control>
<md-error>User did something wrong</md-error>
</md-input-container>
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
ng 4.1.x, md beta 5
Is there anything else we should know?
arciisine, YeomansIII, ruslan-simonenko, aldo-roman, dschnelldavis and 4 more
Metadata
Metadata
Assignees
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentfeatureThis issue represents a new feature or feature request rather than a bug or bug fixThis issue represents a new feature or feature request rather than a bug or bug fix