Edgewall Software

Changes between Initial Version and Version 1 of Ticket #11435, comment 3


Ignore:
Timestamp:
Jan 9, 2014, 9:38:14 AM (9 years ago)
Author:
Ryan J Ollos

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11435, comment 3

    initial v1  
    11There is still the issue mentioned in comment:63:ticket:10245, which is present after an upgrade to jQuery UI 1.8.24 and the !DateTimePicker 1.4.3. I'm not sure if either behavior is a defect, but the inconsistency is not desirable.
    22
    3 The datetimepicker stays visible after clicking //Now// until the field it is bound to loses focus. Maybe it should be expected to close. The datepicker disappears after clicking //Today// and will not reappear until putting the focus elsewhere and then back to the element that the datepicker is bound to. It seems reasonable that the datepicker might disappear after clicking //Today//, but it is a little strange the clicking the mouse in the field doesn't cause it to reappear.
     3The **datetimepicker** stays visible after clicking //Now// until the field it is bound to loses focus. Maybe it should be expected to close. The **datepicker** disappears after clicking //Today// and will not reappear until putting the focus elsewhere and then back to the element that the datepicker is bound to. It seems reasonable that the datepicker might disappear after clicking //Today//, but it is a little strange the clicking the mouse in the field doesn't cause it to reappear.