-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Chips placeholder bound to variable only shows after triggering its change detection (by clicking component). #11861
Labels
P4
A relatively minor issue that is not relevant to core functions
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 28, 2018
…ed to form field Fixes changes to the placeholder of a chip input not being propagated to its parent form field. Also un-deprecates the input for `placeholder`, because we need to know when it has changed. Fixes angular#11861.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 30, 2018
…ed to form field Fixes changes to the placeholder of a chip input not being propagated to its parent form field. Also un-deprecates the input for `placeholder`, because we need to know when it has changed. Fixes angular#11861.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
If you have a chips component roughly like the following (check stackblitz for a working example). The placeholder will not render as expected (hide on disabled true; show on disabled false) until you somehow trigger change detection by clicking the component.
What is the current behavior?
Only shows placeholder (for disabled === false) after user triggers change detection.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-hxrcpk
Other similar example:
https://stackblitz.com/edit/angular-hxrcpk-3zsauz
What is the use-case or motivation for changing an existing behavior?
Showing/hiding placeholder based on component's disabled input parameter.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: 6.0.5
Material 6.0.3
Is there anything else we should know?
This is not a new behaviour, it already happened in past material major versions.
The text was updated successfully, but these errors were encountered: