openui5
openui5 copied to clipboard
Add a property disabling manual input of `sap.m.DatePicker`
OpenUI5 version: 1.98.0
Currently, sap.m.DatePicker allows both manual user input and selecting a date from a popover.
In order to avoid the potential date formatting issues (e.g. DD.MM.YYYY vs. MM/DD/YYYY) caused by user manual input, it would be great to be able to disable manual input, leaving just option of selecting a date from a popover. More generally, to add a property (e.g. disableManualInput) to all input controls, which have a helper popover.
Of course, there can be developed some workarounds with CSS / JS, but it would be great to have such boolean property, which can set either via XML-template or view controller. And yes, it can be bypassed with the DevTools, therefore such property might be useful for the UX purposes only.
Hello pubmikeb,
thank you for submitting this feature request. I have forwarded the details to the corresponding development team and they will contact you as soon as possible. The internal reference ID is 2170295664.
Regards Sebastian
This issue will be covered in backlog item BGSOFUIBALKAN-5998.
Hi Team currently I've the same issue. Is there any update? Really need a property for disable manual input in sap.m.DatePicker. Thank you, Amrita
How would that affect copy & paste? What does it mean for accesibility to force users into the value help dialog, which is optimized for mouse, instead of just typing? What about power users? Have you taken all of that into account?
How would that affect copy & paste? What does it mean for accessibility to force users into the value help dialog, which is optimized for mouse, instead of just typing? What about power users? Have you taken all of that into account?
It's more to ensure the proper date format provided by user, of course, on a backend the input should be validated, since it can be changed via DevTools, but normally help value should minimize the typos by manual input, which is especially relevant for date format.
Hi @HerzogIgzorn and Team,
Is the feature available?
Hello @jeniferranjini,
the feature is planned in our backlog but is not yet assigned to any active development sprint. I'm afraid, you will have to wait a little longer. The responsible development team will update this GitHub issue as soon as it is available.
Regards Sebastian