I have several input date widgets that have On Change events that look at the value of the widget and execute tasks like hiding or highlighting itself other widgets. But I am getting exceptions when the on change event fires before the user has completed typing in the date.
Is there a way to trap that the date isn't complete OR trap the exception and have it not show an error message and resume the client action?
When the on change action fires when the date isn't complete, it shows as a null date. That would be a good way to trap except that a null date is valid for all of these data elements.
Hi Jeff,
OnChange will be triggered whenever the input value is changed... A good option is to use event right below OnChange and select OnBlur, which will trigger after the user "leaves" the input.
Another good option is the Debounce component... It is very useful to define an interval in milliseconds for the onchange to be triggered. Especially if the user types the date instead of selecting the date from the Date PickerDebounce Forge Component
You can use Interactive Datepicker from OSUI. It provides more configurable options as well as events.
- Niranjan
Does it allow entering dates via typing? I don't want the users to have to navigate calendars.
Yes it does!