We reproduced this issue on Chrome with SmartGWT 12.0p 2018-06-06.
The computer locale is en_US but we load date formats from the application user profile, whom in this case has it set to "dd/MM/yyyy".
After the upgrade to SmartGWT 12 the selector set a date in the DateField/DateTimeField in the "MM/dd/yyy" format (default input format) but since we set the format to that fieldto dd/MM/yyyy the date in the field will not correspond to the one selected in the calendar.
This did not happen before the upgrade and the fix is as easy as calling setInputFormat() in every component we do a setFormat(). I would like to have a behavior consistent with the old version of the framework so I won't have to double check any DateItem in the software.
The computer locale is en_US but we load date formats from the application user profile, whom in this case has it set to "dd/MM/yyyy".
After the upgrade to SmartGWT 12 the selector set a date in the DateField/DateTimeField in the "MM/dd/yyy" format (default input format) but since we set the format to that fieldto dd/MM/yyyy the date in the field will not correspond to the one selected in the calendar.
This did not happen before the upgrade and the fix is as easy as calling setInputFormat() in every component we do a setFormat(). I would like to have a behavior consistent with the old version of the framework so I won't have to double check any DateItem in the software.
Comment