We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug which template:
A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
{ "schema": { "type": "object", "properties": { "first_name": { "type": "string", "floatLabel": "always" } } } }
Expected behavior The 'First Name' label is floated.
Desktop (please complete the following information):
Context This feature is documented as supported, however, I am unable to get it to work.
The text was updated successfully, but these errors were encountered:
It may be worth noting that the following schema shows that the 'textarea' type properly respects the 'floatLabel' property.
{ "schema": { "first_name": { "type": "string" } }, "form": [ { "key": "first_name", "type": "textarea", "placeholder": "Make a comment", "floatLabel": "auto" } ] }
Sorry, something went wrong.
Specifying an appearance of 'legacy' will allow floatLabel to work again.
{ "schema": { "type": "object", "properties": { "first_name": { "type": "string", "appearance": "legacy", "floatLabel": "auto" } } } }
This commit is what caused it to stop working.
However, it is worth noting that this Stackblitz shows that floatLabel should work with the appearance 'standard', so this is still a valid issue.
Stale issue
No branches or pull requests
Describe the bug
which template:
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The 'First Name' label is floated.
Desktop (please complete the following information):
Context
This feature is documented as supported, however, I am unable to get it to work.
The text was updated successfully, but these errors were encountered: