MDBootstrap staff commented 5 years ago

Oh, sorry. That is because of editable: true option in the picker. I believe that merging this 2 functionalities together is really unintuitive for the users because when you actually want to edit something you should click on this specific field to type in your changes and that's why we didn't expect such functionality. I think that you can change the behaviour of this component to serve your needs but we do not support wrong UX practice and I can't change this component behaviour according to what you request. I hope you understand me.

root-nine priority commented 5 years ago

Well I don´t think it´s unintuitive. We have a lot of customers who prefer working with the keyboard, others prefer working with the mouse. So with the two options mixed I can serve both needs. I have our application in production environment with MDB 4.7.6 where this setting is working and that currently stops me from upgrading to 4.8.8.

MDBootstrap staff commented 5 years ago

I understand. If you want to change the behaviour of this component and still have the same functionality you can modify this part of mdb.js package or work with double-clicking on the input. You can always programmatically trigger 2nd click on 1st click if you want to have a quick fix to this issue without modifying any source code. Sorry for the inconvenience. We didn't plan this 2 functionalities working together. I will see if we can modify this to serve this functionality in the future.