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
We would like to request the ability to define custom sizes for the Textarea field type in JSON schema. This feature would allow developers to specify the expected size of the input area, specially height, directly in the JSON configuration. The goal is to improve the user experience by visually indicating the expected amount of input text. For example, a larger textarea would signal to the user that they are expected to write a more detailed response.
Use Case:
When creating forms, certain fields may require long responses, such as feedback forms, comment sections, or descriptions.
A small default textarea can be misleading, causing users to feel constrained or unsure about the level of detail they should provide.
By enabling customization, developers can better guide the end user and enhance the overall usability of forms.
Additional Notes: If implemented, this feature should gracefully fall back to default dimensions when no custom size is provided, ensuring backward compatibility with existing JSON schemas.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Description
We would like to request the ability to define custom sizes for the Textarea field type in JSON schema. This feature would allow developers to specify the expected size of the input area, specially height, directly in the JSON configuration. The goal is to improve the user experience by visually indicating the expected amount of input text. For example, a larger textarea would signal to the user that they are expected to write a more detailed response.
Use Case:
When creating forms, certain fields may require long responses, such as feedback forms, comment sections, or descriptions.
A small default textarea can be misleading, causing users to feel constrained or unsure about the level of detail they should provide.
By enabling customization, developers can better guide the end user and enhance the overall usability of forms.
Additional Notes: If implemented, this feature should gracefully fall back to default dimensions when no custom size is provided, ensuring backward compatibility with existing JSON schemas.
Additional Information
No response
The text was updated successfully, but these errors were encountered: