You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug: if the input field is cleared with reset after being changed, the placeholder is not displayed. Feels like it should if the field is empty and marked as untouched.
Following steps to reproduce:
Using reactive forms.
Create an input field (md-input) with placeholder set to some text inside md-input-container .
On some event (e.g.) checkbox selected - reset the input.
Now two cases:
If placeholder is floatingPlaceholder it stays above (though should go down if field is reset)
If placeholder is not floatingPlaceholder it is not displayed at all (though it should be)
I was making a form where the input should get cleared and disabled once checkbox is selected. And default value (e.g. placeholder) should be displayed instead of the text in the input. Spent all day trying to figure out how it can be solved. Didn't find a way.
"@angular/material": "^2.0.0-beta.1", Chrome
The other thing which also feels as quite weird behaviour:
When input is programmatically disabled via reactive forms, the border is not becoming dotted. The same setup as above.
The text was updated successfully, but these errors were encountered:
Bug: if the input field is cleared with reset after being changed, the placeholder is not displayed. Feels like it should if the field is empty and marked as untouched.
Following steps to reproduce:
Using reactive forms.
I was making a form where the input should get cleared and disabled once checkbox is selected. And default value (e.g. placeholder) should be displayed instead of the text in the input. Spent all day trying to figure out how it can be solved. Didn't find a way.
"@angular/material": "^2.0.0-beta.1", Chrome
The other thing which also feels as quite weird behaviour:

When input is programmatically disabled via reactive forms, the border is not becoming dotted. The same setup as above.
The text was updated successfully, but these errors were encountered: