-
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
Bug: md-prefix stretches together with input field #2493
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jan 2, 2017
Prevents the input's suffix and prefix from stretching together with their parent node and leaving some weird spacing between themselves and the input. This was a side-effect of using `display: table-cell`. Fixes angular#2493.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jan 5, 2017
Prevents the input's suffix and prefix from stretching together with their parent node and leaving some weird spacing between themselves and the input. This was a side-effect of using `display: table-cell`. Fixes angular#2493. Fixes angular#1881. Fixes angular#1421.
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.
When I put prefix in a wide md-input-container, the prefix stretches together with it.
Easy to reproduce. Just make the md-input-container wide enough:
<md-input-container class="full-width">
<span md-prefix>#</span>
<input md-input formControlName="tagInput" placeholder="Tags>
</md-input-container>
Have a look at the copyright and hash prefixes here:
I believe prefixes should stay the same width not dependent on the parent width.
Another thing (not sure if it was already mentioned) - fields disabled via code .disable() do not display as dotted. Also visible on the screenshot (field to the left of checkbox is actually disabled).
The text was updated successfully, but these errors were encountered: