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.
π Feature Request
π― Problem to Solve
Visual design requested here.
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:
Don't need to support:
π Proposed Solution
https://www.w3schools.com/tags/att_input_required.asp
Per the visual design, we should add a
required
attribute to each input control that enables or disables the display of the visual state.Need compatibility with existing Angular form validation patterns.
π Tasks