Ability to imperatively float md-input placeholder #2466
Assignees
Labels
feature
This issue represents a new feature or feature request rather than a bug or bug fix
Comments
kara
added
the
feature
devversion
added a commit
to devversion/material2
that referenced
this issue
Jan 10, 2017
Refactors the `[floatingPlaceholder]` input to be able to specifiy whether the label should always float or not. There are three options for the `floatingPlaceholder` input binding now - If set to `true`, the placeholder will *always* float - If set to `false`, the placeholder will *never* float - If set to `null`, the placeholder will float if text is entered. Closes angular#2466
devversion
added a commit
to devversion/material2
that referenced
this issue
Jan 10, 2017
Refactors the `[floatingPlaceholder]` input to be able to specifiy whether the label should always float or not. There are three options for the `floatingPlaceholder` input binding now - If set to `true`, the placeholder will *always* float - If set to `false`, the placeholder will *never* float - If set to `null`, the placeholder will float if text is entered. Closes angular#2466
devversion
added a commit
to devversion/material2
that referenced
this issue
Jan 14, 2017
Refactors the `[floatingPlaceholder]` input to be able to specifiy whether the label should always float or not. There are three options for the `floatingPlaceholder` input binding now - If set to `true`, the placeholder will *always* float - If set to `false`, the placeholder will *never* float - If set to `null`, the placeholder will float if text is entered. Closes angular#2466
devversion
added a commit
to devversion/material2
that referenced
this issue
Jan 27, 2017
Refactors the `[floatingPlaceholder]` input to be able to specifiy whether the label should always float or not. There are three options for the `floatingPlaceholder` input binding now - If set to `true`, the placeholder will *always* float - If set to `false`, the placeholder will *never* float - If set to `null`, the placeholder will float if text is entered. Closes angular#2466
devversion
added a commit
to devversion/material2
that referenced
this issue
Feb 1, 2017
Refactors the `[floatingPlaceholder]` input to be able to specifiy whether the label should always float or not. There are three options for the `floatingPlaceholder` input binding now - If set to `true`, the placeholder will *always* float - If set to `false`, the placeholder will *never* float - If set to `null`, the placeholder will float if text is entered. Closes angular#2466
devversion
added a commit
to devversion/material2
that referenced
this issue
Feb 1, 2017
Refactors the `[floatingPlaceholder]` input to be able to specifiy whether the label should always float or not. There are three options for the `floatingPlaceholder` input binding now - If set to `true`, the placeholder will *always* float - If set to `false`, the placeholder will *never* float - If set to `null`, the placeholder will float if text is entered. Closes angular#2466
kara
pushed a commit
that referenced
this issue
Feb 3, 2017
|
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.
Currently there is a
floatingPlaceholderproperty onmd-input-containerthat controls whether or not you'd like a floating placeholder at all. This property effectively disables the floating placeholder.However, it's not meant to be an imperative way to toggle the floating placeholder on and off. If you try to set
floatingPlaceholderto true, it doesn't actual float it. It will still be gated on the two conditions that the value must not be empty or the input must be focused.We should add a way to actually toggle the placeholder, not just disable it. The motivation for this change is the autocomplete. Sometimes the text field will be empty and unfocused (e.g. if you are keying down through the option list), but the placeholder shouldn't reset.
cc @mmalerba
The text was updated successfully, but these errors were encountered: