Input controls are often used in forms or property editor dialogs. Often the user is required to provide an input to the control before the form can be submitted or before the property changes can be saved.
With Nimble controls today, client applications will manually add … (Required) to the control's placeholder text or to the label.
We need to provide a standardized way for the application to let the end-user know that a control is required.
Input controls:
Combobox
Number Field
Radio Group
Select
Text Area
Text Field
🎯 Core Requirements
Component needs to have a visual indication that the control is required. Could be an * or … (Required) added to label.
🎨 Visual Design Request
📌 Request Background
Input controls are often used in forms or property editor dialogs. Often the user is required to provide an input to the control before the form can be submitted or before the property changes can be saved.
With Nimble controls today, client applications will manually add
… (Required)to the control's placeholder text or to the label.We need to provide a standardized way for the application to let the end-user know that a control is required.
Input controls:
🎯 Core Requirements
*or… (Required)added to label.🍆 Non-requirements
Don't need to support:
🥅 Acceptance Criteria