Date format for DateTimeItem is not valid after rolling SmartGWT

[bbaker]

SmartClient Version: v11.0p_2017-04-04/LGPL Development Only (built 2017-04-04)
Browsers: Seen in latest versions of Chrome, IE and Firefox

After rolling from v11.0p_2016-10-23 to the version above, our DateTimeItem controls give a "Must be a Date." validation error after selecting a Date from the date picker. Setting the value with setValue(newDate()) is acceptable to the control.

I've attached a sample.

Any guidance or insight is greatly appreciated.
Thanks

[Isomorphic]

This test cases uses a format that won't be successfully parsed by just calling setInputFormat(), you have to provide your own parser if you want to allow user editing of this format.

However, this has always been the case, but you're reporting this as a behavior change. Perhaps instead, code that installed a parser was accidentally dropped in the upgrade process?

[bbaker]

We never wrote a custom parser, so that's not likely.

Note that the older version doesn't honor the display format set by setFormat(), but the newer version does. Maybe that was fixed and is perhaps the source of the behavior change? We implemented the functionality for our users to customize their date formats a couple years ago, and it just now broke.

[Isomorphic]

If you mean to say that the setFormat() call was a no-op, we don't know of any version where that would have been true either.

What we can say for sure is that there was no version where that format could have worked, because it is not parseable.