Sure, the readonly is so that the user cannot modify the actual text input (and perhaps put something in that is invalid). It forces them to use the UI. Also, it prevents the soft keyboard from popping up on mobile.
I have the same thing going on but with Firefox…
In my 3.9.7 based app, the time picker is never working in Firefox, but it works on all the other browsers.
In my v6 beta based app, one time picker in particular (but not all of them) is also not working in Firefox.
(This is using quite an old v6 beta… you can check out which one in the js package)
@patrick, I’ll DM you the details to take a look…
The Datepicker component is a wrapper around the Date Range Picker, perhaps you can test the picker from the original site and see if it works there. The datepicker isn’t maintained anymore since the last 4 years, also don’t see any good alternatives for the picker and the current version just works good.
it will change where the datepicker popup is placed in the DOM, when the datepicker is in a modal it will place the popup also in the modal so that the modal focus trap doesn’t prevent the focus on the elements in the popup.
Could you test the datepicker outside of a modal to see if touch works correctly. @Antony did send me a test page for his Firefox problem and there I could verify that it was the modal that was causing the problem.
Also you may want to test with the Beta channel, the datepicker is updated there to work correctly within modals.