-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(MdInput): placeholders don't float when MdInput value has bound expression #2477
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
Comments
Just confirmed that this will be fixed with #2455.
|
@devversion Wow, thanks for the quick reply!! I haven't found that PR right away, would've otherwise not opened this issue. I'll leave it open though, until #2455 is merged! Thanks so much! |
@PascalPrecht No worries. Thanks for the issue 😄 I will reference your issue, so it will be closed once the PR is merged. |
+ Fixed client api consumption. + upgraded angular/material (still suffers from angular/components#2477)
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. |
Bug, feature request, or proposal:
When binding a value to
MdInput
using an expression,placeholder
attribute (ormd-placeholder
) don't float when value is set, which results in placeholder text + input value to overlap. Also after focussing and blurring the input, the placeholder goes back to its original position. However, when using a static value, it works perfectly fine.What is the expected behavior?
placeholder
attribute (and/orMdPlaceholder
) should float, also when initialMdInput
value comes from an expression.What are the steps to reproduce?
foo="bar"
)MdInput
and give it a placeholder (placeholder="Some Placeholder"
)Here's a Plunk that reproduces the bug: https://plnkr.co/edit/NnwmYrakshZ5DEBkW27D?p=preview
Is there anything else we should know?
There's an issue that might be related to this bug. When setting form values programmatically, placeholder positions also aren't updated. This issue can be found here: #2441
Someone came up with a fix for that as well: crisbeto@72bc742
The text was updated successfully, but these errors were encountered: