Closed pedromagueija closed 3 years ago
Hello @pedromagueija ,
Thank you for sharing this finding. I've created an internal incident 2070389230. The status of the issue will be updated here in GitHub.
Regards, Petar
Hi @pedromagueija ,
This issue is already fixed and the fix is included in version 1.83.
Best Regards, Nikolay Hristov UI5 Developer
@pedromagueija @dimovpetar @NHristov-sap
Hello guys,
There is no 24 in the time conventions in primitive types. In the documentation it is clear the primitive types to be worked in sapui5. This was not a bug and is causing rework for many customers around the world who follow the conventions. I suggest changing the 24 to 00 in the UI, which is the most common in all UI tools. Or return to the convention as it was before.
https://sapui5.hana.ondemand.com/#/topic/e1ddc69c01474faf830a522db8c9238a
https://sapui5.hana.ondemand.com/#/topic/07e4b920f5734fd78fdaa236f26236d8.html
https://sapui5.hana.ondemand.com/#/topic/07e4b920f5734fd78fdaa236f26236d8.html
https://www.odata.org/documentation/odata-version-2-0/overview/
OpenUI5 version: latest (seems to be for all though)
Browser/version (+device/version): Edge/85.0.564.68
Any other tested browsers/devices(OK/FAIL):FAIL
URL (minimal example if possible): https://openui5.hana.ondemand.com/entity/sap.m.TimePicker/sample/sap.m.sample.TimePicker
User/password (if required and possible - do not post any confidential information here): n/a
Steps to reproduce the problem:
What is the expected result? The value should have changed to 02:00:00
What happens instead? The control resets the value to 24:00:00
Any other information? (attach screenshot if possible) When using databinding the 24:00:00 value is not accepted by the control even when using support2400="true". It always uses 00:00:00.