If the local is set to be th_Th the date picker is loosing the value. This may be related maybe to the fact that the buddhist calender is 543 ahead ? Not sure about that, but i can see in the value change event on server side that the value is null.
Looking into the datepickerConnector.js and debuging the setLocale i can see that the regex (datepicker.$connector.regex) is wrong due to datepicker.$connector.yearPart.initial is not match the the year 2530 ( which is applayed after using the toLocaleDateString ).
Even we fix this i can see that the 543 years plus are added to every day selection. Not sure if this is another issue or still related to that one.
Another thing is that the the displayed year in the popup is not adjusting bzt still remain in the gregorian calender value. For example 2019 instead of 2562
If the local is set to be th_Th the date picker is loosing the value. This may be related maybe to the fact that the buddhist calender is 543 ahead ? Not sure about that, but i can see in the value change event on server side that the value is null.
Looking into the datepickerConnector.js and debuging the setLocale i can see that the regex (datepicker.$connector.regex) is wrong due to datepicker.$connector.yearPart.initial is not match the the year 2530 ( which is applayed after using the toLocaleDateString ).
Even we fix this i can see that the 543 years plus are added to every day selection. Not sure if this is another issue or still related to that one.
Another thing is that the the displayed year in the popup is not adjusting bzt still remain in the gregorian calender value. For example 2019 instead of 2562