-
Notifications
You must be signed in to change notification settings - Fork 9
Description
Current setting on my doc:
clearIcon={null}
Documentation:
clearIcon={} // set null to not render nothing
I can still click on the button even though it is invisible. This is not a big deal for us, but I wanted to let you know. The package is working great otherwise, thank you for creating it.
Additional Issue related: In an effort to "catch" a user trying to delete a date/time by clicking on the invisible delete icon, I have found the following to be true..
If you add some logic to your onChange that essentially does not set the state of the date object of its' value is null (aka user has clicked on the delete button) your state will be preserved. However, the datetimepicker does not render this value. Instead it wipes what the user sees (because the clicked delete) You can check in memory that the value still exists because you stopped them from changing it, but the user will still believe the deleted it. I would suggest removing whatever logic is in place to wipe the "entry field" and instead always show the value that it is fed. OR change the clearIcon functionality to actually not allow them to delete the date object when it is set to null.
I hope this makes sense.