I’m hoping I’m just missing something but it could be a little bug/feature that needs adding…
Whenever an input is set as a datepicker selecting it on mobile (tested with IOS) the keyboard is shown and gets in the way of the picker. If you have the time element selected, it can be almost impossible to get to if the picker is on a modal:
It would be good if there could be an option to force virtual keyboards to stay closed. From some very quick reading, some libraries set the text field to readonly to overcome this with the datepicker still initialising when clicked. I’m not sure whether this would work with the DMX datepicker.
Are you sure setting readonly="true" to the datepicker doesn’t fix this?
Tested this on an Android phone (Samsung Galaxy S10) just now and it seems to be working fine.
Do you know what… it’s too early and I clearly need more coffee! You’re right Teodor, setting that does the trick.
However… I didn’t think through the follow on impact for desktop if set to readonly. On desktop you then can’t type in the value which is useful for those users. Is there a way to target virtual keyboards to stay closed?
