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
Currently it is not possible to set a placeholder on a textfield with float label, because the float label collides with the placeholder when the field ist empty.
Initially it was a Bug and it seems there was some action to fix it but then whole work was cancelled with the explanation that floating labels should not be used with placeholders.
This is not only a breaking change from the previous behaviour, but IMHO also an incorrect interpretation of labels and placeholders. Labels (and therefore floating labels too) are supposed to describe the input content and placeholders are giving a hint or example, mostly about the correct format. There is also a broad agreement about not replacing labels with placeholders because of screenreader behavior.
Also from a library quality standpoint it is not best practice to have properties that collides visually.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently it is not possible to set a placeholder on a textfield with float label, because the float label collides with the placeholder when the field ist empty.
Initially it was a Bug and it seems there was some action to fix it but then whole work was cancelled with the explanation that floating labels should not be used with placeholders.
This is not only a breaking change from the previous behaviour, but IMHO also an incorrect interpretation of labels and placeholders. Labels (and therefore floating labels too) are supposed to describe the input content and placeholders are giving a hint or example, mostly about the correct format. There is also a broad agreement about not replacing labels with placeholders because of screenreader behavior.
Also from a library quality standpoint it is not best practice to have properties that collides visually.
Kind regards
Beta Was this translation helpful? Give feedback.
All reactions