User tests: Successful: Unsuccessful:
PR for #17938
Thanks to @GCLW for the code and his patience
add the following two lines to the "created" field
timeformat="12" format="%Y-%m-%d %H:%M:%S"
As you set the time in the calendar observe the time in the field.
This is the bug. It should show 00:00
Apply this PR,clear cache, and it will behave correctly as in the video below
if i popup calendar in the hour, minute field if i select
10:00 am it shows 10:00
11:00 am it shows 11:00
12:00 am it shows 00:00
10:00 pm it shows 22:00
11:00 pm it shows 23:00
12:00 pm it shows 12:00
i do not say that this change is wrong
it seems correct
but there is an ux problem, that the hours selector 12 is placed after 11,
thus user selecting would expected it to show something bigger right ?
maybe replace 12 with 00 when calendar is shown in am / pm format , and of course place 00 on top of the hours drop down selector ?
I think it would be wise to keep the hour selector containing only 1-12 in when using the timeformat=12 attribute. Only when the timeformat=24 is used should there be a "00" in the selector. There is no UX problem. it is a logical range 01-12 that stays consistent, the user only selects if it is AM or PM.
I think you are trying to force the logic that if someone were to select 11 PM and changed their mind to make it midnight they would just bump up the 11 to a 12, which effectively now makes it 12 PM (noon). That is not a UX problem. That is 100% user error.
The correct logic by a user would be "I have it set to 11:30pm, but I need to change it to midnight. The user would then change the 11 to a 12 and change PM to AM. That is the user logic.
|Status||Pending||⇒||Ready to Commit|
|Status||Ready to Commit||⇒||Fixed in Code Base|
|Closed_Date||0000-00-00 00:00:00||⇒||2017-11-18 15:52:39|