Background
This issue replaces #3646, which originally proposed hiding the clear button on required date-pickers. After discussion, we concluded that blocking users from clearing values isn't good UX.
What should happen
limel-date-picker should have internal validation similar to limel-select (see commit 04af5d9).
When a date-picker is:
- marked as
required
- initially empty or has a value cleared by the user
- and the user has interacted with it
...the component should automatically become invalid.
This allows forms to properly block submission when required date fields are empty, without preventing users from clearing values (which would be poor UX).
Related
Background
This issue replaces #3646, which originally proposed hiding the clear button on required date-pickers. After discussion, we concluded that blocking users from clearing values isn't good UX.
What should happen
limel-date-pickershould have internal validation similar tolimel-select(see commit 04af5d9).When a date-picker is:
required...the component should automatically become
invalid.This allows forms to properly block submission when required date fields are empty, without preventing users from clearing values (which would be poor UX).
Related